Should you leave a stable senior role for a startup?

The single question that predicts whether a move from a stable company to a startup will go well is this: does the startup have a specific, nameable problem that your exact experience solves, or are they hiring "someone senior" as a category, without a clear thesis for why it's you?

The good version of this move

A startup that says "we're scaling from 20 to 200 people and we've never done that before, and you have" has a specific thesis. A startup that says "we need someone experienced to help us figure things out" does not — and that vagueness usually means the org isn't ready to use senior experience well yet, regardless of the title or equity on offer.

What actually changes about the job itself

At a stable company, senior roles usually come with existing processes, established peer relationships, and a scope that's already been fought over and settled. At a startup, you're often building the process AND doing the job AND defending the scope simultaneously. This isn't necessarily worse — many senior professionals find it more energizing — but it is a different job than the title implies, and worth being honest with yourself about wanting.

The financial reality check

Model the ESOP component of a startup offer as likely worth zero, and evaluate the fixed pay and role on those terms alone. If the offer only makes sense assuming the equity pays off, you're not evaluating a job offer — you're evaluating a bet, and should treat it with the risk tolerance a bet deserves, not the certainty a salary deserves.

The question that actually matters

Not "is this a good startup," but "does this specific founding team know exactly what they want from someone at my level, and can they articulate it clearly in an interview." If they can't articulate it, assume you'll be the one inventing your own job description after you join.