How to be Good at Interviews

How to be good at interviews? Start by changing the job of the interview.

An interview is not a performance in which you must look perfect.

It is a structured conversation in which both sides are trying to reduce uncertainty.

The interviewer wants evidence that you can do the work, learn what you do not yet know, communicate clearly and operate well in the real environment. You want evidence that the role, team, manager, expectations and opportunities fit what you can genuinely contribute and become.

The gold standard is therefore not charisma theatre. It is credible evidence delivered clearly under pressure.

Did You Know? Strong Interviews Are Built Before the Interview

The most confident-looking candidate is not automatically the strongest.

Good preparation changes the interview because the candidate arrives with a map.

That map includes:

what the role actually requires;
which experiences prove relevant capability;
which gaps need honest explanation;
what questions remain about the employer;
which stories can demonstrate judgment, teamwork, learning and results.

Preparation reduces improvisational load.

Instead of inventing an answer, you retrieve a relevant piece of evidence.

The Gold-Standard Interview Loop

Research — understand the role and organisation.
Map — match requirements to your evidence.
Select — choose strong examples.
Structure — make answers easy to follow.
Rehearse — practise aloud under realistic conditions.
Listen — answer the question actually asked.
Clarify — check ambiguity.
Respond — lead with the point, then evidence.
Ask — use your questions to evaluate the role.
Review — improve after each interview.

Step 1: Read the Job Description Like a Problem

Do not treat a job description as decorative text.

Extract the requirements.

Create four columns:

Requirement — what the role appears to need.
Evidence — where you have demonstrated it.
Gap — what you have not yet done.
Transfer — which adjacent experience may still matter.

This prevents generic preparation.

Step 2: Build an Evidence Bank

Before the interview, prepare real examples from your experience.

Useful categories include:

solved a difficult problem;
improved a process;
handled conflict;
worked with limited information;
learned something quickly;
made a mistake and repaired it;
led without formal authority;
delivered under time pressure;
worked with a difficult stakeholder;
changed your mind after new evidence.

Do not memorise polished speeches.

Know the facts of the example deeply enough to explain them naturally.

Step 3: Use a Clear Answer Structure

Behavioural questions benefit from structure because stories can wander.

A familiar structure is STAR: Situation, Task, Action, Result.

Use it as a scaffold, not a cage.

A strong answer usually makes four things clear:

What was happening?
What were you responsible for?
What did you personally do?
What changed as a result?

Then add one more question when useful: What did you learn?

Step 4: Lead With the Answer

Many weak interview responses contain useful information but make the listener wait too long to find it.

If asked, “How do you handle competing priorities?”, begin with your principle.

For example:

“I separate deadlines from business impact, identify dependencies and confirm trade-offs early with the relevant stakeholders.”

Then give the evidence.

This is point → proof.

Step 5: Quantify Carefully

Numbers can make evidence concrete.

Examples:

time reduced;
revenue influenced;
errors reduced;
students supported;
projects delivered;
turnaround time improved;
customer satisfaction changed.

But never invent metrics because you think interviews require them.

If the impact was qualitative, explain it honestly.

Credibility beats fake precision.

Step 6: Prepare for the Obvious Questions

Some questions appear frequently because they reveal useful information.

Tell me about yourself.
Why are you interested in this role?
Why are you leaving your current role?
What are your strengths?
Tell me about a difficult challenge.
Tell me about a disagreement.
Tell me about a mistake.
Why should we hire you?

Do not memorise one universal script.

Prepare the reasoning and evidence behind each.

Step 7: Prepare for Technical and Role-Specific Questions

General communication cannot substitute for technical competence.

If the role requires coding, finance, teaching, engineering, data analysis or operations, identify the likely tasks and practise them.

Ask:

What problems would someone in this role solve every week?
What knowledge is foundational?
What trade-offs would matter?
What could be tested live?

Interview preparation should resemble the work when possible.

Step 8: Rehearse Aloud

Thinking an answer silently is not the same as speaking it.

Practise aloud.

Listen for:

long openings;
missing point;
too much background;
weak evidence;
unclear ownership;
filler language;
unfinished endings.

Then shorten.

A strong interview answer is usually easier to understand than the first draft.

Step 9: Practise Follow-Up Questions

Real interviews do not always stop after the prepared answer.

Expect:

What happened next?
What would you do differently?
What was your specific contribution?
How did you measure success?
What did your manager think?
What was the hardest trade-off?

Follow-ups test whether the story is real and whether your thinking survives beyond the script.

Step 10: Listen Before Answering

A polished answer to the wrong question is still a weak answer.

Pause.

If the question is ambiguous, clarify.

For example:

“Would you like me to focus on the technical decision or on how I managed the team around it?”

That is not weakness.

It is communication.

Step 11: Handle Gaps Honestly

You will not have every requirement.

A credible answer can say:

“I have not owned that exact process before. The closest experience is X, where I had to learn Y quickly. I would expect a learning curve, and this is how I would approach it.”

This shows self-awareness and transfer.

Pretending experience creates risk.

Step 12: Prepare Questions for the Interviewer

Good questions help you evaluate the role.

Useful areas include:

What would success look like in the first six months?
What problems does the team most need this hire to solve?
How are priorities decided?
What does strong performance look like here?
What are the most difficult parts of the role?
How does the team give feedback?
What changed in this role over the last year?

Questions are evidence that you are evaluating the work, not merely trying to survive the conversation.

Step 13: Research the Organisation

Know:

what it does;
who it serves;
major products or services;
recent developments relevant to the role;
how the role fits the organisation.

Do not memorise flattering facts.

Use research to ask better questions and make your evidence relevant.

Step 14: Prepare Logistics

Reduce avoidable uncertainty.

confirm time;
confirm location or link;
test camera and microphone;
prepare documents;
plan travel;
know interviewer names if provided;
prepare a quiet environment for virtual interviews.

The night before is for reducing uncertainty, not rebuilding your entire career story.

Step 15: Handle Nerves Through Familiarity

Nerves do not automatically mean poor performance.

Reduce novelty.

Practise:

the first two minutes;
the most difficult question;
the technical task;
the closing question;
the virtual setup.

The aim is not to feel nothing.

The aim is to operate despite activation.

Step 16: Use AI as a Rehearsal Partner, Not a Biography Writer

AI can generate likely questions, challenge vague answers and simulate follow-ups.

But do not let it invent achievements.

A safe workflow is:

provide a truthful experience;
ask for difficult questions;
answer in your own words;
ask what is unclear;
verify that every revised detail remains true.

MyCareersFuture career guidance similarly notes that AI can support interview preparation while human judgment, authenticity and real practice remain important.

Step 17: Review Immediately Afterwards

After the interview, write:

What questions appeared?
Which answers were strong?
Where did I ramble?
What evidence was missing?
What did I learn about the role?
What would I change next time?

This turns every interview into training data.

Interviews for Students

Students may face scholarship, DSA, CCA leadership, internship or university interviews.

The same principles apply.

Do not manufacture adulthood.

Use evidence from:

school projects;
CCA;
volunteering;
sports;
competitions;
family responsibilities;
independent learning.

A small real example is stronger than a grand invented one.

Interviews for Career Changers

Career changers need to make transfer visible.

Do not only say, “I want a new challenge.”

Explain:

which skills transfer;
what new skills have been built;
why the target role fits;
what evidence supports the transition.

The interviewer needs a bridge between the old role and the new one.

Interviews for Technical Roles

Technical interviews often test both answer and process.

Explain:

what you understand;
what assumptions you are making;
which approach you are considering;
how you would verify.

A partially correct but transparent reasoning path can be more informative than silent guessing.

Common Interview Traps

Over-Rehearsal

Answers sound memorised and fail when the question changes.

Biography Dump

The candidate answers “Tell me about yourself” with every job ever held.

Generic Enthusiasm

“I love your company” without evidence or role-specific reasoning.

Fake Weaknesses

Using disguised strengths rather than a real learning area.

Blaming

Speaking negatively about former colleagues instead of explaining the situation professionally.

No Questions

Treating the interview as one-way evaluation.

Invented Numbers

Creating metrics for impact that was never measured.

A 30-Day Interview Scaffold

Week 1: Evidence

Map role requirements.
Build eight evidence stories.
Identify gaps.

Week 2: Structure

Practise concise introductions.
Use STAR flexibly.
Prepare technical examples.

Week 3: Pressure

Run mock interviews.
Practise follow-ups.
Record and review answers.

Week 4: Precision

Research target employers.
Refine questions.
Practise logistics and closing.

How to Measure Improvement

Are answers shorter and clearer?
Does every claim have evidence?
Can you adapt stories to different questions?
Do you listen fully before answering?
Can you explain gaps without defensiveness?
Are your questions becoming more useful?
Do you recover smoothly when surprised?

Frequently Asked Questions

How long should interview answers be?

Long enough to answer clearly and provide evidence, but short enough that the interviewer can follow and ask more. Many answers improve when the point appears early.

Should I memorise answers?

Memorise facts and evidence, not a rigid script.

What if I do not know an answer?

Say what you know, clarify the question, explain how you would approach the unknown and avoid bluffing.

How should I answer “Tell me about yourself”?

Give a short professional story connecting your current experience, relevant capability and reason for this role.

Should I ask about salary?

Compensation is a legitimate part of evaluating work. Timing depends on the hiring process and context; stay factual about what is being discussed.

Can AI help me prepare?

Yes. Use it for rehearsal, question generation and critique, while keeping every biographical claim truthful.

Helpful Reading Inside eduKate

Singapore Career Resources

Good interviews are built from evidence.

Understand the role. Map your experience. Prepare real examples. Structure answers. Practise aloud. Listen carefully. Ask useful questions. Review after every attempt.

The gold standard is not a flawless performance.

It is a truthful, clear and well-prepared conversation that helps both sides make a better decision.

Continue the series with How to be Good at Goal Setting, How to be Good at Self-Discipline and How to be Good at Money Management.

Properly taught kids shine a bright light into the future.