Why pre-screen project coordinators before the hiring manager interview
This role is defined by a specific difficulty that never appears in a job description: the coordinator is accountable for information they cannot produce themselves, held by people who do not report to them and who are busy. A coordinator who accepts whatever the tracker says produces reports that are confidently wrong. One who chases, verifies and escalates keeps the project honest. Both describe the same duties on an application, and a short screen separates them.
What actually matters when screening Project Coordinator candidates
- 01
Execution and reliability
Check how many concurrent projects they coordinated, budget size, and which tools they ran: MS Project, Smartsheet, Jira, Asana. Ask for a schedule they built and held.
- 02
Improving the process
Probe for a process they rebuilt: status reporting cadence, RAID log hygiene, intake forms, change request workflow, or a project template others later adopted.
- 03
Judgement and autonomy
Test how they handle a slipping dependency or a vendor missing a deliverable: what they escalate, what they resequence, and when they raise a change request.
- 04
Communication
Assess how they write steering updates and run stand-ups or kick-offs: minutes, action logs, and chasing owners across engineering, finance, and external suppliers.
Pre-screening questions to ask Project Coordinator candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Tracking that is accurate
3 questions01How do you track progress and performance during a project?
Listen forVerification against something real rather than accepting status updates, with how they spot a task reported as on track that is not.
Reports the tracker as given, or no method for checking whether a reported percentage means anything.
02Can you describe your experience with project management software?
Listen forNamed tools with real daily use, plus something they configured or restructured rather than only updating what was there.
Names tools they cannot describe using, or maintains a parallel personal spreadsheet because the system is not trusted.
03What methods do you use to manage several projects at once?
Listen forA concrete triage approach with how they decide what gets attention on a given day, plus what they let slide deliberately.
Handles everything equally, or prioritises by whoever contacted them most recently.
Improving the run
3 questions04What is your process for delegating and following up on tasks?
Listen forClear ownership and a deadline agreed with the person rather than assigned to them, with a follow-up rhythm that does not depend on memory.
Assigns tasks in a tool with no conversation, or follow-up that only happens when something has already slipped.
05How do you ensure project requirements are actually met?
Listen forRequirements traced through to delivery with a check at the end, and a case where something agreed early was quietly dropped.
Assumes requirements are met if tasks are marked complete, or no final check against what was originally agreed.
06How do you handle changes or adjustments during a project?
Listen forChange recorded with its effect on timeline made visible, rather than absorbed silently into the existing plan.
Changes accepted without adjusting the schedule, or scope creep noticed only when the deadline arrives.
Escalating early
3 questions07How would you handle a project at risk of missing its deadline?
Listen forA threshold for escalation applied before the deadline is at risk, with options presented rather than just a warning delivered.
Escalates only once the deadline has passed, or escalates everything with no filtering.
08What strategies do you use to manage project risks?
Listen forRisks tracked with owners and review dates, plus one that materialised and what had already been prepared for it.
A risk register maintained but never reviewed, or risks recorded with nobody accountable for them.
09Can you describe a time you had to make a decision under pressure during a project?
Listen forA decision inside their authority made promptly, with a clear sense of what they could decide and what needed a manager.
Escalates every decision, or made a call well outside their remit without telling anyone.
Chasing without friction
3 questions10What is your approach to stakeholder communication?
Listen forChasing senior people without friction, with a specific example of getting an update from someone who had ignored two requests.
Avoids chasing senior stakeholders, or escalates to their manager as a first response to a missed update.
11How do you handle conflict within a project team?
Listen forA real disagreement, often about priority or capacity, with what they did within their authority before involving a manager.
Passes every conflict upward immediately, or no experience of a disagreement between team members.
12Can you describe a project that did not go as planned and how you handled it?
Listen forAn honest account including their own part in it, with what they would flag earlier if the same thing happened again.
Every failure attributed to other people, or no project they have been part of that went wrong.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Execution and reliability
35%5Names live projects with budgets and dates, shows baseline versus actual schedule slippage, and explains how milestones were tracked weekly.
Improving the process
25%5Describes a specific coordination bottleneck removed, such as replacing email status chasing with a dashboard, and cites time saved.
Judgement and autonomy
25%5Distinguishes issues they resolved alone from ones warranting sponsor escalation, and shows evidence of re-planning critical path without being told.
Communication
15%5Gives clear, brief status framing (on track, at risk, blocked) with named owners and dates, and follows up until actions close.
Coordinators are accountable for information held by busy people who do not report to them. A one-way video screen lets you hear how they chase and verify it.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for a project coordinator take?
Ten to fifteen minutes across eight to ten questions, answered async. Enough to hear how they keep a tracker accurate, how they chase updates from people senior to them, and when they escalate.
How much should tool familiarity matter?
Less than it appears to. Project tools are learnable in a week and every applicant lists several. What matters is whether they treat the tool as a record of reality or as reality itself, and that shows up in how they answer the chasing question.
Evaluating answers
What is the strongest signal when screening a project coordinator?
What they do when a task is not updated. Strong coordinators go and ask, verify rather than assume, and note the difference between what was reported and what is true. Anyone who reports the tracker as-is will produce status reports nobody can rely on.
How do I test their escalation judgement?
Ask when they would raise a slipping task. The answer you want has a threshold attached, applied before the deadline is at risk rather than after. Coordinators who escalate everything are as unhelpful as those who escalate nothing.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
