I started my first job at a startup at the beginning of January.
The pay was low, the commute was long, and I knew it wasn’t ideal. I told myself it was temporary. I wanted exposure, real responsibility, and a chance to operate inside a fast-moving environment instead of just preparing for one.
At first, it delivered exactly that.
The early momentum
The first week or two felt exciting. Things moved quickly. Decisions were made fast. Features shipped almost immediately. I had responsibility, context, and a feeling of being “in the game.”
It was energizing to see something go from idea to production so quickly. I respected the ambition behind it. Speed, when it works, is intoxicating.
But once the product went live, a different pattern started to emerge.
When speed loses structure
Bugs began appearing in clusters. Not subtle edge cases, but issues that pointed to deeper instability. There was no clear ownership of the system, no consistent handover, and no stable structure to build on. Requirements shifted frequently, sometimes within the same day.
When I suggested slowing down slightly to break problems into parts, define responsibilities, or reduce over-reliance on automation while things were unstable, those suggestions didn’t land as technical input. They were taken personally.
Over time, certain comments started becoming routine.
Being referred to as “the engineer” in a mocking way, while I wasn’t allowed to touch the code and was instead expected to fix things through prompts alone. Being told that if I really knew what I was doing, I would just be handed the tool and everything would magically work. Or that the solution to recurring issues was simply to “write a better prompt.”
Individually, these comments might sound small. Together, they changed the tone of the environment.
What was hard wasn’t disagreement. It was the erosion of trust. I was expected to fix things end to end, but not trusted with real ownership. Responsible enough to take pressure, but not respected enough to shape the system. That gap matters more than people realize.
For a while, I did what most junior engineers do in situations like this. I started doubting myself. I wondered if this was just a skill gap I hadn’t closed yet, or if I was expecting too much too early.
But the doubt didn’t come from the work itself. It came from being held responsible without being trusted, and from being asked to deliver outcomes without being given ownership. Once I separated those things, the self-doubt lost its grip.
The day it became clear
There was one day, right around launch, when everything seemed to pile up.
A technical discussion turned tense. On the way home, my bike broke down and I spent hours just trying to get back. When I finally did, even something small at home failed in an oddly timed way.
None of these things were dramatic on their own. But together, they felt like a signal. Not in a mystical sense. Just a clear reminder that I was stretched thin, absorbing more stress than I had space for.
I took that day at face value, rested, and paid attention to what my body had been telling me for a while.
When my body reacted before my brain did
I didn’t immediately label the situation as unhealthy.
My body did that first.
I started feeling a constant sense of dread before going in. Nausea on the commute. Mouth ulcers showing up out of nowhere. Sleep that never really felt like rest. Anxiety spikes that didn’t match the size of the problems on paper.
That’s when I realized I wasn’t learning cleanly anymore.
I wasn’t curious. I wasn’t experimenting. I was bracing.
There’s a difference between being challenged and being stuck in survival mode. Once I noticed that line had been crossed, it became harder to ignore.
On top of that, payments were delayed. I had to follow up multiple times to get paid. I found myself counting days instead of thinking about growth.
That was the point where the decision became obvious.
Why I left
I didn’t leave because I can’t handle pressure.
I left because pressure without structure isn’t growth.
Speed without clarity isn’t learning.
And low compensation combined with high chaos and no ownership creates a negative return on effort, no matter how much ambition is involved.
The hardest part wasn’t resigning. It was accepting that endurance isn’t the same as progress.
What the month gave me anyway
Despite everything, the month wasn’t a waste.
Being inside an early-stage environment taught me things I wouldn’t have learned from the outside. I saw firsthand how important clear systems, ownership, boundaries, and basic respect in the workplace are for any business to function.
I learned how fragile things become when structure is missing, and how quickly people burn out when everything depends on one person’s control.
I also learned softer but equally important skills. How to communicate in high-pressure environments. How to detach emotionally when things aren’t in your control. How to extract learning even when the environment isn’t ideal.
I got exposure to how startups think about branding, pitching, hiring early talent, and approaching growth and funding. Even watching what didn’t work gave me a clearer picture of what I’d want to do differently in the future.
Those lessons will matter.
Ending in a better place
What made it possible to leave was knowing I wasn’t trapped. During this period, I kept moving forward elsewhere. I advanced through multiple hiring processes, secured an offer from a larger organization, and opened parallel paths that gave me real choice.
That changed everything.
I could step away without panic. Without burning bridges. Without tying my self-worth to a single environment. The decision came from clarity, not desperation.
I don’t see this month as a failure. And I don’t see it as a hero story either.
It was a systems mismatch.
A lesson in boundaries.
It reminded me that tools don’t replace discipline, and speed doesn’t replace structure. Engineering fundamentals, ownership, and clear systems matter more than how fast something ships.
Most importantly, it reinforced something I want to carry forward early in my career: bad systems can quietly make capable people doubt themselves. Good systems do the opposite. They expand confidence instead of eroding it.
Leaving wasn’t about quitting.
It was about choosing not to let the wrong environment define who I become next.
I can totally relate as I worked in a startup environment with no clear structure and I lasted only a couploe of months. I tried to change things but realised my energy was being spent for nothing as I wasn't being listened to. My next job did the opposite and gave me the support and structure I needed to grow as a developer.
Every experience, negative or positive, is a learning. I like how you frame that here.