INTERVIEW PREP

Got an interview lined up? Don't wing it.

The most common interview questions โ€” and how to answer them. Behavioural, technical, and salary discussion playbooks. Plus a free cheat sheet for the night before.

Get the free cheat sheet
Most missed question
"Why are you leaving your current job?"
The wrong answer kills more offers than weak technical skills. Our cheat sheet gives you 3 framings that don't sound bitter or vague.
Common Questions

Questions you'll almost definitely be asked

Pick a category โ€” we'll show the questions that come up in 80% of interviews and how to answer each one.

Behavioural
Technical
Salary & Offer
Closing the interview
"Tell me about yourself."
Use a 60-second 3-act structure: Present (what you do now and one impressive recent win), Past (the path that got you here), Future (why this role is the logical next step). Don't recite your CV โ€” they have it in front of them.
"Tell me about a time you failed."
Pick a real failure with a clear lesson โ€” never something fake like "I work too hard." Use STAR: Situation, Task, Action, Result. Spend most time on what you changed afterwards. Interviewers want growth, not perfection.
"Why are you leaving your current job?"
Frame the move forward, not the escape. "I've grown a lot here, but the next set of problems I want to solve doesn't exist on this team." Avoid criticising your manager, salary, or hours โ€” even if true.
"What's your greatest weakness?"
Pick a real weakness that isn't core to the job, then describe what you're actively doing about it. Skip the clichรฉ reverse-flex ("I'm a perfectionist"). Be human, be specific, show self-awareness.
"Tell me about a conflict with a coworker."
They're testing emotional regulation. Pick a low-stakes example, describe how you raised the issue directly, and end with what you learned about communication. Never name-and-shame.
"Walk me through your most complex project."
Pick something you drove, not something the team built. Describe: the constraint, the trade-off you debated, the decision, and the measurable result. Don't go too deep on tech without checking they want it.
"How would you approach [hypothetical problem]?"
Think out loud. Clarify constraints first ("What's our budget? Latency requirement? Team size?") โ€” this alone separates strong candidates from average ones. Then sketch 2 approaches and weigh them.
"What technologies are you currently learning?"
Have a real answer, even if it's small. The wrong answer is "nothing right now, I'm too busy." That signals you've stopped growing. Even a 30-min weekly habit counts.
"How do you stay updated in your field?"
Name 2-3 specific sources โ€” newsletters, podcasts, communities, courses. Generic answers like "I read articles" sound made-up.
"What are your salary expectations?"
Always defer if asked too early. "I'd like to understand the role and team better before discussing numbers โ€” could you share the budgeted range?" If they push, give a band based on real research, not a single number.
"What's your current salary?"
In many regions you can decline politely: "I'd rather focus on the value I'd bring to this role than anchor on past compensation." Pivot back to the conversation.
"We can offer X โ€” would that work for you?"
Never accept on the spot. Buy 24 hours: "Thank you. I'd like to take a day to consider the full package โ€” is that okay?" Then come back with a thoughtful counter that references market data.
"How did you arrive at that counter-offer?"
Have receipts. Quote market data (Joboful Salary Guide, Levels.fyi, Glassdoor). Reference specific skills you bring. Never say "because I want more" โ€” give the recruiter a justification they can take to their manager.
"Do you have any questions for us?"
Always have 3+ ready. Top picks: "What does success look like in this role at 6 months?" / "What's the biggest challenge the team is facing right now?" / "What's the team's growth plan over the next year?" Avoid asking only about benefits and time off.
"Why should we hire you?"
Tie three of your strengths to specific things they've said about the role. Don't list generic skills. End with: "I'm confident I can [specific outcome]".
After the interview ends โ€” what now?
Send a thank-you email within 24 hours. Reference one specific thing you discussed, restate your interest, and offer to provide anything they need next. This still moves the needle โ€” most candidates skip it.
Tips

The non-obvious things that separate offers from rejections

Show up early โ€” but not too early

Arrive at the building 15 minutes ahead, walk in 5 minutes early. Earlier signals nervousness; later kills momentum. For video calls, log on 2 minutes before the scheduled time.

Talk less than you think

Most candidates over-explain. A tight 90-second answer beats a rambling 4-minute one. If they want more depth, they'll ask. Pause confidently after answering.

Eye contact > script recall

Don't memorise. Memorised answers feel rehearsed and disconnect you from the room. Have anchor stories ready, not paragraphs.

Research the interviewer, not just the company

Spend 5 minutes on their LinkedIn. A casual "I saw you joined from X" creates instant rapport and signals genuine interest.

Bring a notepad

For questions, key terms, follow-ups. Looks engaged, gives you a moment to think before answering, and doubles as your post-interview thank-you note material.

Don't bad-mouth past employers

Even if asked. Even if true. Even if everyone agrees. Interviewers extrapolate โ€” if you complain about Acme Corp today, you'll complain about us next year.

The STAR Method

The single framework that fixes most behavioural answers

Behavioural questions ("tell me about a time whenโ€ฆ") trip up smart candidates because they answer in summary instead of story. STAR forces structure.

  • S โ€” Situation: set the scene in two sentences.
  • T โ€” Task: what was your specific responsibility?
  • A โ€” Action: what did you (not the team) do?
  • R โ€” Result: the measurable outcome โ€” numbers, percentages, real impact.
Example
Q: "Tell me about a time you handled a tight deadline."
S: Last year our biggest client doubled their order size two weeks before launch.
T: I was the project lead โ€” needed to ship without delaying the launch.
A: Re-prioritised the backlog with my team, pulled in two contractors for design, and personally took over QA to free engineers.
R: Shipped on time. Client renewed for 2x value. We documented the playbook for future scope changes.

Your night-before-the-interview cheat sheet.

A free 6-page PDF: 30 most common questions, sample answers using STAR, salary discussion scripts, and the questions you should ask them at the end.

  • 30 questions with sample answers
  • 8 questions to ask the interviewer
  • Day-of checklist (what to bring, what to do)
FAQ

Interview prep, answered

How long should my interview answers be?

For most behavioural questions, 60โ€“90 seconds is the sweet spot. Open-ended ones like "tell me about yourself" can run to 2 minutes. If your answer hits 3+ minutes, you've lost them.

Should I take notes during the interview?

Yes โ€” it signals engagement and gives you something to reference in the thank-you email afterwards. Just don't write while the interviewer is making a key point.

What should I wear?

Match the company's culture, then dress one level up. For a startup, smart casual. For consulting/banking, full formal. When in doubt, ask the recruiter โ€” they'll happily tell you.

How soon can I follow up after the interview?

Send the thank-you email within 24 hours. After that, give them their stated timeline plus 2โ€“3 business days before nudging.

What if I don't know the answer to a technical question?

Be honest, then think out loud. "I haven't worked with X directly, but here's how I'd approach itโ€ฆ" shows reasoning, which is often what they're really testing.

Interview Preparation 2026 โ€” Job Interview Tips That Actually Work

A bad interview rarely fails on technical skills โ€” it fails on framing, confidence and structure. Joboful's interview prep guide focuses on the things smart candidates still get wrong: rambling answers, weak salary discussions, and poor closing questions. Each section is built around real interviews from across the UAE, India, UK, Canada and Australia.

Behavioural interviews

Most large companies now lean on behavioural interviewing โ€” past actions predict future actions. The STAR method (Situation / Task / Action / Result) gives you a repeatable structure so your stories land with impact. Practice three or four core stories and adapt them to the question.

Technical interviews

For technical and case-style interviews, think out loud. Interviewers are evaluating your problem-solving process at least as much as your final answer. Clarify constraints, sketch trade-offs, and don't be afraid to revise your approach mid-way โ€” that's strength, not weakness.

Salary discussions

The salary conversation usually decides whether you'll regret the offer six months later. Use the Joboful Salary Guide for benchmarks, defer the question until you understand the role, and never accept on the spot. A polite 24-hour pause to consider the full package is industry standard and respected by recruiters.