Joining Attend.com

When I left Etsy at the end of February, it was because I wanted to join something small where I could have a lot of impact. I did that, becoming a co-founder/CTO at a three person startup in Boston in the online grocery space. Unfortunately that business didn't work out, and closed its doors for good on April 6th. That left me wondering what to do next, and I spent the month of April talking to a lot of companies and exploring opportunities. I wanted to stick with my original plan of joining a small company, but I decided to make post-Series A companies my main focus, to take away some of the risk that I experienced at a seed stage, pre-product company.

I was introduced to Attend by a friend, and the company fit all of my criteria. It has a popular product in the market, has around 30 employees (~5 full-time engineers), just raised a Series A, is in growth mode, and has a great team. There's a ton of potential for me to learn technically there and grow as a leader. Attend provides an event management software product, which is also appealing to me since I like to go to a lot of conferences. The company's current focus is in higher ed, but it's only a matter of time before we tackle the tech conference circuit :-).

I'm starting this coming Tuesday as the "Lead Front End Engineer", although I plan on touching a lot more than just the front-end. That's where the biggest need is right now, but I'm excited to apply my knowledge across all layers of the stack and help grow and scale the business.

I'm really looking forward to this next challenge - wish me luck!

Comments

Post a Comment

Popular posts from this blog

14 Day Challenge - Information Diet

Image
In the spirit of the 30-day challenges popularized by Matt Cutts (among others), I have spent the last 14 days on an "information diet".  This is not a new idea by any means, and in fact there was an entire  book written about the concept (and a more recent one from Cal Newport which I highly recommend).  I actually heard about it initially from Tim Ferris, and this post on the 4-Hour Life Blog.  Anyway, enough with the background - what the heck is this about?
Read more

Trust, but verify

I’ve always disliked this phrase, and it felt like a pure contradiction - you wouldn’t need to verify if you truly trust. It has come up recently in my life and work, so I decided to dig in and crystallize my thoughts. The phrase originated as a Russian proverb (doveryai, no proveryai) and is attributed to Vladimir Lenin and Joseph Stalin . Inauspicious beginnings, to say the least. Ronald Reagan then co-opted it in 1986 to refer to nuclear disarmament, and from there, it entered the American lexicon. People often consider it a leadership principle or some fundamental truth, which needs more nuance.  As a leader, one must decide how to operate in different contexts. A good initial posture is to distrust and verify often until you have built up the appropriate level of trust over a long enough period. I’ve had so many occasions in my career when I heard some variant of: The code is terrible The code we’re writing is excellent! That’s impossible That will take months We’re in a good stat
Read more

Cognitive Biases in Software Engineering

Image
Human logic, unlike that of the machines which we program and use every day, isn't perfect.  We make mistakes, we establish bad mental habits, and we have many cognitive biases that negatively impact our ability to be successful engineers.  I want to go over five of the most common biases that I see on a regular basis as a software engineer.
Read more