Questions to ask your interviewer

Shows you know the difference between driving a programme and merely updating one, and reveals the real remit.

The answer tells you whether you are filling a gap, fixing a problem, or building something new.

Pins down what you would actually be doing on day one, and lets you tailor everything that follows.

Signals you think in terms of contribution, not duties, and gives you material for your closing pitch.

Cuts through the advert to the real rhythm of the role: meetings, updates, site time and reporting.

Invites honesty about the hard part, and shows you would rather know the difficulty than be surprised by it.

Protects you from scope creep and clarifies whether your planning expertise is genuinely the core of the job.

Shows you understand that client, consultancy and contractor planning are different disciplines, not the same job relabelled.

Surfaces travel expectations and portfolio breadth before they become a surprise after you have accepted.

Basic due diligence: you learn where planning sits, how senior it is, and who owns your development.

Shows you see planning as an integrated controls discipline rather than a standalone scheduling desk.

Settles the practicalities early so neither side wastes time on an arrangement that will not work.

Tells you whether you would be mentored, mentoring, or the only planner holding the whole programme together.

Reveals how close you would be to delivery, and how much consistency the organisation expects across programmes.

Strong planners know the programme drives entitlement, so asking this signals you understand contract and schedule are linked.

A precise, practical question that avoids the classic mismatch between advertised flexibility and actual site expectations.

Useful in consultancy: it tells you whether you would be building schedules, reviewing others' schedules, or both.

Joint ventures create real ambiguity about who manages you, and asking shows you have worked inside one before.

Tells you what you would need to learn, and signals that your interest goes beyond one scheduling tool.

Reporting rhythm defines your week, and the audience tells you how much analysis rather than data entry is expected.

Invites the interviewer to talk shop, and gives you an opening to reference comparable work you have delivered.

An excellent follow-up: it shows you listen carefully and think about where a problem actually originates.

Constraint-led thinking separates a planner from a scheduler, and the answer shapes any programme you would build.

Framing it as opportunity rather than failure lets the interviewer be candid, and hints at your first project.

A commercially literate question that tests the security of the role without ever sounding anxious about it.

Shows you know contract administration and the programme are linked, and that you have used such systems.

A pure planner's question: the answer tells you about critical path, resource peaks and interface risk.

Demonstrates awareness of how procurement models reshape reporting, risk allocation and the client's appetite for schedule detail.

Lifts the conversation above your own role and shows you think at portfolio, not just project, level.

The single most useful question you can ask, because everything they truly value surfaces in the answer.

Turns a vague job description into a concrete plan you can quote back at your first review.

Forces a specific, measurable answer instead of generalities, and shows you are comfortable being measured.

Signals you intend to keep growing, and tells you whether the organisation genuinely invests in its controls people.

Gets past the essential criteria to the behaviours that actually get people promoted in this team.

The longer horizon draws out strategic expectations that a ninety-day answer almost always misses.

Shows you are planning a career rather than taking a job, and tests whether a route genuinely exists.

Ambitious without arrogance, it hands the interviewer a picture of you already performing in the role.

Broad enough to get an honest answer, and the specifics they choose reveal what they actually value.

Personal questions get warmer, more candid answers, and build rapport where interviews usually go flat.

Retention is the honest test of culture, and hesitation in the answer is as informative as the words.

A courteous way to test culture through lived experience rather than the polished corporate description.

Quietly makes the case for your transferable experience while revealing how the team supports new starters.

Positions you as a market-aware professional and often draws out candid comments about pay and retention.

Entirely legitimate once the role is clear, so ask it late in the conversation and ask it matter-of-factly.

Neutral phrasing keeps the focus on their budget rather than your expectations, which protects your negotiating position.

A material part of UK reward that candidates routinely forget to check until after they have accepted.

Site-based controls roles can carry real travel costs, so settle who bears them before you accept.

Protects you from an unsustainable commute, and shows you are thinking practically about sustained site delivery.

Never leave without it: you learn the timeline and show you are actively managing your own search.

Sets a clear date so your follow-up is expected rather than pushy, and removes the guesswork from waiting.

Your safety net: it surfaces doubts while you are still in the room to answer them.

Bold but effective, it invites the objection early and gives you one last chance to answer it.

Lets you prepare properly for a panel, technical test or presentation rather than guessing what is coming.

Removes the guesswork from a technical presentation and shows you prepare deliberately rather than hopefully.

Knowing whether it is a technical lead, operations or HR lets you pitch your examples at the right level.

Essential where you are hired into a pool rather than one post, as it reveals how resourcing really works.