Can I Get a Job in 35 Days? — Speed Training Myself Till I Get Placed, Day 13
August 29, 2026
This is Day 13 of this series.
But tomorrow, I’m starting something that feels a little more serious.
A 35-day challenge.
The challenge starts on August 30, 2026.
The question is simple:
Can I get a job in 35 days?
I don’t know.
That’s kind of the point.
First, sorry.
My inconsistency took over again.
But I’m back.
And this time, I don’t want to wait until I’m perfectly consistent to start showing up.
As decided, I worked, learned, and applied.
I even got rejected.
And honestly?
I don’t think I’m as capable as I should be right now.
Not because I don’t know things.
That’s actually the frustrating part.
I’ve studied DBMS. I’ve studied OS. I’ve worked with Python. I’ve built projects. I’ve solved a decent number of DSA problems.
I know a lot of things.
But knowing something and being able to explain it precisely, under interview pressure, are two very different things.
That’s the gap I want to fix now.
I need polishing, not another giant roadmap.
I don’t want to complicate my life with another 17-step productivity system.
So I’m keeping this ridiculously simple.
For the next 35 days, I’m going to drill these subjects:
- DBMS
- SQL
- CN
- OOP
- OS
- Python
- Flutter/Dart
- Android
- Java
I’ll give AI the context it needs about me and my preparation, and then I’ll let it interview me.
Not explain things to me.
Question me.
I’ll have two interview sessions every day, roughly 1–1.5 hours each.
I’ll focus on one subject for two days before moving to the next.
And I’ll document the sessions.
The goal isn’t to memorize 500 interview questions.
The goal is to reach the point where if someone asks me something I supposedly know, I can actually explain it clearly, precisely and confidently.
That is currently missing.
Communication isn’t my biggest problem.
Confidence isn’t either.
Clarity is.
And that’s what I’m going after.
DSA gets harder too.
I’ve reached a point where Easy and Medium problems are becoming relatively comfortable.
So I don’t think solving more of the same is going to help me much.
I’ll continue doing a 90-minute contest every morning.
But now I’ll deliberately pick 4 Medium/Hard/Hard problems.
And yes, I’m giving myself permission to look at solutions.
The goal isn’t to maintain a perfect “solved without help” record.
The goal is to force myself to see harder patterns.
If I can’t solve something, I’ll study the solution, understand why it works, and move on.
Hopefully, after doing this enough times, the things that currently look like magic will start looking familiar.
And I’ll actually build something too.
I’ll be working on my Razorpay Buildathon project alongside all of this.
So the rough structure is:
Morning:
90-minute DSA contest.
During the day:
Interview drilling.
Later:
Razorpay Buildathon/project work.
End of the day:
I’ll dump the resources, questions, notes and useful chats here.
No fancy system.
Just a public record of what I’m doing.
And because I know myself, I’m not going to promise that I’ll do this perfectly every single day.
I’ve already tried that.
Instead, I want to see whether I can become someone who comes back quickly after missing a day.
That’s probably a more useful skill anyway.
The 35-day experiment
So, starting tomorrow — August 30, 2026 — this officially becomes Day 1.
Not Day 1 of my journey.
I’ve already been doing this for a while.
Day 1 of the 35-day challenge.
For the next 35 days, I’ll document what I learn, what I get wrong, what I build, what I apply for, the interviews I get, and, inevitably, the things that don’t work.
I don’t know what Day 35 will look like.
Maybe I’ll have an offer.
Maybe I’ll still be applying.
Maybe I’ll have learned far more than I expected.
Maybe I’ll have to start another 35 days.
But I want to find out.
And I’m going to find out publicly.
I’ll also experiment with what I share along the way:
- Interview drilling sessions
- Things I got embarrassingly wrong
- Weekly LeetCode Q3/Q4 breakdowns
- DSA patterns I finally understood
- Buildathon progress
- Resources that actually helped
- Applications and interviews
- And hopefully, eventually, the offer itself
I don’t know whether this will get traction.
I’m going to try anyway.
Because right now, I care more about getting better and getting hired than making everything look impressive.
So here we go.
Day 13 of the series.
Day 1 of the challenge.
35 days.
One question:
Can I get a job in 35 days?
Let’s find out.
My goal is still ridiculously simple:
Become so good that rejecting me becomes difficult.
