Intro: the other half of the equation
We like to think interview success is 90% on us. We grind LeetCode, memorize design patterns, and rehearse STAR. What about the other half of the equation? What if the interviewer is unprepared, asks canned questions, or is just serving time?
The industry talks endlessly about leveling up the candidate. Almost nobody talks about leveling up the interviewer. Today we unpack that gap — and, more usefully, a strategy to still look excellent in front of an unprepared interviewer.
While you read, practice dialogue, not a five-second answer: a mock with a live engineer and an express quiz that shows whether you actually understood the idea.
Why interviewers are losing the arms race
In the dinosaur era, interviewers loved asking how to delete a file named -f on Unix. It froze the candidate, and you could watch their brain work in real time.
That no longer works.
Candidates are better prepared than ever. Thousands of resources walk through every popular problem (Min Stack, URL Shortener, you name it). Invent a “new” question and it shows up in prep databases the next day.
The result: the candidate ships a perfect solution in two minutes. What did that tell us? Nothing. We do not know if they understood it or just memorized the answer.
Here is the real problem: candidates became professional preparers, while most interviewers stayed amateurs. At best they get a two-hour course and a couple of shadow interviews. That is nowhere near enough.
The interviewer’s main mistake (and your opening)
Many interviewers think the job is to ask a question and watch whether the candidate solves it in 35 minutes. That is the mistake.
The craft of interviewing is not the question. It is digging. A real interviewer takes your answer and starts probing the edges of what you actually understand.
If they do not do that, they are unfit for the role. How do you turn that weakness into your strength?
How to win when the interviewer is lost
Four moves we practice with readers of itcareergym.ru. This is not manipulation. It is clear thinking a weak interviewer will not extract on their own.
1. Don’t look memorized
An instant perfect answer to a hard problem makes a good interviewer suspicious and a bad one freeze. Your job is to show the thinking.
“I remember the classic solution — let me check why it works instead of just rewriting the code.”
Show that you understand what is under the hood. Interviewers who only wanted code get pulled into how you think. That is how you should sound on a mock: out loud, with pauses, no race to five seconds.
2. Use echo questions
If the interviewer asks a question and goes quiet (it happens a lot), do not rush to answer. Ask:
“Are we designing this for 1,000 RPS or for a single request?”
A weak interviewer did not think about that. Your question shows you are thinking wider than the prompt. You take the conversation. Load, consistency, cost of being wrong — the same clarifications as in write-ups like Amazon system design, only spoken on a mock.
3. Stretch the standard problems
If they ask about URL Shortener (a worn-out prompt), do not recite Wikipedia. Say:
“I can write the Base62 version in a minute. Let’s talk about expiring a billion stale links and how we geo-distribute this.”
That is going beyond the frame. You stop being a problem-solver and start sounding like an architect. For the interviewer it is a lifeline — they get a signal even if they cannot extract it themselves. Build that case once as a pet project instead of reciting Base62 from a cheat sheet.
4. Help the interviewer dig
After you answer, add: “If we change the language or the OS, the behavior changes because…” You offer follow-ups yourself (the rm -f example). The interview becomes a conversation, and you stick as someone with depth.
On the company side, digging is a skill of its own — we covered it in why interviewers make mistakes. On the candidate side it is simpler: do not wait for the probe. Put it on the table.
You cannot cram a conversation
Echo questions and “why this works” sound fake if you say them for the first time on a real loop. Try them with a partner first.
Why you should prep for a bad interview
For interviewers to get better, companies need incentives (bonuses, badges, promotions). Until that lands, you are interviewing today.
Keep in mind:
- Interviewers are people. They are often busy with their real job and do not want to spend time prepping.
- A bad question is not a bad outcome. If you can steer the dialogue, you can still get an offer on a raw problem.
- This is your opening. Most candidates freeze and answer from a template. A live mind that can reason stands out against 90% of the crammers.
How ItCareerGym helps you win
The product is not a drill for canned answers. We teach you to think like an interviewer.
- Trainers. We do not just hand you problems. We show the traps on each step and how to answer so even an unprepared interviewer sees you are the one. Start with quizzes.
- Mock interviews. We train you not to dump a perfect answer in five seconds, but to hold a conversation, ask questions, and sell your experience — on /find/.
- Strategy. Not only algorithms, but interview psychology. How to turn an interviewer’s red flag into a green one — including through STAR stories.
What to do right now
In a world where candidates prep like professionals and interviewers often prep like amateurs, the person who takes the lead wins.
Do not wait for the interviewer to score you. Leave them no choice but to score you high.
Want to steer any interview and still be ready for the hard problem? Start with an account and the first mock — in mocks you practise steering the conversation yourself.
FAQ
Tap a question — the answer opens below.
-
If I nail Min Stack in two minutes, is that a plus?
A strong interviewer gets suspicious. A weak one freezes. Say out loud that you will check why the solution works. That is what a mock trains — not a problem bank on speed.
Link to this answer -
They asked a question and went quiet. Answer immediately?
No. Clarify the load: 1,000 RPS or a single request. Echo questions show you think wider than the prompt. You only get that in a live mock.
Link to this answer -
Everyone already memorized URL Shortener. What do I say?
Not Wikipedia, not Base62 in a minute. Jump to expiring a billion stale links and geo-distribution. That is architecture — and you can show it as a pet project.
Link to this answer -
Why prep for a “bad” interview if companies promise to train interviewers?
Badges and bonuses will not land today. You interview now. A bad question is not a bad result if you steer the talk. The company side is in why interviewers make mistakes.
Link to this answer -
How is Gym different from a problem bank?
We do not drill a five-second answer. Trainers show traps; mocks teach you to sell experience. Start with registration and the first mock.
Link to this answer
Don’t wait to be scored
Take the conversation. Practice it on the platform while the interviewer is serving time at their day job.
Related: Why interviewers make mistakes · STAR stories · AI in interviews · Resume clarity