Tag Archives: Aaron Patzer

Startup Engineer: Which number is right for you?

Having been an engineer at a startup I empathize with people who are being recruited into startups especially if it’s their first startup. The key deciding factor for me was that I wanted to learn everything about engineering a consumer product. Sure making bank is a nice motivation, but I quit my Masters at Stanford because I knew I’d learn a ton more working on the ground floor of a startup than I would sitting in a classroom. I still wholeheartedly believe that the only way I learn is by doing, which is why I’m starting a company instead of getting an MBA. It’s my MO but that doesn’t mean it works for other people.

The point of this post isn’t how to negotiate or what to ask for because it really depends on your needs (maybe I’ll cover that later). Its meant to paint a realistic picture of what life is like as a ground floor engineer versus past 10, 20 and 30+.

Being a ground floor engineer means you work everyday… 365 days at the very least for the first year. You’re expected to be a generalist, and its best if you’re passionate about the product. There’s just a shit load to do: features, infrastructure, testing, integration, bug fixes, mastering new technologies, bringing others up to speed on the architecture, interviewing candidates, and the list goes on. You’re on call, you fix everything big and small, and you don’t complain you just learn and do! The benefit is you have one of the biggest equity stakes in the company, but the bigger benefit is you know how the entire system is architected and the code you’ve written impacts millions of people! I chose this role for myself because I wanted to be a generalist and learn how the entire system was integrated and built (also why I majored in EE and CS). I also wanted to gain some insight into prototyping and how product’s evolved. If you’re a hungry geek do yourself a favor and don’t settle for anything over 10. Start early!

5-10 stuff is built… but you’re still adding a ton of value to the product and defining the engineering team. You might miss out on a lot of the business and product decisions that were made early on, but if the company is pivoting then it’s ok. You’re still going to play a heavy hand and have your pick of projects long-term.

10-20 this is when startups call in specialists. They are interested in hiring a front-end or back-end developer, algorithms guy, or architect. Not really a hacker-type, but someone who has a deep understanding of a set of technologies or a predilection towards a particular area. Its also one of the more risk averse positions because the startup has mostly likely gone through 1-2 rounds of funding and has gained user traction.

20-30+ get ready to scale and maintain! There’s still a lot of innovation going on, and its focused on scaling the system to support user growth. If you’re a young engineer you’re probably going to be thrust into the maintenance camp, learning the existing architecture first before being given your first juicy project. But hey its a startup and it’s making progress! If the founding engineers are still around you’re in luck because they’ll have a ton of knowledge to impart.

The biggest thing to think about when deciding what stage you want to start at is knowing personally how comfortable you are with change. New people starting every day, week or month, business goals and priorities switching courses, having new bosses, and your own workday context switches: working on a project to fighting fires and back to coding. The earlier you start the more change you deal with and the less time you have to really sit down and think through problems.  You’ve got to be quick on your feet,  and deal with the ebbs and flows – learn to adapt and accept. If you like stability start later.

Regardless of which position you do decide, a startup is a lot of fun, but it’s a lot of work.  It’s not a cushy job nor is it a way to get rich.  Its like buying a home: don’t be fixated on flipping it, picture  yourself living in it for the next 4-7 years because thats how long it will be if it’s going well.  Your teammates are the family you are going to raise in it, and you want to make sure you fit in well with the culture and community.  Most importantly make sure you buy  and believe in the long term vision of the founder.

(I was affectionately called #2 at Mint.com, because in the words of Aaron Patzer, “…engineers start counting at 0.” )

Enhanced by Zemanta

Momentum

Being at the ground floor of a startup is the best, not that I’ve ever come in at a later stage, but having gone through the full lifecycle of one startup I can vouch for the beginning being the most exciting and romantic period.  You define the product, engage with users, research technologies to use to build your product, and build the company culture.  It can be daunting to take on all of these tasks, which is why it’s important to build momentum slowly.  Reflecting on my experience at Mint.com I’ve realized that one of the key components to its success was momentum.  The momentum that Aaron Patzer and the rest of use Minters kept building over time (time == 4 years, not the popular myth of 2).

There are a couple other companies that have had this natural progression as well: Twitter and Facebook.  But I’ve also noticed more than a handful of companies that started around the same time as Mint and remained flat over the years or closed up shop because they couldn’t get traction or generate revenue.

How do you go about building momentum and keeping it up?

1. Start slow and understand the lay of the land.

As an entrepreneur and engineer it is very tempting to want to build something quick and fast.  There is also a lot of talk of “failing fast”.  If you expect to fail fast, what’s the fallback?  You’ll figure it out as you go, right…  Call me cautious but I believe in pipelining ideas especially when my own funds and time are at stake.  To create a pipeline of ideas you have to understand the entire lay of the land.  Take your initial idea peg it to an industry.  Start by doing an in depth analysis of the major pain points in the industry, which means asking and answering the following questions:

  • How big is the industry?  Are there multiple verticals or other industries that are tangential?
  • What are the major pain points?  How long has each been in existence? How are they currently being solved with and without technology?
  • Who are the primary competitors and who are the secondary competitors?  Who are their customers?  And how do their customers feel about them?  And why do customers use them? Why are they the incumbent?  How do they make money?  How have they positioned themselves against each other?

It usually takes a couple a month or more to complete this market analysis phase, and its worth the effort because it makes you a lot more knowledge in terms of figuring out where you can add value and what the trade-offs are.

2.  Put aside your engineering and entrepreneurial ego and learn to empathize.

Sure you’re a rock star coder, and you can get a web app running in no time, but coding at this point is a bad idea.  Putting a web app in the hands of customers leads to more comments and questions like: “I don’t like this interface.  Why is this button green?  What’s with all the bugs?”  And you’re left thinking these people don’t get it my product rocks!  Or wow I wasted a lot of time writing code…

Instead you want to start having conversations with your customers.  Talk to potential customers and walk them through the problem space you are exploring.  Explore all their problems and then explore all their current solutions.  Tell them you’ll come up with a solution on paper and would like to try it out on them.  Unlike code the great thing about paper is that it’s 100% bug-free!  The added roughness of a paper prototype forces the user to think in terms of workflow and interaction instead of the design aesthetic, which is much farther down the pipeline.

Finding customers who will be evangelical about your product – early adopters or influences – also helps with building momentum.

3. Create a product roadmap.

 

After talking to customers and getting feedback from paper prototyping you have to think like an engineer, which means making trade-offs.  You are constrained by time, money, and resources (hands to code).  You have to figure out how you can add value to customers given these constraints. Come up with a 1-3 year product roadmap that lists all the features and even includes a first phase revenue model. You might end up abandoning the roadmap entirely, but its purpose is to serve as a vision for your product and company.  Use it as a reference when talking to potential customers, employees, and investors.  That’s how you get initial engagement and continue to build momentum.

3. Measure Progress every week, month, and year.

 

Once you’ve launched it’s easy to get bogged down in the day-to-day affairs of running a startup: firefighting, interviewing, fixing bugs, handling user issues, etc.  While these are all important tasks that have to be accomplished you have to be thinking big picture as well, which means measuring new traffic, user engagement, retention rates, and revenue vs. burn rate.  To keep up the momentum you can’t solve each of these issues on your own.  You have to broadcast these numbers to the rest of your team.  The more you broadcast within your startup the more people think about solutions.

Post launch is where you can start to lose steam, because problems start to arise that were both expected and unexpected.  You have to charge through it by prioritizing issues instead of solving all of them at once, and being happy with incremental progress.  Focus on distribution (new users), engagement (keeping existing users), and revenue (making money off of all users).

4. Timing

 

Sometimes a series of events contributes to your success.  When we started Mint.com the recession was looming, and figured it might make fundraising difficult, but it would also force people to become more aware of their finances.  We got the best of both worlds: funding and frugality.  The recession was a momentum booster, because it led to more press and coverage.  You can’t bank on making bank this way.  Instead, stay informed and learn to anticipate industry trends, events, the state of the union, and how they might affect your startup.

5. Don’t stop to smell the roses.

 

When you’re users tell you they love you its easy to want to bask in the glory of it.  Enjoy the moment, literally.  Then go find the haters, on-the-fencers, and non-believers and try your damnedest to convert all of them!

Enhanced by Zemanta

Timeline: Mint.com – 2008

At the start of 2008 the primary goals for Mint.com were to deliver a complete personal finance solution, increase customer acquisition, and grow its revenue.  What this meant in terms of features was that we would put out an investments tab, increase or PR efforts to have Mint known as a name brand in every American household, and improve our offer management system by introducing “Way to Save”.

What started out as a problem for Aaron Patzer, managing personal finances quickly and gaining insight easily into spending habits, soon became an issue for the entire nation.  With the recession looming Mint’s efforts became crucial for Americans everywhere.  However, the recession brought on concerns about funding for Mint, and larger competitors started to gain on us.  We were the underdog in the personal finance space going into 2008.

January 2008 – In its efforts to appease the neglected Mac users and join in on the trend towards web-based applications, Intuit launched Quicken Online, a direct competitor to Mint.com.  Unlike its free competitor, Quicken Online was a subscription model that charged $3 a month.  Aaron’s vision had always been to keep Mint.com a free product for its users.  His goal was to only make money by saving his users money.

Mint.com hit 100,000 users, and continued to grow by tens of thousands every month, as Aaron continued to go on press tours and gain media coverage.

March 2008 – As momentum started building up, Aaron started thinking about raising another round of funding.  The recession in the US was still nascent, but he wasn’t sure how it would impact the growth of the company.  To avoid having to fund raise during the recession, he decided to preemptively seek a series B round of funding.

Mint raised $11.4 in series B funding from Benchmark Capital.

April 2008 – Mint launches a beta version of its investments feature and decides to increase its presence by co-branding with Motley Fool.

May 2008 – After a long month of coding the Mint teams decides to celebrate funding and the launch of investments by going to Sky High Sports and playing several games of trampoline dodgeball, femgineer came out unscathed, I wouldn’t say the same for the mengineers 😀

June 2008 – As the teams size continued to grow we began to outgrow the cubicles that housed the downstairs Minters. Instead of moving out of our down town Mountain View digs we decided to remodel by tearing down the cubicles and having a more open floor plan.  This was also done to foster a more collaborative work environment.

September 2008 – The worst financial debacle since the Great Depression strikes Americans.  Crises in the credit and housing markets cause stocks to decline, increase unemployment, and leave hundreds of thousands of Americans with no savings to fallback on.  Many turn to Mint.com to help them understand their spending habits, make cutbacks, and hopefully weather the painful maelstrom.

As banks continue to go under and consolidate, Mint is forced to pull many offers, and find  new ways of helping users find savings.

October 2008 – Unable to compete with Mint’s growing user base and unwilling to surrender Quicken Online decides to release a free version with fewer features.  Mint continues to lead online personal finance in terms of user engagement and user growth.

December 2008 – In Mint’s quest to continue to keep user’s engaged and increase distribution the team decides to create an iPhone app.  The app is a condensed version of the website, featuring alerts, budgets, and account balances.  The team works hard to get the release out before Christmas time.

After the launch of the iPhone app Mint.com becomes one of PC World’s 25 most innovative products.

Enhanced by Zemanta