As a recent college graduate, should I work in a tech startup?

The night after my graduation ceremony I signed an offer from a fintech startup that operated out of a half-empty coworking space — roughly a dozen people, a dog, and not much in the way of processes. I figured I’d stay a year, learn “how real software is built,” and move on. Two years later I was still there, debugging payment flows at 2 a.m. and wondering why the CI pipeline only broke on Fridays. Fun times, mostly.

If you’re fresh out of college and still living on ramen (well, more like supermarket pasta in my case), a startup is the cheapest bet you’ll ever be able to place on yourself. Low opportunity cost, no mortgage, no kids asking why you missed bedtime again. Worst case you walk away with a GitHub repo full of scars and a line on your résumé that says you shipped production code. That said, I’ve watched someone on my team sink almost six months into job hunting after their first startup folded, so the “you can always get another gig tomorrow” mantra is… optimistic. Keep an emergency fund — even a small one.

Before you jump, prod a little. Some startups turn into zombie factories of ticket-shuffling and compliance checklists, no matter what the pitch deck promised. Ask what the actual engineering work looks like day-to-day. If the answer is “mainly updating screenshots in Confluence,” run. (From what I saw, spending weeks swapping logos across endless PDFs was not uncommon.)

Money matters, even when you pretend it doesn’t. I usually ask two blunt questions: “How many months of runway do we have today?” and “What’s the plan for hitting cash-flow positive?” If the founder waves a vague hand toward “future Series A vibes,” that’s a red flag. Still, I could be wrong — some of those companies get funded anyway. Just don’t make life decisions on promises you can’t verify.

Layoffs are weirdly non-linear. I’ve seen stellar engineers let go because the market tanked and the CFO needed the quickest line item to chop. Your skill set travels with you, sure, but timing and luck have louder voices than we like to admit. An emergency runway that covers a few months of rent is boring advice, yet it’s what keeps the lights on when macroeconomics gets shaky.

Culture is the wildcard. Some teams genuinely operate with flat hierarchies and flexible hours; others talk the talk while secretly rebuilding a mini-corporate empire. Same with tech stacks — one founder may swear by Elixir, the next by a React monolith stapled to a pile of Lambda functions. Match their tooling to what you want to learn; don’t assume “startup” automatically means your favorite language.

Equity can sweeten the risk, if the vesting schedule is humane and the cliff isn’t a cliff-face. Try negotiating for options that you can keep if you leave early. (I failed at this once and watched my shares evaporate — lesson learned.) Just remember: paper millions are still paper until there’s liquidity, and secondary markets are thinner than Twitter makes them sound.

One hack that’s served me well: always run a side project in parallel. Building something you fully own keeps your hands dirty with real code and shields you from the “only did Jira tickets” résumé gap. It doesn’t need to be the next unicorn — a weekend microservice that solves your own itch is plenty. And if the startup explodes spectacularly, you’ve already got something to show.

I don’t have a clean finale here. Startups can be rocket ships or slow-motion train wrecks, sometimes both in the same quarter. If you can stomach that ambiguity — and you’re okay trading stability for a steeper learning curve — give it a shot. If not, there’s zero shame in picking a safer path and hacking on passion projects after hours.

📚 More Q&A here