You are sitting in an interview.
The interviewer asks:
"How would you design this system?"
Your brain immediately starts searching for the perfect answer.
- What technology should I mention?
- What architecture do they expect?
- What keywords are they looking for?
The pressure builds.
But professional problem-solving does not normally happen like that.
Real problems need questions
If someone gives you an unclear requirement at work, you would ask questions.
So do that in an interview.
Ask:
"How many users are we expecting?"
"Does this need to work in real time?"
"What are the reliability requirements?"
"Is this replacing an existing system?"
Those questions are not avoiding the answer.
They are part of the answer.
Explain your reasoning
An interviewer may care less about whether you immediately choose their preferred technology and more about whether you can explain why you chose it.
Talk through your thinking.
- What assumptions are you making?
- What trade-offs exist?
- What would you validate?
- What could go wrong?
- How would you test it?
That is closer to real professional work.
It is okay to say "I do not know"
There is a difference between giving up and acknowledging a knowledge gap.
You can say:
"I have not worked with that technology directly. I would start by understanding the documentation and building a small example. Based on what I know about the underlying concept, I would expect..."
That answer tells the interviewer how you learn.
Your mistakes can become useful
If you realise halfway through your answer that an assumption was wrong, correct yourself.
Say:
"Actually, that changes my approach. If the system needs to support real-time updates, I would reconsider the earlier design."
That demonstrates adaptability.
Professional work involves changing your mind when new information appears.
Do not perform expertise
Trying to sound like an expert can backfire.
You do not need to use complicated terminology.
You need to demonstrate understanding.
Clear explanations are usually more useful than impressive vocabulary.
AI can create another trap
If you have used AI to practise, you may encounter beautifully structured answers.
Do not assume that reproducing those answers makes you sound strong.
If you cannot explain the answer when the interviewer asks a follow-up question, the preparation has not helped enough.
Use AI to understand.
Then explain in your own words.
The lighthouse gives you a way to think
You do not need to pretend you can see every wave.
You need to show that you know how to navigate.
There is no prize for sounding certain when you are not.
Show how you think, how you learn and how you make decisions.