The best day in a week, and it wasn't from studying harder — it came from asking what actually matters right now instead of how much I could force in.
Day 22 of the journey to find a new job.
Today was probably the best day I've had in the last week.
Not because I suddenly studied for ten hours.
Not because I completed all the goals I had missed last week.
And not because I found a magical solution to my consistency problem.
It was better for a much simpler reason.
I stopped trying to force myself to study and started focusing on what actually mattered.
Last week, I spent a lot of energy trying to push myself.
Study more.
Solve more questions.
Sit longer.
Complete more targets.
But somewhere along the way, the act of forcing myself became the problem.
The more I told myself that I had to study, the more resistance I felt.
This week, I'm trying something slightly different.
Instead of asking, How much can I study today?
I'm asking:
What are the things that actually matter right now?
And then giving those things enough space in my day.
Today, I solved a few React and machine-coding questions. I also organized my work better throughout the day.
I went out.
I cooked.
I completed other things that needed attention.
And because those things were no longer sitting in the back of my mind waiting to be done, I was able to sit down and focus better when it was actually time to work.
That seems obvious when I say it now.
But I've spent the last few weeks trying to solve a productivity problem by simply adding more study hours.
Maybe the problem was never the number of hours.
Maybe it was how I was organizing everything around those hours.
There is another change I'm making this week.
I'm trying to be more strategic.
I know that I am comfortable with system design, architecture, and performance-related discussions.
Those are areas where I already have experience and confidence.
But the goal right now isn't to become equally good at everything.
The goal is to get the next job.
And for the kind of roles I'm targeting — frontend-heavy SDE roles — that means I need to be extremely comfortable with a different set of skills.
React.
JavaScript.
Machine coding.
Writing code quickly.
Writing code correctly.
Explaining decisions while building.
And being able to handle performance discussions when they come up.
The interesting part is that I don't think I'm missing the knowledge.
I think I've lost some of the muscle memory.
Over the last few years, and especially with AI becoming part of everyday development, the way we write code has changed.
We still understand what needs to be built.
We still understand architecture.
We can still reason about the problem.
But sometimes we don't manually write enough code anymore.
The small pieces.
The syntax.
The implementation details.
The repeated patterns that once came automatically.
That muscle memory slowly starts drifting away.
And interviews expose that immediately.
You might know exactly what needs to be done, but knowing isn't enough if you can't translate it into working code quickly under pressure.
So that's the focus for this week.
Getting my hands dirty again.
React machine coding.
JavaScript.
Implementation.
Repeated practice.
I don't think it will take very long to get it back.
A week of focused practice should be enough to make a significant difference.
And right now, that is probably a better use of my time than trying to cover everything at once.
There is some good news on the interview side as well.
Right now, I have three potential interviews for this week.
Two are already scheduled.
One is likely to be scheduled.
That's something to look forward to.
More interviews mean more opportunities to test the preparation.
And honestly, that's what I need right now.
I can prepare endlessly in isolation, but eventually the interview itself is where I discover the gaps.
Every interview tells me something.
Sometimes it's a React fundamental I need to revisit.
Sometimes it's machine coding.
Sometimes it's communication.
Sometimes it's simply execution under pressure.
The goal is to keep getting those opportunities and improve from each one.
At the same time, there is something that feels a little alarming.
For the last seven working days, I haven't received any calls through Naukri.
Earlier, after optimizing my profile, I was receiving a reasonably good number of recruiter calls.
Now that flow has slowed down.
That matters because Naukri had been performing well as one of the sources of interview opportunities.
So this is something I need to investigate again.
What changed?
Did the profile lose visibility?
Are the keywords no longer working the way they were?
Do I need to update the profile again?
Or is it simply a temporary slowdown?
Whatever the reason is, I need to look at it.
Because the job search isn't just about preparing for interviews.
It's also about making sure that the opportunities keep coming.
Preparation without interviews is incomplete.
And interviews without preparation are wasted opportunities.
Both sides need to keep moving.
And yes, I'm still building my project.
I've mentioned it several times throughout this series because it has become part of my own job-search journey.
The idea behind it is not to tell people exactly how they should learn.
I don't think learning works that way.
Everyone has a different approach.
Some people follow structured sheets.
Some follow interview lists.
Some solve problems based on patterns.
Some simply solve as many problems as they can and gradually build intuition.
I don't think there is one system that works for everyone.
So that's not what I'm trying to build.
Instead, I'm trying to optimize the process around finding a job.
The different steps.
The tracking.
The applications.
The opportunities.
The follow-ups.
The things that usually get managed manually.
The idea is to make the entire journey of finding a job simpler and faster.
Of course, this is also where I need to be careful.
I've already seen how easily the project can take over my preparation.
With AI especially, building becomes incredibly tempting.
You get an idea.
You can prototype it quickly.
You get another idea.
You improve it.
And suddenly you're three hours deep into something that wasn't even part of your plan for the day.
So the project stays.
But it cannot become the main path right now.
The job is still the priority.
Maybe once I get through this process myself, test the system properly, and understand whether it actually works, I can make parts of it public.
But first, I need to prove it on my own journey.
Day 22 feels different from the last week.
Not because everything is suddenly fixed.
But because I'm no longer trying to win by doing everything.
I'm trying to win by doing the right things.
Last week, the question was:
How much can I do?
This week, the question is:
What matters most right now?
For the moment, the answer is clear.
Get better at React and machine coding.
Rebuild the coding muscle memory.
Prepare according to the roles I'm actually targeting.
Keep the interview pipeline moving.
And continue building the project without allowing it to take over the primary goal.
Three potential interviews.
A clearer preparation strategy.
And a better day after a difficult week.
That's a good place to restart from.
Day 22 done.
This week, I don't want to do more. I want to do what matters.
Comments