I split the day into four fixed six-hour blocks, and the win wasn't hours or questions covered — it was moving through the day without negotiating with myself.
Day 29 of this journey to finding a new job was probably one of the most productive days of the entire month.
And I think something is changing now.
For the last twenty-eight days, one of my biggest problems was not that I didn't know what to study. I always knew what needed to be done. There were React and JavaScript machine-coding questions, system design, performance, observability, DSA, interview preparation and many other things that I wanted to cover.
The problem was deciding what to do when.
When everything is important, nothing really gets a proper place.
I would wake up and think about what I should study. Then I would start with one thing, remember something else, switch to another topic, get an idea for a project, work on that for some time and eventually reach the end of the day feeling like I had been busy but without being completely satisfied with what I had actually accomplished.
Today, I tried to change that.
Instead of planning individual tasks throughout the day, I divided my twenty-four hours into four different parts of six hours each.
The first part, from midnight to six in the morning, is for things that I want to explore. AI, new technologies, new ideas or anything that I genuinely want to learn outside the immediate interview preparation.
The second part of the day is focused on machine coding. React, JavaScript and writing code.
The third part is for design-related preparation — system design, frontend architecture, performance optimization, observability and similar topics.
And the final part is dedicated to DSA.
Now, I don't know whether this exact schedule will survive for the next few weeks. Maybe I will have to modify it. Maybe some parts of the day will need more flexibility.
But the idea behind it worked today.
For the first time in a long time, I was able to touch every important area of my preparation without constantly asking myself what I should be doing next.
That question itself takes a surprising amount of energy.
When you are preparing for something uncertain, especially something like a job search, your brain is constantly negotiating with you.
Should I solve DSA?
Should I prepare for the interview?
Should I work on the project?
Should I learn AI because the market is changing?
Should I revise React fundamentals?
Should I apply for more jobs?
Every option sounds important. And because every option has some value, it becomes very easy to keep switching between them.
Today, I tried to remove some of that negotiation.
There was a time for everything.
And once I knew what I was supposed to focus on during a particular part of the day, it became easier to simply start.
I think that was the biggest win of Day 29.
Not the number of hours.
Not the number of questions.
Not even the amount of content I covered.
The win was being able to move through the day without constantly feeling that I was ignoring something important.
Over the last month, I have tried many different strategies.
I tried forcing myself.
I tried setting very ambitious goals.
I tried starting slowly.
I tried taking smaller goals.
I tried working for longer hours.
I tried taking more breaks.
Some of them worked for a few days. Some didn't work at all.
But I think that is also what these twenty-nine days have been about.
We are not just preparing for interviews.
We are figuring out how we work.
There is a difference between knowing how to work and knowing how you work.
You can read ten productivity books and understand every concept inside them. You can know about deep work, habit formation, discipline, motivation, momentum and consistency.
But eventually, you still have to sit alone with yourself and figure out what actually helps you move.
For me, the biggest problem was probably lack of boundaries.
Everything was entering everything else.
My project entered my preparation time.
My preparation entered my leisure time.
Leisure entered my sleep.
And sleep affected the next day.
There was no clear separation.
And when there is no separation, every decision starts competing with every other decision.
The project is useful, so why not work on it?
AI is important, so why not learn it?
System design is important, so why not study that instead of React?
DSA is important too.
Suddenly, instead of having one day, you feel like you need five different days to do everything you believe is important.
But we only have one.
So now, instead of trying to fit everything everywhere, I want to give things their own place.
And today, that worked.
This week is also important from the interview perspective.
We have three interviews around this period. Two are first-round interviews, and one is expected to be a second round, which I am trying to get scheduled.
Tomorrow, I have one interview scheduled from three to four. Then there is another interview on Wednesday from five to six. And I will try to get the second round scheduled around Thursday.
So the next few days are going to matter.
But I don't want to repeat what I have done earlier.
Whenever an interview came closer, I would sometimes completely change my entire routine.
Everything else would stop.
I would try to squeeze as much preparation as possible into the available time.
And yes, sometimes that is necessary.
But I also think preparation works better when the base is already moving.
You cannot build momentum only when an interview appears on the calendar.
The preparation has to continue even when there is no interview.
The interview should only decide where we focus more.
And that is what I want to do now.
Keep moving across the important areas, build the foundation, and then increase the focus wherever the upcoming interview requires it.
Another thing I have been observing is the job calls.
We did not receive any calls today.
But based on what I have seen over the last few weeks, Tuesday and Wednesday usually seem to be better days.
Those are the days when I have received more calls and recruiter outreach.
So I am hoping that tomorrow brings one or two opportunities that can eventually turn into interviews for the following week.
Of course, there is no guarantee.
And I think this journey has already taught me not to attach too much emotion to individual days.
One day you get interview calls.
Another day you get rejection emails.
Another day nothing happens.
And then suddenly, an opportunity appears.
You cannot completely control the outcome.
But you can control whether you are ready when the opportunity arrives.
That is probably what this entire month has been trying to teach me.
For twenty-eight days, I kept talking about motivation, momentum, distractions, comfort zones and consistency.
Today, I don't feel like talking too much about motivation.
Because I don't think motivation is going to carry us through the rest of this journey.
Structure might.
A clear direction might.
And repetition definitely will.
There will still be bad days.
I am sure of that.
There will be days when this schedule doesn't work.
Days when I oversleep.
Days when I get distracted.
Days when I work on my project for longer than I should.
But hopefully, now there is something to return to.
A structure.
Not a prison.
Not a rigid timetable that makes me feel guilty if I miss one hour.
Just a direction.
A way of asking: What should I do now?
And then having an answer.
Day 29 was a good day.
Not because everything was perfect.
But because, for the first time in quite some time, the day felt like it had a rhythm.
We covered different areas.
We moved forward.
We did not spend the entire day negotiating with ourselves.
And right now, that is enough.
We are getting closer to Day 30.
One month into this journey.
One month of interviews, preparation, projects, distractions, good days, bad days, interviews that went well, interviews that did not, motivation that disappeared and motivation that came back.
And despite everything, we are still here.
So tomorrow, we continue.
One interview at a time.
One topic at a time.
One day at a time.
Day 30 is next.
And hopefully, we keep moving faster from here.
Comments