Skip to content
Question Vault?
Free to readNo accountNo email wallNo invented statisticsNo ads on medical, legal or end-of-life pagesCopy or print any set and take it with you
03 · Professional & Academic

3rd Interview Questions to Ask Employer

Questions for a third interview, when the basics have been covered twice and you are close enough to the offer to ask sharper things: the first ninety days, why the role is open, how performance is judged, who you would depend on, hours and office expectations, level and pay band, and what is left to decide.

20 questions · each with a note on why · conversation guide

The questions

Open any question for the note

  1. What does the first ninety days look like, and what would tell you it had gone well?

    Why ask it

    By the third round they should be able to answer this concretely, with named projects and people. If it is still expressed as settling in and learning the ropes, the role has not been planned, and you will spend your first quarter inventing the job while being judged against an unstated standard.

  2. What is the first problem you want this person to take on?

    Why ask it

    The answer tells you what the job actually is, as opposed to what the advert said. Note whether the problem is the one you were interviewed for. A mismatch here is common and is much easier to raise now than in your first week.

  3. Why is the role open: is it new, or did someone leave?

    Why ask it

    Three different situations with three different risks. A new role means influence and ambiguity; a departure means inherited work and comparisons; a backfill after a long vacancy means a backlog and colleagues who have been covering it. Each changes what your first months feel like.

  4. What happened with the person who had this job before?

    Why ask it

    Listen for length of tenure and whether they left the company or moved within it. Repeated short stays in the same seat point at the manager or the scope rather than the people. A guarded answer to a reasonable question is itself worth noting at this stage.

  5. How is performance judged here, and by whom?

    Why ask it

    You want to know the mechanism: who writes the review, how often, whether ratings are compared across teams, and whether the numbers you would be measured on are within your control. Vague answers about impact usually mean the assessment is a judgement made by one person in a room you will not be in.

  6. Who would I work with most closely, and could I speak to one of them?

    Why ask it

    A reasonable request by the third interview, and the response is informative either way. Companies confident in the team say yes readily. A refusal, or an offer of a carefully chosen advocate instead, tells you something about how much scrutiny they are comfortable with.

  7. Who does this role depend on that it has no authority over?

    Why ask it

    Most of the frustration in a job lives here. Ask which teams you would need things from and how those requests are prioritised. If the answer amounts to persuasion with no shared plan, you now know the real skill the job requires.

  8. What has already been tried on this problem, and why did it not stick?

    Why ask it

    You get the history, and you find out whether the obstacle was technical, financial or political. If two predecessors proposed the same fix and neither got it approved, the constraint is not a lack of ideas, and no amount of enthusiasm from you will change it.

  9. How are decisions made in this team, and what needs sign-off above you?

    Why ask it

    This maps your actual autonomy: spending, hiring, timelines, technical choices. A manager who has to escalate most things will pass that delay to you. Ask for a recent example rather than a description, because the example is much harder to make sound better than it is.

  10. What does a normal week look like in hours and meetings?

    Why ask it

    Ask for their own week, then for the busiest recent stretch and how long it lasted. Everyone says they value balance; what you want are the specifics of evening work, weekend cover, on-call rotations, and time zones you would be expected to overlap with.

  11. What is the expectation on being in the office, and is it written down?

    Why ask it

    Written policy and lived practice often differ, especially where a manager values presence. Ask what the team actually does this month, which days are busy, and whether that has changed recently. Verbal flexibility rarely survives a change of manager.

  12. How secure is the funding and headcount for this team over the next year?

    Why ask it

    Fair to ask at final stage, particularly after layoffs, a funding round or an acquisition. You are listening for whether the role sits in a growing area or is being filled from a budget that has to be justified again in six months. Hesitation is your answer.

  13. What is changing in the organisation over the next six months that I would notice?

    Why ask it

    Reorganisations, leadership changes, a system migration and a new strategy all land on whoever joined most recently. Someone honest will mention at least one. Being told nothing much is planned, in an organisation of any size, usually means they have not been told either.

  14. How do you handle it when someone on the team is not performing?

    Why ask it

    The answer reveals whether difficult conversations happen early and privately or late and formally. Managers who describe a specific, humane process have usually done it. Managers who say it has never come up either have very small teams or avoid the subject until HR is involved.

  15. What kind of person struggles here?

    Why ask it

    Easier for an interviewer to answer honestly than a question about weaknesses, and the answer is frequently revealing: people who need structure, people who expect quick decisions, people who dislike being on call. Check whether the description sounds like you.

  16. What does someone need to be good at here that is not in the job description?

    Why ask it

    Every organisation has an unwritten competence: writing memos, managing a founder, keeping calm with one particular department, working across time zones. This question surfaces it, and it is usually the thing that decides who does well rather than the listed skills.

  17. What level is this role, and where in the pay band would I sit?

    Why ask it

    By the third interview this is a reasonable and expected question, and the placement within the band matters as much as the band itself. Being brought in at the bottom limits your raises for years, so ask what would justify a higher point and who decides.

  18. What would progression look like from here, and who has recently done it?

    Why ask it

    Ask for names and timeframes rather than a policy. If nobody in this team has been promoted in two years, the ladder described to you is theoretical. It is also worth asking whether the last promotion required someone above them to leave.

  19. Is there anything about my background you are still unsure about?

    Why ask it

    Direct, and it gives you the chance to answer the objection while you are still in the room rather than losing to it afterwards. Answer it briefly and without defensiveness. Interviewers who name a genuine reservation are usually leaning toward hiring you.

  20. What are the remaining steps, and when do you expect to decide?

    Why ask it

    You need this to manage other offers and to know when following up is appropriate rather than pushy. A specific date is a good sign; an open answer at third stage often means another candidate is still in play or an approval has not come through.

Using a final interview well

Practical guidance for the conversation itself

What is different about the third round

You are being sold to as much as tested

Getting this far means they are seriously interested, and that changes what you can ask. Questions about pay band, headcount stability and speaking to a peer are all reasonable now, and asking them signals that you are weighing a real decision rather than hoping to be chosen.

Do not repeat the first-round questions

Asking again about culture or values at this stage suggests you have not been listening. Build on what you were told earlier: name the priority the second interviewer mentioned and ask how it is being resourced.

Ask different people different things

The hiring manager knows the work and the standards. A prospective peer knows what the week actually feels like and how the manager behaves under pressure. Recruiters know the band, the level and the timeline. Aim each question at whoever can answer it honestly.

Write the answers down afterwards

Three rounds blur together, and if two offers arrive you will want the specifics: who said what about on-call, which projects were named, what the band was. Notes made the same day are also what you refer back to when the offer is being negotiated.

How to read the answers

  • Specifics beat sentiment. Names, dates, numbers and recent examples mean the thing exists; adjectives usually mean it does not.
  • Notice who gets blamed. If every difficulty is attributed to a previous employee or another department, you will be next in that sequence.
  • Watch for a role that keeps growing during the conversation. Two jobs described as one is the most common way a good offer becomes a bad year.
  • Take note of anything they will not put in writing. Flexible hours, a review at six months, a title change: if it cannot go in the offer letter, treat it as an intention rather than a term.
  • Interviewers who ask you good questions in return usually work in teams that think clearly. A final round with no curiosity about you is worth pausing over.
  • Pay attention to how the process itself has been run. Rescheduling, silence between rounds and contradictory information tend to predict how the job will be managed.

Mistakes at this stage

Treating it as a formality

Final rounds are frequently where a strong candidate loses, usually by relaxing into vagueness. Prepare as you did for the first, with two or three examples ready and a short list of questions you have not asked yet.

Asking what you could have looked up

Anything on the website, in the annual report or in recent news counts against you here. Read those first, then ask a question that starts from what you found: what the last results announcement means for this team, for instance.

Raising money with the wrong person

Pay, band and benefits are usually the recruiter's territory; scope, standards and the team are the manager's. Aiming the money question at a future peer puts them in an awkward position and tells you nothing reliable.

Not asking the awkward question because you want the job

Wanting the offer is exactly why people skip past hours, on-call, the last person's departure and how secure the team is. Those are the terms you will live with, and nobody will volunteer them once you have signed.

Ignoring what you noticed

A dismissive comment about a colleague, an evasive answer about turnover, a manager who checked their phone throughout: candidates routinely explain these away and then meet the same thing again in month three. Write it down and weigh it when the offer arrives.

After the interview

  1. 1Send a short note the same day to the person who led the conversation, referring to one specific thing that was discussed rather than to the opportunity in general.
  2. 2Write out the open questions you still have. Anything unanswered about scope, pay or hours belongs in the offer conversation, not after acceptance.
  3. 3If you were promised information, a band, an introduction, a start date, note the date it was promised for and follow up once it has passed.
  4. 4Do your own checking: former employees on professional networks, reviews, and anyone in your own network who has worked there. This is the point at which what you learn can still change your decision.
  5. 5Decide in advance what you would need to accept, and what would make you decline, so the answer is not made in the ten minutes after the phone call.