Free tool

Walk in prepared, not memorised

A printable question bank with guidance for the answers, plus a checklist that tracks what you have actually done. Everything stays on your device.

Nothing uploaded Free & unlimited No account

Prep checklist

0 of 14
Saved on this device: checkboxes persist in local storage so you can return later. Clearing site data resets them.

Interview question bank

Tell me about yourself.
Give a 60-second version of your resume summary: current scope, one concrete result, and why this role is the logical next step. Do not walk through your entire history chronologically.
Why this role, and why now?
Connect the posting's first responsibility to something you have done and want to do more of. "I want a new challenge" is not an answer; "the platform scale here is the next version of what I did at X" is.
Why are you leaving your current role?
Stay forward-looking and neutral. Talk about what you are moving toward, not what you are escaping. Never criticise a manager or employer — interviewers assume you will describe them the same way.
Tell me about a time you disagreed with someone at work.
Choose a disagreement about the work, not a personality clash. Explain the positions, the evidence you used, how you resolved it and what the relationship looks like now. The interviewer is assessing collaboration under pressure.
Describe a failure and what you learned.
Pick a real failure with consequences. Own your part without blaming others, name the cost, describe the change you made, and show the later evidence that the change worked. Avoid the humblebrag failure.
Tell me about a time you delivered under a tight deadline.
Use STAR and include the trade-off you chose: what you cut, what you protected, and how you communicated risk early. The decision is the story, not the long hours.
Tell me about difficult feedback you received.
State the feedback plainly, whether you initially agreed, what you changed, and what improved. Interviewers are checking coachability and self-awareness, not perfection.
Tell me about a time you influenced without authority.
Name the stakeholders, why they resisted, the evidence or pilot you used, and the decision that changed. This is the standard seniority test; vague "I persuaded the team" answers fail it.
How do you prioritise competing work?
Give a framework — impact, deadline, dependency, effort — then a real example where you explicitly dropped or delayed something. A prioritisation story with nothing deprioritised is not a prioritisation story.
What is the hardest technical or operational problem you have solved?
Choose one where the constraint mattered: time, budget, legacy systems or conflicting requirements. Explain your diagnosis, the options you considered, the decision and the measurable outcome.
How do you handle ambiguity?
Describe a situation with missing information, the assumptions you surfaced, the small experiment or stakeholder check you ran, and how you kept moving. Show judgment, not tolerance for chaos.
Tell me about a process you improved.
Name the before state with a number, the change you made, who you had to bring along, and the after state. If you can, include what you would do differently now.
Why should we hire you?
Three sentences: the match between the role's priority and your evidence, one proof point, and the risk you remove for the team. Do not re-summarise the whole interview.
What does success look like in the first 90 days?
Ask this to learn the real priorities and to show you think in outcomes. Write down the answer — it is the best material for a follow-up note.
What is the biggest constraint on the team right now?
A candid answer tells you whether the role is set up to succeed, and whether the problem is one you want to own.
How are decisions made when the team disagrees?
Listen for a real mechanism — an owner, a forum, an escalation path — rather than "we collaborate openly".
What happened to the last person in this role?
Promoted, moved internally, left — each answer tells you something about the path and the pressures. Ask it neutrally and listen carefully.
What are the next steps and the timeline?
Ask at the end of every interview. It tells you when to follow up and prevents weeks of silent waiting.

About this tool

The question bank groups the questions that account for most behavioral interviews and adds a sentence of guidance for each answer — not a script. Guidance is more useful than a script because interviewers probe follow-ups, and a memorised answer collapses the moment the question changes shape.

The checklist on the left is the routine: research, four stories, logistics, questions to ask, and the follow-up. Tick items as you complete them; the state is stored in your browser so you can spread preparation across a week.

Rehearse headlines, not paragraphs. Memorise one line per story — "the audit failure two weeks before the filing" — and let the details come back in the room. That is what keeps an answer sounding like a person rather than a recital.

Common questions

Can I print the question bank?

Yes. Click Print bank; all answers expand for printing, the site navigation is hidden, and the page prints in a clean single column. Put the pages away before the interview — this is preparation material, not a script.

Does the checklist sync across devices?

No. It is stored in your browser's local storage on this device. There is no account and no server, so nothing syncs by design.

Are these the exact questions I will be asked?

They are the shapes of the questions, not a transcript. Employers vary the wording, but the underlying evidence they look for — ownership, judgment, collaboration, results — is consistent.