Big tech → founding engineer: worth the leap?

Engineering & Tech Stack · Series A · high stakes

Big tech → founding engineer: worth the leap?. A startup engineering and tech stack decision for founders. I've been at Amazon a few years and have wanted…

Decision context

I've been at a Big Tech firm for a few years and have wanted to break out of big tech for a while to try the startup world. Seeing a lot of Founding Engineer roles open up (typically $150-200K base with 1-3% equity at the higher end). What I'm optimizing for in my next move is learning. I've only ever worked with Amazon-internal tooling, so I feel boxed in. I'm fine trading off work-life balance, I actually enjoy coding and don't mind the extra hours, and I'm hoping to land something remote because RTO is wearing me down. For anyone who's made this jump or hired for these roles: is going from big tech to founding engineer actually worth it?

Decision graph

Operator judgments (10)

Operator judgment

Cam Sullivan · CEO

You should have an extremely high bar for which startup you join. I know people deep in the SF scene, and the reality is most startups don't really know what they're doing. So the "exposure" you get is often just building everything yourself on brutal timelines with no support. Founding engineers usually carry the bulk of the eng work while the founders or CTO do far less. Add to that: seed stage is statistically the worst for equity returns. Look it up, the gap between 1% pre-Series A after dilution and 0.01% at Series C is smaller than people think. So you're really going for the experience and hoping the lottery ticket hits. Honestly I'd either stay in big tech or start your own thing. The middle path is the one that burns people most. But best of luck whatever you pick, happy to talk through if useful.

Operator judgment

Joe Berrizbeitia · COO

Seeing a wave of ads lately pitching founders "keep your equity, don't bring on a tech co-founder, let our AI build your MVP for 1/10 of the cost". Counted a few in the last couple weeks. It's a concerning trend. Good startups are roughly 1/3 team, 1/3 tech, 1/3 business model. When control and equity-hoarding start outweighing the growth, that balance breaks. Speaking from inside it, I'm a pre-seed tech co-founder with under 30%, built the 0 to 1 MVP, now running ops, and my non-technical partners care more about protecting equity than actually growing. Strong market git, stuck on the revenue model, and the friction is all about control. Not a great spot to be in.

Operator judgment

Juan Francisco Verhook · Founder & CTO

Worst case, 1% pre-A gets diluted to maybe 0.35-0.4% by the time you're a few rounds deep. And that's assuming heavy dilution every round with no anti-dilution protection and no follow-on grants. That's still 30-40x more than the 0.01% you'd get joining at Series C. Each round typically dilutes existing holders ~15-15%, and option refreshes often offset some of that for key early employees. Founders and early team take same dilution hit proportionally, so everyone's aligned on minimizing it. The real variable isn't the dilution math, it's the outcome. 0.35% of a company that exits at $2B is life changing. 1% of the 95% that go to zero is nothing. The percentage matters way less than picking a company that actually makes it.

Operator judgment

Richard Fernandez · CPO

I'd argue that 95% of people don't know what they're doing, not just startups. So that's the wrong filter. What I look for instead is whether the company has a sharp, specific vision of the product they're building or the problem they're solving. Most teams figure out the "how" as they go, that part is learnable. What's much harder is to fix a fuzzy or constantly shifting sense of what they're actually building and why. Clarify of vision beats operational polish every time at the early stage. The execution catches up. A muddled vision rarely does.

Operator judgment

Andrés Vial · Angel & Advisor

Founding engineer is one of the worst risk-adjusted jobs out there. You take on near-founder workload and stress for a fraction of the equity and none of the control. The only real reason to do it is if you're getting some asymmetric upside beyond the role itself: working directly under a founder you'll learn an enormous amount from, getting plugged into a network you couldn't access otherwise, or positioning yourself to start your own thing next with the scars and relationships to show for it. If the only pitch is "build cool stuff fast" that's not enough. The math doesn't work unless there's a second-order payoff you're optimizing for.

Related decisions

View interactive thread on MindCap