By Cyril KimbiThe questions asked in a graduate interview are remarkably consistent. What varies is how candidates answer them — and the difference between a good answer and a poor one is almost never intelligence. It is preparation of the right kind.
“Tell me about yourself”
Almost always first, and routinely wasted. It is not an invitation to narrate your life; it is an opening argument.
A structure that works: present, past, future. What you are doing now, the one or two things in your background that led there, and why this role is the next step. Ninety seconds, not five minutes.
What ruins it: starting at birth, listing your CV in order, or being so brief that the interviewer has to start over. The interviewer is deciding, in this answer, whether the rest of the conversation will be interesting.
“Why do you want to work here?”
This question sorts candidates faster than any other, because most answers are about the candidate rather than the employer.
“It would be a great opportunity for me to grow” describes what you get. It is true of every job, and it tells the interviewer nothing.
A strong answer names something specific and verifiable about the organisation — what it does, a project, a market it operates in, a way it works — and connects it honestly to something you have actually done or want to do. Specificity is the whole test. If your answer would survive a find-and-replace of the company name, it is not an answer.
“What is your greatest weakness?”
The purpose is not to catalogue your faults. It is to see whether you can assess yourself accurately and act on it.
Two failure modes: the fake weakness (“I work too hard”), which reads as evasion, and the disqualifying one (“I struggle with deadlines”), which reads as a warning.
What works is a real limitation, stated plainly, followed by what you did about it and where you are now. “I used to avoid asking questions when I did not understand something, because I thought it looked incompetent. On my final-year project it cost the team two weeks. I now ask within the first day, and I check my understanding in writing.” That is a weakness, an actual consequence, and a correction — which is the entire point of the question.
The behavioural family
These begin with “tell me about a time when” and are the ones most worth preparing, because they are asked in almost every structured interview:
- A time you led something.
- A time you disagreed with someone.
- A time you failed.
- A time you worked under pressure.
- A time you solved a problem with incomplete information.
- A time you learned something difficult quickly.
Prepare six stories rather than sixty answers. One good story usually serves three questions with a different emphasis each time. Structure each with STAR, and make sure the Action section contains actual decisions with reasons — that is what is being assessed, not the outcome.
“Where do you see yourself in five years?”
The interviewer is not testing clairvoyance. They are checking that your direction is compatible with the job, and that you have thought past the first payslip.
Name a capability rather than a job title. “I want to be the person the team asks about data quality” is credible and compatible. “In your job” is awkward; “running my own company” may be honest but says you are passing through.
Your questions for them
Having none is read as having no interest. Having three is read as having done the work.
Ask about the work itself: what a successful first six months looks like, what the team is currently finding difficult, how the role came to exist, how performance is assessed. Avoid asking anything answered on the first page of the website — it demonstrates the opposite of preparation. Save salary and leave for the offer stage unless they raise it.
Practicalities that decide more than they should
- Test the technology beforehand for a remote interview — camera, microphone, and a backup connection. Say at the start that you may need to switch if the line is unstable; interviewers accept that far better than a silent freeze.
- Have your CV in front of you and know what is on it. Being unable to discuss your own document is fatal.
- Silence is allowed. Three seconds of thought before answering reads as considered, not slow.
- Ask for clarification rather than answering the wrong question confidently.
- Send a short thank-you message within a day. It is rare enough to be remembered.
If this is your first interview
Two things help more than anything else. Rehearse out loud — answers that feel complete in your head reliably fall apart when spoken, and finding that out at home is free. And treat early interviews as practice rather than as verdicts; the second is always better than the first, so it is worth arranging one you care less about first.
If your experience is mostly academic, that is workable material. A candidate who describes how they diagnosed a weak paper, restructured revision around timed past papers, and tracked the improvement is demonstrating self-management with evidence — which is exactly what these questions test.
Frequently asked questions
How long should an answer be?
Ninety seconds to two minutes for behavioural questions; thirty to sixty seconds for factual ones.
Should I memorise answers?
No. Memorised answers sound memorised. Learn the structure and the stories, not the sentences.
What if I do not know the answer?
Say so, then say how you would find out. That is a better answer than a confident invention, which will be tested.
Is it acceptable to ask about salary?
At offer stage, yes. In a first interview, only if the interviewer raises it.
What if I have no work experience?
Use coursework, projects, tutoring, association roles, family business work and exam preparation. The question is about how you behave, not about where you were employed.
