A task slip that may or may not move the completion date
The scenario describes a project schedule where one task has slipped by several days, and asks for the reasoning out loud, whether that task sits on the critical path, what happens to the overall completion date if it does, and what tradeoff options exist if compressing the schedule elsewhere would mean spending more budget to catch up.
Follow-up questions push on specifics, how to tell whether a task has float or not, and how that reasoning gets explained to a stakeholder who just wants to know if the deadline is still safe.
What the session actually asks
Expect the session to open with a described schedule or budget scenario that has a specific planning answer buried inside it, not an abstract question about project management philosophy in general.
Follow-up questions test whether the reasoning holds together when a new detail is introduced, a second task also slips, or the budget for catching up is more limited than expected, since two candidates can start from the same schedule and only one of them explains clearly what actually threatens the completion date.
The session stays on planning and budget reasoning throughout, rather than branching into stakeholder communication or facilitation questions the general and comprehensive types cover instead.
Scoring
How the Technical dimension gets scored here
Technical carries the most weight in this session specifically, and the written reasoning behind the score explains what drove it, whether the critical path reasoning was sound, whether a tradeoff recommendation was defended with real planning logic rather than guessed at, and whether the answer actually adapted when the scenario's details changed.
Calibration floors and caps apply here the same way they do everywhere else on Intervieux, so a confident-sounding but vague answer about scheduling can't outscore one that's less polished but analytically specific. Communication still factors in on how clearly the reasoning gets narrated, since explaining a schedule risk to a nervous stakeholder is a real part of the job too.
Frequently asked questions
Do I need specific software experience, like a particular scheduling tool, for this interview?
No. The session tests critical path and budget reasoning conceptually, not familiarity with one specific scheduling software's interface.
Is this specific to construction project management?
No. The scenario applies critical path and budget tradeoff reasoning broadly, which shows up in IT, construction, and other project management contexts alike.
How is this different from the general project manager interview?
General covers a setting-neutral round of scope, risk, and stakeholder questions. This session stays specifically on critical path and budget tradeoff reasoning.
Is it possible to set a harder interviewer for this one?
Yes. A formal style combined with an analytical or challenging personality raises the difficulty of the follow-ups considerably.
Is this useful for a project manager without a formal certification yet?
Yes. The scenario tests planning reasoning directly, which doesn't require a specific certification to demonstrate, even though many candidates pursuing one find the practice useful.
Related pages
Practice the planning reasoning, not just the schedule
Run a technical AI interview to work through a critical path or budget tradeoff scenario out loud, then get scored on how clearly and specifically that reasoning holds up.