Second round cleared, and a final round with the Engineering Manager waits tomorrow — a different kind of preparation than getting the code right.
The interview process has started to change shape.
There are no new interviews scheduled yet for this week, and the pipeline is quieter than I would like. But one of last week's interviews moved forward, and that has changed where my attention needs to go.
I cleared the second round.
Now there's a final round with the Engineering Manager tomorrow.
What's interesting is how different this feels from the beginning of the journey.
When I started, even getting through the first round felt like the main challenge. Then, after a few interviews, I started understanding where I was making mistakes and what the second rounds were actually testing. The second round became the next hurdle.
Now I've crossed that one too.
And that has given me some confidence — not that every interview will automatically go well, but that I'm capable of adapting to the level of preparation each round demands.
The Engineering Manager round is a different kind of preparation.
I'm going back through the projects I've worked on, the decisions I've made, the problems I've solved, and the situations I've been involved in. I'm also spending time understanding the company itself — what it does, how it works, its culture, and why I would actually want to join.
For a senior role, the conversation isn't only about whether I can write code.
It's also about how I work with people.
How I communicate.
How I make decisions.
How I handle disagreements.
How I resolve conflicts.
How proactive I am.
And whether I can explain the things I've built and the reasoning behind them.
That's probably the biggest difference I'm noticing between this job search and my previous switch.
Earlier, there were roles where the primary question was essentially whether I could do the job. At the senior level, the evaluation becomes broader. Technical ability is still important, but the interviewer also needs to understand how I operate when the problem isn't purely technical.
And there's something else I'm trying to remind myself before tomorrow.
Even if the interview doesn't go the way I want, it doesn't erase everything I've learned so far.
Every round has taught me something about what companies expect, where I communicate well, where I hesitate, and how I behave under pressure.
Of course, the goal is still the same: I want the offer.
But I don't want the outcome of one interview to determine how I see the entire journey.
Tomorrow, I'll prepare as much as I can. I'll go through the projects, think through the common questions, understand the company, and make sure I can clearly explain why I want to be there.
After that, the rest is a conversation.
I can't predict what questions will come, how long the discussion will last, or exactly what the interviewer will be looking for.
What I can control is whether I walk into that conversation prepared and communicate what I actually know.
That feels like a much better place to be than where I started.
Day 36 done.
Comments