Project Planner Interview Questions UK: 8 Real Questions and What Interviewers Want

Most Project Planner interviews in the UK follow a pattern, and knowing it beats guessing. Below are eight questions from our bank of 12, each with a note on what the interviewer is really after.

Eight Project Planner interview questions, and what the interviewer is thinking

1. Walk me through how you would build a project schedule from scratch, and which scheduling software you have used.

Why they ask: This is the core planner skill, so they test your method and tool experience.

2. Explain total float and free float, and how you would use float information when managing a schedule.

Why they ask: Float is a basic concept, and they want to see that you can apply it rather than just define it.

3. What does a typical day or week look like for a project planner, and what makes a good one?

Why they ask: They want to see that you understand the rhythm and the interpersonal side of the role.

4. How do you measure and report progress, and what does an S-curve tell you?

Why they ask: They test your approach to progress measurement, which underpins reliable reporting.

5. What are the main types of logic relationships in a schedule, and what problems do you see with lags, constraints and open ends?

Why they ask: Logic quality is the most common weakness in schedules, so they want to see attention to detail.

6. The latest update shows the project is eight weeks behind with the end date fixed. The project manager asks you for a recovery programme. What do you do?

Why they ask: This tests your schedule recovery techniques and how you avoid unrealistic fixes.

7. Tell me about a time you built a programme for a complex project and got reluctant people to provide the input you needed.

Why they ask: They test your ability to gather information and engage stakeholders, since planners depend on others' data.

8. A task owner gives you a very short duration for an activity that you believe is unrealistic. How do you handle it?

Why they ask: Challenging durations diplomatically is a daily planner skill.

A sample answer to question 1

Walk me through how you would build a project schedule from scratch, and which scheduling software you have used.

I'd begin with the scope, contract milestones and a work breakdown structure, so the plan covers everything and nothing twice. Then I'd run planning workshops with discipline leads, to identify activities, durations and logic, rather than guessing from my desk. In Primavera P6, I'd set up the project calendars, create the WBS and activities, assign relationships, mostly finish-to-start with minimal lags and constraints, and add milestones. I'd then check there are no open ends, forward and backward pass the schedule to find the critical path and float, and review it with the project manager and team to confirm that it's buildable. If appropriate, I'd add resource or cost loading. I'd baseline it once approved and agree the update cycle. I have used P6 on construction and infrastructure projects, Microsoft Project and Asta Powerproject on others, and I'm comfortable exporting to Excel and Power BI for reporting. A good schedule is a communication tool as well as a calculation.

Common mistake to avoid: Building the plan alone at a desk; Heavy use of constraints instead of logic

Want the rest?

Full model answers, key points and common mistakes for all 12 questions are on the Project Planner interview questions page. The first five are free, no sign-up needed.