How To NOT Get Screwed As A Software Engineer

The speakers say co-founders often benefit from splits closer to equal, rather than a technical founder receiving 10% because a business founder negotiated harder. Early employees doing co-founder-level work may be undercompensated at 1% or less. For essential engineers, they suggest asking whether a successful exit could provide life-changing money.

If business leaders make decisions without the engineer and use them only to write code, the speakers see that as a warning sign. They also suggest comparing effort across the team: a technical co-founder working constantly while other counterparts contribute little may be carrying an unfair share.

Engineers often see product and launch results firsthand, so the speakers encourage them to trust evidence that a company is not working. They caution against being brushed off when growth, revenue, or runway are poor. A demanding role can still be a good deal if compensation, learning, work-life balance, or other benefits make it worthwhile.

A strong situation can offer a good risk-reward trade, substantial responsibility, and faster learning than a larger company. A startup can also be valuable even if it fails, for example by providing experience or helping someone get a visa. Shared ownership and honest expectations matter too, and having a seat at the table means sharing responsibility when things go wrong.

The speakers recommend comparing the job with alternatives, asking directly for a voice in decisions, and opening a conversation about how equity was set. If the work is undervalued, another company, location, or career move may offer better compensation or opportunity. They encourage technical workers to recognize their value and business leaders to treat teammates honestly.