I thought working at a big MNC was a privilege.
It looked like the sensible version of success. A respected company. A stable role. A clear title. A path that other people could understand without needing an explanation.
Then, on the day I had decided to resign, my manager told me I had received a raise.
I had walked in ready to say that I was leaving. Before I could get to it, he shared the good news. For a moment, every emotion arrived at once. Relief. Gratitude. Doubt. Guilt. Excitement. Fear.
I thanked him.
Then I told him I was quitting.
This sounds like a story about money.
It is not.
The question was never money
Money was never the reason I stayed, and it was never the reason I left.
I did not dislike working. I was willing to work hard. I wanted difficult problems, responsibility, and the pressure that comes with becoming better. But effort by itself is not growth. Being busy is not the same as moving forward.
A job is an exchange of more than salary. I give it my time, energy, attention, and some of the most important learning years of my life. In return, I need more than a monthly deposit. I need new skills. Better judgment. More ownership. A steeper learning curve. I need to feel that the person leaving work today knows something the person who arrived in the morning did not.
The question that kept following me was not, “Am I earning enough?”
What am I becoming by staying?
And slowly, I stopped liking my answer.
I was living in two versions of software
My problem was not the work itself. My problem was what I was no longer gaining from it.
The environment felt old school. Even tools such as ChatGPT and Claude were blocked on the office network. Outside work, I was already using AI assistants across my personal projects. I used them to explore ideas, understand unfamiliar code, debug faster, compare approaches, and move from a rough thought to something real.
Inside the office, I went back to writing and investigating almost everything manually. Work that I knew could move faster took much longer. It felt like I was living in two different eras of software development every day.
This was never about asking AI to think for me. It was about shortening the distance between a question and a useful answer. I still had to understand the system. I still had to review the code. I still owned the result. But I had seen how much faster a developer could learn and iterate with the right tools, and I could not unsee it.
Every change waited for permission
There were approvals for almost everything.
Even when the code worked, I could not simply push it forward. I had to wait. I could not always implement an idea in the way I believed was best. I needed approval for the approach, approval for the change, and approval for the next step.
Some of that process exists for good reasons. Enterprise software needs reviews, controls, testing, and accountability. I understood that. I was not expecting to treat a company system like one of my personal repositories.
But over time, the process stopped feeling like a safety net and started feeling like a ceiling.
I was not angry that a large company had rules. I was worried about what staying inside that pace was doing to me. The world outside was moving quickly. Cursor, Claude Code, Codex, and a new generation of AI tools were changing how software could be built. I wanted to explore that shift deeply, not watch it through a firewall.
I realised the safe choice had its own risk
Leaving a stable job sounds risky. It is risky.
But staying also had a cost. Every month I stayed comfortable was another month in which I was not testing how far I could push myself. I had products I wanted to build. I had ideas I kept returning to after work. I had a way of working that made me feel awake, curious, and fast.
In my twenties, the resource I was most afraid of losing was not money. It was momentum. These were the years when I could take a risk, recover from being wrong, and learn without needing every decision to look sensible from the outside.
I started to understand that large company life was probably not the right fit for me, at least not at this point in my life. The scale was impressive, but the speed was not mine. The structure was sensible, but I wanted ownership. I did not only want to complete assigned work. I wanted to decide what deserved to exist and then take responsibility for making it real.
Eventually the question became very simple.
What could really go wrong? I was still in my twenties. If there was ever a time to bet on myself, this was it.
The raise made the decision clearer
The timing was almost too perfect.
A raise is supposed to make leaving harder. For me, it did not. The timing felt surreal, but I had already made the decision. I appreciated the recognition, but there was no new debate in my head. A higher number was never going to change why I was leaving.
The raise changed the number, not the direction.
I was not leaving for more money. I was not staying because of money. The raise simply proved it. What I wanted could not be added to a payslip. I wanted speed, ownership, exploration, and the freedom to discover how good I could become when my learning was no longer waiting for permission.
I was leaving because growth mattered more to me than comfort.
So I went through with it. I left the stable role, stepped away from the predictable path, and went all in on my own projects.
Did I regret it?
Absolutely fucking not.
That does not mean every day became easy. Building your own products replaces one kind of pressure with another. There is uncertainty. There are wrong ideas, failed experiments, technical problems, distribution problems, and days when progress is difficult to measure.
But I learned more than I expected. I explored technologies I might never have touched in my old routine. I built complete products instead of seeing only one part of a large system. I had to think about engineering, design, pricing, users, distribution, and whether an idea deserved to survive.
I also moved fully into AI assisted development. My workflow changed completely. I learned to give better context, question weak output, debug generated code, compare solutions, and use models as collaborators without handing them my judgment.
On the right problems, I felt like I was working twenty times faster. More importantly, I was learning at that speed too.
I did not quit work
I quit a way of working that no longer matched the person I wanted to become.
I still value what the job taught me. I learned how enterprise teams build, review, test, document, and release software. I worked with real systems and real constraints. Those lessons did not disappear when I resigned. They became part of how I build now.
But leaving gave me something I needed more at that moment: room to move.
I used to think the privilege was having a safe job at a large company. Now I think the privilege is being young enough to take a real risk, honest enough to admit when a path is wrong for you, and stubborn enough to build another one.
The day I got a raise, I quit my job.
It remains one of the best decisions I have made.