Interview questions by job title, and how to answer them

A way to structure an answer about something you did: the Situation (one or two sentences of context), your Task (what you were responsible for), the Actions you took (the longest part, in the first person), and the Result (what changed, ideally with a number). It keeps a story to about two minutes and makes sure you end on the outcome.

Prepare five to eight stories rather than fifty answers. One story about a hard problem, one about a conflict, one about a mistake, one about leading without authority and one about a result you're proud of will cover most behavioural questions, and the role-specific pages show which technical topics to revise.

They're written by the FindAJobAI team for each role, based on the skills employers list in job ads and the way interviews for that job are usually run: a screening call, skills or technical rounds, behavioural questions and a final conversation. No company's confidential questions are copied, and wording varies from one interviewer to the next, so prepare the skill behind each question, not a script.

No. The sample answers are fictional: the people, employers and numbers are invented to show how a strong answer is built, and the outlines show what it contains. The details have to be yours. Interviewers ask follow-up questions ("what would you do differently?", "what was the number?"), and a memorised story falls apart there, while one you lived holds up.

Two or three questions that help you decide whether you want the job: what success looks like in the first months, what the team's hardest current problem is, and how decisions get made. Each role page lists five questions worth asking for that job.