Tell me about a time you had to explain a technical constraint to a product manager or a non-engineer, and they did not want to hear it.
What they are really testing: They want to know if you can translate infrastructure reality into business language without hiding behind jargon or simply giving up. Junior engineers often either cave or lecture.
A real interview question
Tell me about a time you had to explain a technical constraint to a product manager or a non-engineer, and they did not want to hear it.
What most people say
drag me
“I told the PM it was not technically possible and that they did not really understand how the database works.”
It centres blame on the other person, gives no translation, no options, and no outcome, which reads as an engineer who cannot be trusted in front of stakeholders.
The follow-ups they ask next
What if the PM had insisted on the one second refresh anyway?
Say you would put the cost and the delivery date in writing, escalate calmly with the trade-off, and let the business decide with eyes open.
How did you know 15 minutes was the real limit?
Point at a measurement you actually took, the batch job duration or the warehouse load time, not a guess.
What the interviewer is listening for
- Measured the constraint before arguing about it
- Translated the limit into cost and time, not schema talk
- Offered several options with different trade-offs
- Owned the outcome and named a concrete delivery time
What sinks the answer
- Blames the PM for not being technical
- Says impossible without ever quantifying anything
- Gives a flat no with no alternative path
- Story ends with nobody deciding anything
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“I have not had this exact situation, but here is how I would reason about it. First I would measure the actual limit so I am arguing with numbers, then I would explain it in terms of cost and dates, then I would bring two or three options rather than a wall, and let the business pick.”
Keep going with behavioural
Foundation
Tell me about a time you had to learn a new technology quickly. How did you go about it?
Foundation
So, why cloud? You have not worked in cloud before, so walk me through what actually pulled you here.
Foundation
Why are you leaving your current job?
Foundation
Tell me about a time you noticed something was broken, wasteful or risky, and nobody seemed to own it. What did you actually do?
Junior
You join a team and inherit a service with no documentation and the original author has left. Walk me through your first week.
Junior
Describe a time you were blocked and there was genuinely nobody available to ask. What did you do?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free