1. Before the Interview
Most interviews are won or lost in the preparation. Work through this checklist the day before — it takes about an hour.
Re-read the job description — List the five requirements repeated most often. Those are what you will be scored against.
Map your resume to those five — For each requirement, pick one concrete example from your own experience. That is your evidence bank.
Research the company properly — Recent news, their product, who their customers are, and who you are meeting. Ten minutes on LinkedIn goes a long way.
Prepare your numbers — Revenue moved, time saved, users served, team size. Specific figures are what interviewers remember.
Rehearse out loud — Say your answers aloud, not in your head. The first time you hear yourself should not be in the interview.
Test your setup — For virtual interviews, check camera, mic, lighting and connection the day before — not five minutes prior.
2. The 30 Most Common Interview Questions
These come up in the overwhelming majority of interviews across industries. Prepare an answer for each and you will rarely be caught off guard.
About You
What they are really asking: Can you describe yourself clearly and relevantly, without rambling?
- ›Tell me about yourself.
- ›Walk me through your resume.
- ›What are your greatest strengths?
- ›What is your biggest weakness?
- ›How would your colleagues describe you?
- ›What are you most proud of professionally?
Your Experience
What they are really asking: Can you back up what is written on your resume with specifics?
- ›Describe your current role and responsibilities.
- ›What has been your biggest professional achievement?
- ›Tell me about a project you led from start to finish.
- ›What tools and technologies do you use day to day?
- ›Describe a time you had to learn something quickly.
- ›Why is there a gap in your employment history?
Behavioural
What they are really asking: How do you actually behave under pressure? Answer these with STAR.
- ›Tell me about a time you failed.
- ›Describe a conflict with a coworker and how you resolved it.
- ›Tell me about a time you missed a deadline.
- ›Describe a time you received difficult feedback.
- ›Tell me about a time you had to persuade someone.
- ›Describe a time you had to make a decision without enough information.
Motivation & Fit
What they are really asking: Will you actually stay, and do you want this job specifically?
- ›Why do you want to work here?
- ›Why are you leaving your current job?
- ›What do you know about our company?
- ›Where do you see yourself in five years?
- ›What kind of work environment do you thrive in?
- ›Why should we hire you?
Salary & Closing
What they are really asking: Are your expectations realistic, and are you genuinely engaged?
- ›What are your salary expectations?
- ›Are you interviewing anywhere else?
- ›When could you start?
- ›Is there anything else we should know about you?
- ›Do you have any questions for us?
- ›How do you handle working under pressure?
3. Model Answers — The Eight That Decide It
Listing questions is easy; knowing what a good answer contains is the hard part. For each of these, here is what the interviewer is really testing, how to structure your reply, and a worked example you can adapt.
Tell me about yourself.
What they are testing
Whether you can be concise and relevant. It is also a warm-up — a rambling answer here colours everything that follows.
How to answer
Present → Past → Future, in about 90 seconds. What you do now, the experience that got you here, and why this role is the logical next step. Nothing personal, nothing before your career started.
Worked example
"I am a backend engineer at a fintech company, where I own our payments service — about 400,000 transactions a month. I came into payments from a general platform role three years ago and stayed because I liked how unforgiving it is; a bug is money, not a cosmetic issue. I have taken that service from 99.2% to 99.95% reliability. I am looking to move now because I want to work on payments at a larger scale, which is exactly what this role is."
What loses points
Starting with where you were born. Reciting your resume top to bottom. Going past two minutes.
What is your biggest weakness?
What they are testing
Self-awareness and whether you actually act on feedback. Not whether you have flaws — everyone does.
How to answer
Name a real weakness, then spend most of your answer on the specific system you built to manage it. The fix is the answer, not the flaw.
Worked example
"I used to take on too much rather than say no, which meant a couple of things shipped late. What fixed it was making my workload visible — I keep a public list of what I am committed to, and when someone asks for something new I ask which item moves. It feels blunt but it has made my delivery dates far more reliable, and my manager knows what I am actually holding."
What loses points
"I am a perfectionist" or "I work too hard" — every interviewer has heard these and reads them as evasion. Equally, do not name a weakness that is the core of the job.
Why do you want to work here?
What they are testing
Whether you researched them, and whether you will still be here in two years.
How to answer
Give two reasons: one about the work itself, one about the company specifically. Both should be things you could not say about their competitor.
Worked example
"Two reasons. The role is squarely on infrastructure rather than features, which is where I do my best work. And on the company — I read your engineering post about moving off the monolith in stages rather than a rewrite. That is a hard, unglamorous decision and it tells me the team is pragmatic. That is who I want to work with."
What loses points
Praising their size, funding or brand. Anything you could paste into an application for any other company.
Why are you leaving your current job?
What they are testing
Whether you will speak badly about them next. This is a character question, not a logistics question.
How to answer
Frame it as moving toward something, not away. Keep it short — two sentences — and stay warm about your current employer even if the reality was not.
Worked example
"I have learned a lot there and the team has been good to me. But we are a five-person engineering group and I have gone about as far as I can on scale — I want to work on systems an order of magnitude bigger, and that is not something my current company will have for years."
What loses points
Criticising your manager, the culture or a colleague. Even if entirely justified, it costs you the offer more often than it earns sympathy.
Tell me about a time you failed.
What they are testing
Whether you take responsibility and whether you actually learned something. Interviewers are wary of candidates who have never failed.
How to answer
Use STAR. Pick a real failure with real consequences, own your part without blaming, and be concrete about what you changed afterwards. The recovery is the point.
Worked example
"I shipped a migration without a rollback plan because the staging run was clean. It was not clean in production — we were degraded for about forty minutes. I called it and reverted manually, which took far longer than it should have. What changed is that I now treat the rollback path as part of the change, not a contingency; I write and test it before the migration itself. I have run eleven migrations since with no incidents."
What loses points
A fake failure that is secretly a strength. Blaming a teammate or a vendor. Choosing something so small it shows nothing.
Where do you see yourself in five years?
What they are testing
Whether your ambitions fit what this company can offer. They are checking for a mismatch, not for a life plan.
How to answer
Talk about the kind of problems and scope you want, not job titles. Connect it to a path that plausibly runs through this role.
Worked example
"I want to be the person a team relies on for hard architectural calls — someone with enough depth in one domain to be genuinely trusted. Whether that comes with a staff title matters less to me than the scope. This role would put me on systems far bigger than I have handled, which is the part I am missing."
What loses points
"Your job" as a joke. Naming a title the company does not have. Saying you want to start your own company.
Why should we hire you?
What they are testing
Whether you understood the actual requirement, and whether you can advocate for yourself without arrogance.
How to answer
Pick the two hardest requirements in the job description and answer each with evidence. This is a closing argument, not a personality summary.
Worked example
"Your posting leads with reliability and with mentoring. On reliability, I took a payments service from 99.2% to 99.95% and built the on-call runbook the team still uses. On mentoring, I have onboarded four engineers, two of them career changers, and both are now shipping independently. Those are the two things you said matter most, and they are the two things I have spent three years doing."
What loses points
Generic traits — hardworking, passionate, quick learner. Everyone claims them and none of them are evidence.
Do you have any questions for us?
What they are testing
Genuine interest. Saying no is the most common way a strong candidate loses momentum at the end.
How to answer
Ask two or three that you could not have answered from their website. Questions about how the team actually works land better than questions about the company.
Worked example
"What does success look like in this role at six months? And what is the thing about working here that people only find out once they have joined?"
What loses points
"No, I think you covered everything." Salary and holiday in a first round. Anything answered on their careers page.
4. The STAR Method
Any question that starts with 'Tell me about a time...' is a behavioural question. STAR keeps your answer to about 90 seconds and stops you from wandering.
Set the scene in one or two sentences. Where were you, what was the context?
What specifically were you responsible for? Keep it on you, not the team.
What did you actually do? This is the longest part — spend most of your time here.
How did it end? Use a number wherever you can, and say what you learned.
Example answer
"Our onboarding flow was losing about 40% of new users at the payment step (Situation). I owned the checkout experience, so fixing that drop-off was on me (Task). I ran session recordings, found the card form was failing silently on mobile, rebuilt it with inline validation and added a progress bar (Action). Drop-off fell from 40% to 17% in six weeks, and I now review session recordings monthly rather than waiting for a complaint (Result)."
5. Questions to Ask the Interviewer
Saying 'no, I'm good' is the most common way strong candidates lose momentum. Have four ready and ask at least two.
- ✓What does success look like in this role after six months?
- ✓What is the biggest challenge the person in this role will face?
- ✓How is performance measured and reviewed here?
- ✓What does the team structure look like, and who would I work with most?
- ✓What do you enjoy most about working here?
- ✓What are the next steps in the process, and when can I expect to hear back?
Avoid: Questions you could have answered with 30 seconds on their website, and anything about salary or holiday in a first-round interview.
6. Virtual Interview Tips
Video interviews fail for boring, fixable reasons. None of these are about your answers.
- ✓Join two to three minutes early — never exactly on time, never late.
- ✓Put your light source in front of you, not behind. A window facing you beats any lamp.
- ✓Position the camera at eye level so you are not looking down at the interviewer.
- ✓Look at the camera when you speak, not at your own face on screen.
- ✓Close every other tab and notification. One ping breaks your train of thought.
- ✓Keep a printed copy of your resume and your notes just off camera.
- ✓Have a phone number ready as a backup if the connection drops.
7. After the Interview
The follow-up is short and most candidates skip it. That is exactly why it works.
Send a thank-you email within 24 hours — Four sentences maximum. Thank them, reference one specific thing you discussed, restate your interest, and stop.
Write down what you were asked — While it is fresh. The same questions will come up in your next interview elsewhere.
Log it in your tracker — Record the date, who you met, and when they said they would respond, so nothing slips.
Follow up once if the date passes — One polite message a few days after their stated deadline. Once — not three times.
Thank-you email template
Subject: Thank you — [Role] interview
Hi [Name], Thanks for taking the time to speak with me today. I especially enjoyed hearing about [specific thing discussed]. It reinforced my interest in the [Role] position, and I would be glad to bring my experience in [relevant skill] to the team. Best regards, [Your name]
Keep every application in one place
Track which companies you have applied to, what stage each is at, and when to follow up.
Open Job Tracker8. Frequently Asked Questions
- How long should my answers be?
- Aim for 60 to 90 seconds for most questions, and up to two minutes for behavioural ones. If you are past three minutes, you have lost the room. Pause and ask if they would like more detail.
- What if I do not know the answer?
- Say so, then show your thinking. 'I have not dealt with that exact situation, but here is how I would approach it' is a far better answer than guessing or going silent.
- How do I answer the salary expectations question?
- Give a researched range rather than a single number, and anchor it to the market rate for the role and location. If it is very early in the process, it is reasonable to ask what range they have budgeted.
- Should I really ask questions at the end?
- Yes. Interviewers consistently read 'no questions' as low interest. Two thoughtful questions is the minimum.
- How do I explain a gap in my employment?
- State it plainly, keep it brief, and move to what you did with the time — study, caring responsibilities, freelance work, health. Confidence matters more than the reason itself.
- Is it worth practising out loud?
- It is the single highest-return thing you can do. Answers that read well in your head often fall apart when spoken. Record yourself once and you will hear exactly what to fix.
- How many examples from my experience do I actually need?
- Around six well-prepared stories will cover almost every behavioural question. Pick a success, a failure, a conflict, a deadline problem, a time you influenced someone, and a time you learned something fast. The same story can answer several questions if you emphasise a different part.
- What should I do if I get an aggressive or rude interviewer?
- Stay level and answer the question asked. Some interviewers deliberately apply pressure to see how you respond. If it crosses into genuine rudeness, that is real information about the workplace — finish the interview politely, then weigh whether you want the job.
- Can I take notes into the interview?
- Yes, and most interviewers see it as preparation rather than a crutch. Bring a short page of your key numbers and your questions for them. Do not read answers off it — glancing is fine, reciting is not.
- How soon should I follow up if I hear nothing?
- Wait until a few days after whatever date they gave you, then send one short message. If they gave no date, two weeks is a reasonable point to check in. Once, not repeatedly.