6 things I wish I’d known while leaving Microsoft job for a startup

Jensen Harris

Leaving a big company job for a startup can rejuvenate your career and make you love work again. But landing a startup job requires relearning some things, especially if (like me) you logged years and years at Microgoogfaceforceazon.

Here are six things I wish I’d known:

1) At a startup, you will probably make less money at first.

Yes, if you join the perfect startup early enough, your equity may someday turn into a private island and 200 foot yacht. But, in the meantime, your take home pay is likely going to be a bit less than it is now. The so-called “golden handcuffs” that big companies give you in stock grants/bonuses that vest over time are because those companies need to overpay you in order to get you to stay. Think about the metaphor for a second: You don’t have to handcuff people to things they love.
You can make a great living at a startup of course, and growth stage startups in particular pay competitively and often with fantastic benefits. But if optimizing for the most take home cash is your #1 priority, keep your job. Seriously… it’s ok. Startups are not for everyone.

2) About your resume:

if you’ve been at a big company for a long time, you really need to figure out what experiences you’ve had that show depth outside of that company. Wrote apps for an unfamiliar platform? Started a nonprofit? Ran a successful Kickstarter campaign? All great. When I left Microsoft after 16 years, I had worked on what seemed to me to be a dizzying array of roles and products. Within Microsoft, that was compelling. To the external world, it was just 16 monolithic years at MSFT and everyone asked pointedly: why didn’t you leave sooner? Also, leave off whatever “high potential” programs you were selected to, or awards you won inside of the megacorp. Same with review scores. Those don’t matter on the outside, and just show that you’re still deeply entrenched in the value system of the company you’re leaving.

3) Here’s something it took me a long time to learn on the outside: say “I” instead of “we.”

Working for @stevesi at MSFT, I learned an incredibly important lesson about leading inside of a large team: always say “we did this” not “I did this.” Perfect advice for that situation.
When interviewing, though, saying “we did this” makes it hard to identify your personal contribution. I find myself talking to megacorp candidates trying to understand what did *they* do? What specific designs did they draw… what code did they write… what ideas were theirs? But also, don’t claim personal accomplishment for a team effort unless you provably did it. You probably didn’t “bring AI to iOS” yourself. You didn’t “create the Windows 7 kernel” or “increase S3’s scalability 400%” yourself. Specify *your* actual contribution to the product.

4) For devs: show true curiosity outside of your company’s stack.

Your mastery of Google’s internal experimentation pipeline is not interesting outside of Google. If you are MSFT and I ask you if you’ve used Redis and you say “you mean Azure Redis Cache?”, that’s not a good sign.This means if you work for Amazon, build something on DigitalOcean. Googler? Build with React. From Microsoft? Get into AWS. The best big company devs we’ve hired are the ones with natural, proven technical curiosity outside of their company’s native stack, shown by actual work.Don’t say the reason you want to join a startup is “to have a chance to learn XYZ technology.” Learn and build with the tech you are curious about yourself… your company is not in control of your learning. Prove that you’re curious by actions, not words.

5) Be a worker… and be prepared to show it.

Big companies are necessarily full of people whose primary job it is to carry information from one meeting to another, from one department to another. Middle managers and PMs, in particular, are often defined by this type of work.Startups don’t have this kind of “info pusher” job. They can’t afford to, and they’re not big enough to need it. Everyone is responsible for making something, building product, owning decisions, selling something, hustling. You can’t just show up at the meeting and “seem senior.”
Big company folks sometimes flame out at startups because this kind of individual work is not what they actually want. No judgment from me or anyone else if it’s not… be honest with yourself about the degree to which you want to be on the frontlines, making or selling things.

6) Embrace the unique skills you developed in a big company.

No one builds more reliable software at scale than Amazon or Google… this knowledge can be a huge boon to a startup. Salesforce perfected solution-based selling; this may help scale your SaaS startup’s sales expertise.Don’t feel like you have to be on your back foot or defensive about your time at a megacorp. It took me a year out of Microsoft to realize that so much of what I learned there was applicable in my new startup job—i just needed to learn to apply it in a different environment.
There’s a whole world out here, free from the walls of your megacorp job. Enter into it for the right reasons, and you’ll find joining a startup to be truly transformative for your career and rejuvenating for your soul. Prepare for it the right way, and you too can join us!

Leave a Reply

Your email address will not be published. Required fields are marked *