Mock interview practice, built from your resume and the job posting

What this interview prep tool actually does

Most interview practice is guesswork. You rehearse answers to a list of the most common interview questions, then get blindsided by something specific to your own resume. This tool works the other way round: it reads the resume you uploaded and the posting you pasted, and generates the six questions you are most likely to be asked.

Nothing comes from a generic question bank. If your resume shows four years at one employer and seven months at the next, expect a question about the seven months. If the posting leans on stakeholder management and your resume never uses the phrase, expect to be asked about competing priorities.

Then it marks what you write: a score out of 10, a verdict, what worked, what to fix, and an example strong answer built from your own experience.

What kinds of interview questions it generates

Every session produces six questions in a fixed mix, so you practise the whole shape of an interview instead of drilling one category.

• Two behavioural questions drawn from your resume — a career change, a short stint, a promotion, a project that stands out. The "tell me about a time when" questions, the ones that need a story ready rather than an adjective.
• Two technical or role-specific questions drawn from the job description. If the posting names a tool, a methodology or a certification, expect to be asked about it.
• One situational question — a realistic scenario from the job. A deadline slips, a client escalates, two priorities collide. The interviewer wants your reasoning, not a rehearsed line.
• One culture-fit or motivation question. Why this company, why this role, why now. Have a reason that is specific to this employer rather than to the industry.

Each question carries a one-line note on what the interviewer is really assessing.

How your answers are scored

Type an answer under a question and it is scored out of 10 — against that question, against the resume you uploaded, against the posting. Not a generic rubric. You also get a verdict of Excellent, Strong, Good, Needs Work or Weak, plus what worked and what to change.

• 9-10, exceptional. Specific, well structured, and it lands a real result.
• 7-8, strong. The structure is there, but it is vaguer or less impactful than it could be.
• 5-6, adequate. It answers the question, but it could have come from any candidate.
• 3-4, weak. Vague, unfocused, or it misses what the interviewer was asking for.
• 1-2, poor. It does not address the question, or there is too little of it to judge.

Aim for 7 or above on every question before you walk in. When an answer comes back at 5 or 6, the feedback is usually saying one thing: it is true, but it could have been written by any candidate. At the end you get an average score and a per-question breakdown, so you can see which answer is dragging the rest down.

What separates a strong answer from a weak one

• Structure. STAR — situation, task, action, result — is just a way of making sure you finish the story. An answer that stops at the action and never reaches the result leaves out the part the interviewer was waiting for.
• Specifics. "I improved the reporting process" scores lower than "I cut the monthly close from nine days to four."
• Relevance. Every answer should connect to something the posting asks for. An impressive story about work this employer does not need is a wasted turn.
• Length. Three to five sentences — enough to finish the story, short enough that nobody loses the thread.
• Ownership. "We" hides you. Say what you decided and did, then credit the team.

The example answer under each score draws on your own material where it can, so you can hear how your experience sounds once it is structured well.

How to get the most out of a session

• Upload the resume you actually sent for this job, not a general one.
• Paste the whole posting, including the "nice to have" list. A two-line summary produces two-line questions.
• Write each answer out in full sentences, the way you would say it out loud. Notes are harder to judge than prose.
• Run it again after rewriting your two weakest answers.

Built in Canada, for Canadian job hunts

thecareer.ca is a Canadian site and this tool was built here. A Canadian interview isn't a fundamentally different exercise, and it would be dishonest to claim otherwise. What being Canadian does mean is small and concrete: this page is written in Canadian English, and everything is priced in Canadian dollars.

One thing worth knowing before you walk in: Canadian human rights legislation puts some questions off limits for employers — age, marital or family status, religion and place of origin among them. If one comes up, you are under no obligation to have an answer ready.

Before the interview: the rest of the application

Interview prep is the last link in a chain. If you have few interviews to prepare for, the problem sits earlier — around 75% of resumes are filtered out by applicant tracking software before a person reads them, and the ones that survive get roughly seven seconds of a recruiter's attention.

• ATS resume scanner — score your resume against a job description before you apply, and see which keywords the posting expects that you never use.
• Resume builder — rebuild the document in a format parsers can read cleanly.
• Cover letter generator — write for the actual posting instead of a template.
• How ATS works — plain English on what the software does to your file.

Interview prep questions, answered