Joining a startup as the first engineer: how to bet on the right one.

Priya had three offers. A FAANG team with a number she could brag about, a Series B with a fancy title, and a four-person startup with a whiteboard sketch and a founder who answered her emails at 1am. She took the startup. Two years later it was acquired, and the equity paid off her education loan twice over. She will be the first to say it could easily have gone the other way.

Joining a startup as one of the first engineers is one of the highest-leverage career bets you can make, and one of the easiest to get wrong. The salary is lower, the title is bigger, and the risk is real. So the only sensible question is: how do you tell a good bet from a bad one before you have spent two of your most productive years on it?

Look at the founders the way an investor looks at founders

At pre-seed and seed, you are betting on people far more than product. Spend your interview time understanding the team, not just the tech stack. Three things matter most:

• Do they understand their customer better than you expected? Founders who can describe their users' problem in vivid, specific detail tend to build things people want.
• Have they shipped and learned, or only planned? Ask what they believed six months ago that they no longer believe. Good founders have updated.
• Do they make you sharper or smaller? You will spend more waking hours with these people than with your family. Notice how you feel after the conversation.

Ask the questions that reveal runway and reality

You are allowed to ask hard questions, and how a founder responds is itself a signal. Be direct and kind:

• How much runway is left, and what has to be true to raise the next round? If you want to understand what that answer means, our runway calculator shows how a cash balance and burn rate translate into months.
• What are the last three months of revenue or key usage numbers? You are looking for a line that points up and to the right, not a single good week.
• If the next round does not come, what is the plan? There should be one.

Understand your equity before you fall for the percentage

"One percent" means nothing until you know the details. Learn the vocabulary so you can read the offer: vesting, cliff, strike price, preference, dilution and option pool are all on our terms page. Ask how many shares are outstanding, what the last price per share was, and what your grant could be worth across a few honest scenarios, including the one where the company is sold for a modest sum.

Then accept the truth every experienced startup engineer eventually internalises: most equity ends up worth little, a few grants change your life, and you should choose a company you would be proud to have built even if the equity were zero.

Judge the engineering culture by how decisions get made

Ask to see the codebase or do a paid trial day if you can. You are not just checking code quality; you are checking how the team thinks. Do they ship small and often, or in big risky bursts? How do they decide what to build? When something breaks, do they blame or do they fix the system? A small team with healthy habits will out-build a bigger team with bad ones.

Priya's bet worked partly because of luck and partly because she did the work to stack the odds. You cannot control the luck. You can absolutely do the work. Find a team worth betting on, and bet with open eyes.