A friend of mine turned down a Google L5 offer three years ago to join a 22-person Series A company. The startup ran out of runway in 18 months. He went back to Google and got an L4 offer this time around. He says he doesn’t regret it, but I notice he says it a bit too quickly.
I’m not going to tell you which path is right. But I’ve watched enough of these decisions go sideways to have opinions about what makes the difference between a good bet and a wishful one.
What big tech actually gives you
Compensation clarity, mostly. A senior engineer at Google, Meta, or Apple in 2025 earns somewhere between $280K and $420K total comp depending on level and location, and crucially, most of that is liquid within a year. The Stack Overflow Developer Survey 2024 found that engineers at large companies consistently report higher median salaries than their counterparts at companies under 100 employees.
The other thing big tech gives you is time. 40 to 50 hours a week is genuinely normal at most FAANG teams. That’s not universal, and there are teams known for grinding, but it’s the modal experience. You get weekends back. You can have a side project, or a family, or both.
What big tech doesn’t give you is scope. At a 50,000-person company, an individual engineer’s contribution to any given quarter’s outcome is, let’s be honest, pretty small. You might own a great feature. But you won’t own a product. The abstractions run deep and your surface area is deliberately bounded.
What startup life actually looks like after the first 90 days
The first month at a startup feels electric. There are 11 engineers and you can read every line of code in a week. You’re talking to users directly. The CEO knows your name. You ship something on day 3.
By month four, some of that electricity has turned into chronic low-level dread. The funding round is taking longer than expected. The on-call rotation has five people in it. A senior person just left and nobody talks about why. This is, I’d argue, the median early-startup experience. Not catastrophic, but not the highlight reel either.
Startups that make it past Series B tend to look a lot more like big tech companies than people expect. Process accumulates. Headcount grows. The “everyone does everything” culture fades when you have 200 engineers and two VP layers. If you joined for startup chaos, you might find yourself in a mid-size company after three years wondering where the chaos went.
The equity question deserves a clear-eyed answer
Startup equity is a lottery ticket with bad odds and a long wait. That’s not cynicism; it’s base rates. According to BLS data on business survival rates, roughly half of new businesses don’t survive five years, and tech startups that raise VC money face their own brutal funnel: few reach Series C, fewer still generate returns that flow meaningfully to common shareholders after liquidation preferences are applied.
I don’t have data on what percentage of startup equity packages ever pay out more than what a big tech package would have earned over the same period. My guess is it’s low. Maybe 1 in 8 or 1 in 10, if you’re at a reasonably well-funded company. If you’re at a seed-stage company where you need a 100x outcome to make money, the math gets much uglier.
None of this means skip the startup. It means treat the equity as a bonus you might get someday, not as deferred compensation you’re counting on.
Career stage changes what the right answer is
If you’re two years out of school, the big tech argument is harder to dismiss. A few years at Google or Microsoft builds a resume layer that travels. The systems you’ll work on are genuinely large. The people around you are often very good. That foundation compounds.
If you’re seven years in and you already have big tech on your resume, the calculus shifts. You have enough signal to evaluate a startup team seriously. You have a financial cushion to absorb some risk. And you’re more likely to get real ownership, not a junior position on a team of 40 doing one slice of a larger product.
The honest version of the “start at big tech and move to a startup” advice is that it works best when the startup is post-Series A, you’re joining in a senior role, and you do it before you’re 35 and have a mortgage and two kids. Timing matters more than people admit. People navigating this with a lot of fixed costs find the startup risk calculus looks very different.
One thing I think most career advice gets wrong
Most takes on this topic focus on salary and title. They underweight culture fit with how the company makes decisions. A flat startup where the CTO makes product calls unilaterally is not the empowering environment the job listing described. A big tech team where the engineering manager shields the team from politics and runs a genuinely autonomous roadmap is better than most startups at giving you real ownership.
The best predictor I’ve seen for whether someone is happy with their choice is whether they correctly anticipated the decision-making environment. Not the perks. Not the comp. Who actually decides what gets built, and do you have meaningful input into that?
That question is worth 30 minutes of due diligence before you sign anything.