What I Learned From My First Startup Job.

My first day, one person was in the office. My laptop had not been ordered. Getting access to the company's Microsoft account took days.

That detail keeps coming back to me. Not because it was the worst thing that happened over the months that followed, but because it was a preview of how things would go. A company that had described itself as financially stable and well-organized had simply forgotten to prepare for its new hire's arrival.

I should have paid more attention to that.

It Sounded Good on Paper

The job was a cloud architect role at an Austrian startup. The office was in a converted tobacco factory. That detail stuck with me during the interview process, the way cool spaces sometimes do. The company described itself as financially stable, with an existing team and a real product. The role sounded solid.

The hiring process took about four months and involved multiple rounds. One interviewer missed two of her scheduled calls with me, though we did eventually meet in a separate session. I chalked all of it up to startup chaos.

Then came the contract.

I had it reviewed by the Arbeiterkammer before I signed. They flagged multiple invalid and missing clauses. The salary had also been quietly reduced by a small amount from what we had discussed, with no explanation offered. The AK helped me address those issues before signing. I accepted the corrected version. I wanted the job.

There were still signals I chose to ignore. I walked past them.

What Was Promised vs. What Actually Happened

I was hired as a cloud architect on an existing team. That team included an external contractor, a full scrum team, alongside a few internal colleagues. Within a few weeks, the startup decided to put the contractor on a break to cut costs. Management kept promising they would return: first one month out, then two months later, then after the new year. They never came back. I ended up as the sole developer on the product.

A few months in, I was asked to build a product showcase website for the company to present at an international conference, by the end of that week. Not a conference website, but something to share the company's product with others while attending. There was no agency budget, no other developer, and this was neither my job title nor my area of expertise. The domain had been registered two months earlier. I built it in a few hours and got it live.

Around the same time, I was worried enough about the company's finances that I applied for a secondary job permit. Management responded in writing: the finances were "perfect." No need to worry.

As autumn arrived, the atmosphere shifted noticeably. Upper management started attending product and team meetings directly. Micromanagement increased. Mandatory office days went from one to two per week. The speed of product development started being criticized openly.

Shortly before Christmas, the company held a surprise all-hands meeting, scheduled one day before the holidays. Three colleagues were laid off on the spot. Management acknowledged the financial situation was bad. The CEO and other executives announced they were voluntarily taking a 30% pay cut.

"Perfect" had become "bad" in the space of a few months.

About six or seven months in, the company organized individual meetings between each employee and the full leadership team: CEO, CFOO, and HR. In mine, they gave me positive feedback and told me the financial situation was "not great but we're working on it," with roughly five to six months of runway remaining.

The Exit

Shortly after, the CTO resigned by email while on a three-week holiday. No replacement was sought.

I could see where things were heading. I did not want to simply walk out, but I also did not want to continue full time at a company running on fumes. I asked to reduce my hours to 20 per week. The company offered a reduction from 38.5 to 36 hours. Since that wasn't workable, I asked about educational leave instead, with the idea of working a few hours a week alongside it. They said they could revisit that in six months.

That was it for me.

I resigned, fully documented with registered mail. I worked until my last day, documented everything I was responsible for, and handed over as cleanly as I could. I don't regret how I left.

Getting What You Were Owed

Shortly after my last day, HR confirmed that my final payslip and my holiday pay (the 13th and 14th month salary under my collective agreement) would arrive with the next payment run.

A few days later, nothing had arrived.

I chased it. Promises were made. Nothing came.

I sent a formal ultimatum: pay everything within a few days or I would take legal action, including statutory interest at 9.2% above the base rate under Austrian law.

The salary arrived about two weeks late. The holiday pay was still missing.

The Arbeiterkammer took over my legal representation and sent a formal letter demanding the outstanding holiday pay under the metal industry collective agreement, late-payment interest under § 49a ASGG, a corrected payslip, and a corrected employment reference. That last point mattered: the company had described my work as "supported" rather than "independently developed and implemented." Under § 1163 ABGB, employment references must be benevolent and factually accurate. "Supported" was neither, given that I had been the only developer on the product for the majority of my time there.

The money arrived a month or so later. The reference was still wrong and the corrected payslip never came. The AK escalated to a lawyer, and a formal labor court claim was filed, worth EUR 2,400: one claim for the missing payslip, one for the corrected reference.

A few months later, the company's lawyers sent a settlement offer. It included paying EUR 150 in costs and fixing the reference, but it also came bundled with a permanent silence clause, a mutual non-disparagement agreement, a requirement to delete any public reviews on platforms like Kununu, and a general release of all claims. The deadline to accept was the next day at 10am.

I rejected it.

My lawyer called me thirty minutes before the court hearing was scheduled to begin. I was already suited up and ready to leave for the courthouse. The company had just delivered the corrected reference and the missing payslip. The case was resolved without a settlement and without any of the additional conditions.

The Data That Followed Me

I thought the story ended at the courthouse. It didn't.

About a year after leaving, the company shared my personal data, including a negative assessment of my personality, with a third party outside the EU, without my knowledge or authorization. I found out by accident. Every time I think this chapter is closed, something surfaces again.

What I'd Do Differently

Looking back, most of the warning signs were visible before I started. Some I noticed but dismissed. Some I simply didn't know to look for. Here's what I'd tell myself now.

1. If the company hasn't ordered your laptop before your first day, pay attention. It sounds minor. It isn't. Onboarding preparation reflects how a company actually operates, not how it describes itself.

2. The hiring process is a signal, not just a hurdle. Months of disorganized rounds and an interviewer who missed multiple sessions without explanation told me something about how this company functioned. I read it as normal friction. I'd take it more seriously now.

3. A salary reduction without a conversation is worth addressing. When the offer came back slightly lower with no explanation, I let it go. I'd ask about it directly next time, not because the amount was significant, but because how a company handles that moment says something about how it handles everything else.

4. Ask for specifics about financial health, not reassurances. "Financially stable" and "perfect" are adjectives, not evidence. Ask about runway, funding rounds, revenue, burn rate. If the answers are vague or enthusiastic without substance, that's worth noting.

5. Confirm who is actually on the team, and in what capacity. I was told I was joining an existing team. Within weeks, I was the only developer. Asking "who specifically will I work alongside, and are they permanent employees?" would have given me a much clearer picture.

6. Understand why a contractor was paused or let go. When the external team was put on a break, I absorbed the work without asking why the decision had been made. That context would have told me something important about where the company's finances actually stood.

A Fair Note to End On

I have worked at different companies, each with their own strengths and weaknesses. None of them came remotely close to what I experienced here. I also know that there are genuinely good startups out there, places where leadership is honest, contracts are fair, and when things go wrong, they go wrong for understandable reasons.

The problems I ran into weren't inherent to startup life. They were the result of specific decisions made by specific people. Most of those decisions followed the same pattern: saying something reassuring instead of saying something true.

What I take away isn't cynicism about small companies. It's a more specific calibration: the gap between what someone says and what the facts show is itself information. "Perfect" and "not great but we're working on it," spoken months apart about the same business, don't sit on a spectrum of honest communication.

Pay attention to that gap. Earlier than I did.