I Worked for a Startup That Didn't Pay Me. Here's What Engineers Keep Getting Wrong

Unpaid work at an early company taught me that contracts are not money, and that discipline and limits matter more than heroics. Lessons for engineers in volatile environments.

Jon Wexler

I once worked for a startup called Soon Dating.

They owed me around $56,000. I never got paid.

Background

This did not start as a bad situation. Like most early-stage opportunities, it began with energy and momentum. There was a real product vision, active development, and conversations about funding that made the future feel close.

There was also a contract. There were defined expectations. On paper, it looked legitimate. In practice, it felt like something worth committing to.

So I treated it like a job. I showed up, built what was needed, and trusted that the structure in place would hold.

That assumption turned out to be wrong.

The shift did not happen all at once.

Payments started slipping. An invoice would be delayed, then another. Each time there was a reasonable explanation. Funding was in progress. Money was expected soon. Something was processing.

Individually, none of these explanations felt alarming. Together, they formed a pattern that I did not act on early enough.

I kept working. Like most engineers, I optimized for progress. I assumed that continuing to deliver would help stabilize the situation or get things across the finish line.

Instead, the unpaid balance grew to a point where it could no longer be ignored.

At that stage, I explored legal options. The reality was sobering.

Even with a contract, enforcement depends on the company having money or assets. If a startup runs out of cash, there is often nothing meaningful to recover. Legal action becomes expensive, slow, and uncertain, especially across jurisdictions or without clear leverage.

The hard truth is this: a contract does not create money. It only gives you a claim to it if it exists.

By the time I fully internalized that, the situation was already set.

Lessons learned

The biggest mistake was not that I worked with a startup. It was that I treated the engagement as if payment was guaranteed.

  • I let unpaid work accumulate beyond a reasonable threshold.
  • I relied on verbal assurances about funding instead of verifying them.
  • I continued delivering at full speed even as warning signs appeared.

None of this felt irresponsible in the moment. It felt collaborative and professional. In reality, it exposed me to risk that I was not actively managing.

What I would do differently is straightforward, but requires discipline.

  • Keep unpaid balances small and enforce clear limits. If payments fall behind, pause work.
  • Structure payments in short intervals or require partial payment upfront.
  • Ask direct questions about runway and funding status, and take vague answers seriously.
  • Separate equity upside from cash compensation instead of blending the two.
  • Be willing to walk away early, before the situation compounds.

The mental shift matters most. When working with early-stage companies, you are not just contributing code. You are making a financial decision every time you continue without being paid.

If you do not manage that decision, it will be made for you.

Bottom line

Startups usually do not fail because they choose not to pay people. They fail because they run out of time and money.

When that happens, contracts offer limited protection.

Structure and discipline at the start of the engagement matter far more than anything you try to enforce at the end.