Why pre-screen junior project managers before the interview
Junior applications describe every project in the first person whether the person ran it or took the notes. The distinction matters, because a coordinator who has never had to tell a stakeholder that a date has moved has not done the hard part of the job. A short screen asks what they owned, and what happened the first time a deadline was going to slip, which is where the real difference shows.
What actually matters when screening Junior Project Manager candidates
- 01
Execution and reliability
Check how they ran schedules and trackers day to day: Asana or MS Project plans, RAID logs, sprint boards, status reports, and whether milestones landed on the dates promised.
- 02
Improving the process
Probe for a workflow they tightened: standardising status report templates, cutting meeting load, automating timesheet chasing, or fixing a handover that repeatedly slipped between teams.
- 03
Judgement and autonomy
Test what they did when a dependency slipped or scope crept: what they escalated to the PM lead, what they resolved alone, and how they weighed schedule against scope.
- 04
Communication
Assess how they write status updates and run stand-ups or steering meetings: chasing late contributors, flagging red items early, and translating engineering detail for sponsors.
Pre-screening questions to ask Junior Project Manager 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.
Owned rather than assisted
3 questions01Can you describe a project you managed from start to finish?
Listen forA project they held, with a clear line between what they decided and what someone else decided.
Ownership claimed for a project they supported, or no decisions they made themselves.
02What previous experience do you have with project management?
Listen forHonest framing of scale and role, including coordination work described as coordination.
Scale inflated, or every project described as one they ran.
03What tools or software do you use for project management?
Listen forTools used to keep a plan current, with a habit of updating rather than reporting from memory.
Plans maintained for status meetings only, or a plan nobody else could read.
Raising a slip early
3 questions04How have you handled missed deadlines in the past?
Listen forA slip raised as soon as it was likely, with options offered rather than only a problem.
Slips reported at the deadline, or recovery attempted before anyone was told.
05How do you ensure project tasks are completed within the agreed timeline?
Listen forProgress checked against the plan regularly, with dependencies tracked rather than assumed.
Progress checked at milestones only, or reliance on people to report problems themselves.
06How do you prioritise tasks within a project?
Listen forPrioritisation driven by dependency and risk rather than by what is easiest to finish.
Tasks worked in order of arrival, or the critical path not identified.
Scope changes
3 questions07How do you handle changes in project scope?
Listen forChanges recorded with the effect on date and cost stated before the change is accepted.
Small changes absorbed without a record, or scope accepted verbally with nothing written down.
08How do you manage risks and issues within a project?
Listen forRisks with owners and dates that are reviewed, with one that actually happened and was mitigated.
A risk register written at kickoff and never revisited, or risks with no owner.
09Can you discuss a time when a project did not go as planned and how you handled it?
Listen forA specific problem, with their own contribution to how it went acknowledged honestly.
Problems attributed entirely to other teams, or no project that went wrong.
Chasing people well
3 questions10Describe your communication style when dealing with project stakeholders.
Listen forRegular updates whether the news is good or bad, matched to what the audience needs to know.
Updates only when asked, or bad news softened until it cannot be softened further.
11How do you handle disagreements within a project team?
Listen forDisagreements addressed directly and early, with escalation used when it is genuinely needed.
Conflicts avoided until they affect delivery, or everything escalated to a manager.
12How do you delegate and follow up on tasks within a project?
Listen forClear asks with dates agreed rather than assigned, and follow-up that is persistent without friction.
Tasks assigned without agreement, or chasing that relies on escalation to get a reply.
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 specific projects with budget, timeline and outcome; maintained live plans and RAID logs that stakeholders actually used.
Improving the process
25%5Describes a concrete change they introduced, why the old process broke, and the time or rework saved afterwards.
Judgement and autonomy
25%5Shows a clear escalation threshold, gives an example of resolving slippage independently, and admits a call they got wrong.
Communication
15%5Delivers concise, honest updates that surface risks before they bite; chases blockers without souring working relationships.
Junior applications describe every project in the first person, owned or not. A one-way video screen asks what they actually held.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Ten to fifteen minutes across eight to ten questions, answered async. Enough to separate ownership from support, test how they handle a slip, and hear how they work with a team.
How much experience should I expect at this level?
One or two projects genuinely owned, however small. What matters is that they held a plan, chased people and reported honestly, not the size of the budget they worked on.
Evaluating answers
What is the strongest signal when screening this role?
Raising a slipping date early. Junior managers with the right instinct escalate before it is unavoidable. Anyone who hoped to recover it without telling anyone will do the same on your projects.
How do I judge their honesty about their own role?
Ask what they owned and what someone else decided. Sound answers draw that line clearly. Anyone claiming full ownership of everything at this level is overstating, which is the trait to catch now.
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
