Before I Switched From My 9–5, I Did This
Everyone talks about resigning. Very few people talk about the preparation that happens months before that decision.
The Thought Stayed in My Mind for a Long Time
I still remember the first time I seriously thought about leaving my 9–5 job.
It wasn’t because I had a bad manager.
It wasn’t because I hated my work.
It wasn’t even because I wanted to become an entrepreneur overnight.
The thought came from something much simpler.
Every evening after work, I would open my laptop again. Not because someone asked me to, but because I genuinely wanted to build something of my own.
Some days it was a small backend project.
Some days it was a DSA platform.
Sometimes I would just spend two hours reading about distributed systems or improving my engineering skills.
I started noticing something.
No matter how tired I was after office hours, I still found myself opening my laptop again.
That’s when I realized this wasn’t just a hobby anymore.
It was becoming something much bigger.
But even then, I never thought, “I’ll resign next month.”
Instead, I asked myself a different question.
“What needs to happen before I can even think about leaving?”
Looking back, that single question probably saved me from making a very emotional decision.
Watching People Quit Made Me Realize Something
Around the same time, I started seeing a lot of posts on LinkedIn and Twitter.
Someone would announce,
“Today is my last working day.”
Another person would post a picture of their resignation letter.
A few weeks later they would announce their startup.
It looked exciting.
For a few days, I also felt like maybe I should just do the same.
But social media only shows the final chapter.
Nobody posts about the months of uncertainty before that.
Nobody talks about wondering whether they’ll have enough money six months later.
Nobody talks about the nights when they question whether they’re making the biggest mistake of their career.
The more I thought about it, the more I realized something.
I wasn’t interested in quitting my job.
I was interested in building a life where leaving my job became a natural next step.
Those are two completely different things.
I Made One Rule for Myself
That weekend, I opened my notebook and wrote down one rule.
“Don’t resign because you’re frustrated. Resign only when you’re prepared.”
It sounds simple.
But it changed the way I looked at everything.
Whenever I felt like quitting after a stressful day at work, I would read that line again.
Frustration lasts for a few hours.
A resignation lasts much longer.
I promised myself that I would never make a career decision based on one bad week.
If I ever left, it would be because I had spent months preparing for it.
Not because I had a bad meeting on Monday morning.
My Evenings Started Looking Different
Earlier, once work was over, I would relax, watch random videos, scroll through social media, and call it a day.
Slowly, that changed.
I gave myself a small target.
Just two hours.
No unrealistic schedules.
No “I’ll study eight hours after office.”
That never worked.
Some evenings I worked on a side project.
Some evenings I learned AWS.
Some days I practiced DSA.
Other days I read about System Design or tried to understand a technology I had been avoiding.
There were many nights when I didn’t feel like doing anything.
Office had already drained my energy.
But I made a promise to myself.
Even if I wasn’t productive for two hours, I would at least sit in front of my laptop.
Some days those two hours became twenty minutes.
Some days they became four hours.
The important part wasn’t the duration.
It was showing up consistently.
I Stopped Waiting for the Perfect Idea
One mistake I made in the beginning was thinking I needed an amazing startup idea before I started building.
So I kept waiting.
Every week I thought,
Get Himanshu Singour’s stories in your inbox
Join Medium for free to get updates from this writer.
“Maybe I’ll get a better idea next month.”
That month never came.
Eventually, I stopped chasing ideas.
Instead, I started solving problems I personally cared about.
If a tool didn’t exist, I built it.
If I found learning difficult, I created notes.
If I wanted a better way to study DSA and System Design, I started working on it little by little.
None of those projects were perfect.
Some never even got completed.
But every project taught me something.
How to deploy applications.
How to work with cloud services.
How to design better APIs.
How to fix production bugs.
How to deal with users.
More importantly, they taught me that building consistently matters far more than waiting for the perfect opportunity.
Money Was the Conversation Nobody Wanted to Have
For a long time, I ignored the financial side of leaving a job.
I only thought about passion.
Reality doesn’t work like that.
Rent doesn’t stop because you’re following your dream.
Bills don’t disappear.
Responsibilities don’t disappear.
I realized that if I wanted the freedom to make bold career decisions, I first needed financial stability.
So instead of rushing, I started saving.
Not because I expected to fail.
Because I wanted peace of mind.
Knowing that I could survive for several months without depending on my next salary completely changed the way I looked at risk.
Confidence doesn’t only come from skills.
Sometimes it comes from knowing you have enough time to recover if things don’t go according to plan.
The Biggest Lesson I Learned
Today, whenever someone asks me,
“How do I prepare before leaving my 9–5 job?”
I don’t tell them to resign.
I tell them to prepare until resigning feels obvious.
Build something while you’re still employed.
Learn skills that increase your value.
Save money.
Create habits that prove you can stay disciplined without someone managing your time.
If you can’t stay consistent for two hours after office, quitting your job won’t magically make you disciplined.
Freedom is amazing.
But freedom without discipline quickly turns into procrastination.
Looking Back
I’m glad I didn’t leave my job the first time I felt frustrated.
If I had, it would’ve been an emotional decision.
Instead, I spent months preparing quietly.
Nobody noticed those evenings.
Nobody saw the weekends I spent learning instead of going out.
Nobody celebrated the small milestones.
But those small efforts slowly built something much bigger than I had imagined.
Looking back now, I don’t think resigning was the hardest part.
Preparing for it was.
And that’s exactly why the transition felt less like jumping into the unknown and more like taking the next logical step.
If you’re thinking about switching from your 9–5, don’t ask yourself, “When should I resign?”
Ask yourself, “What can I start building today so that when the day comes, leaving feels like a decision not a gamble?”
That one question changed everything for me.
Maybe it’ll do the same for you.
If You’re Serious About Making the Switch
If you’ve read this far, chances are you’re thinking about something bigger than just changing jobs.
Maybe you want to become a better Software Engineer.
Maybe you’re preparing for AI Engineering roles.
Maybe you’re aiming for DevOps, SRE, or Backend Engineering interviews.
Whatever your goal is, one thing is true having a structured learning path makes a huge difference.
One of the biggest mistakes I made early in my career was learning random topics without any direction. I’d jump from one YouTube video to another, bookmark dozens of articles, and buy courses I never finished.
Progress became much faster once I started following a clear roadmap instead of learning whatever looked interesting that day.
That’s exactly why I built AlgorithmXlr8.
It isn’t just another collection of videos or interview questions. It’s a structured platform designed to help engineers master Software Engineering, AI Engineering, DevOps, DSA, System Design, and other interview-focused skills through a step-by-step learning path.
Everything is organized in the order you should actually learn it, so you always know what to study next instead of wondering where to begin.
If you’re serious about switching from your 9–5 job, growing as an engineer, or preparing for your next interview, I think you’ll find it genuinely useful.
You can explore it here: https://algorithmxlr8.io
