
The employer is screening for your problem-solving composure and ability to navigate real-world project roadblocks, as mentioned in reports about detailed project discussions. They want to see you didn't just manage the blocker, but managed stakeholder expectations and kept the timeline intact.
Use the STAR method, but emphasize the proactive steps you took before the blocker became a crisis. Start by briefly setting the scene, then clearly state your objective, and then detail two to three specific actions you took. End with a metric-focused result that shows you salvaged the project.
As soon as a blocker surfaces, assess its real impact on the critical path, whether it delays the entire project or just one workstream, and how much schedule buffer already exists. Communicate early and transparently with stakeholders about the issue and its likely impact rather than waiting to see if it resolves on its own, and set revised expectations proactively instead of after the fact. Then work the problem directly: for a vendor delay, escalate to the vendor for a firm new timeline or evaluate whether an alternate vendor or internal resource can close the gap; for a technical issue, bring in the right technical owner immediately and look for a temporary workaround that lets other dependent work keep moving in parallel rather than everything stalling. Update the project plan and risk log to reflect the new timeline and whatever mitigation was applied. Once resolved, close the loop with stakeholders and note what safeguard, such as earlier vendor check-ins or additional technical review time, would reduce the chance of a similar blocker recurring.
Don't apologize excessively for the delay as if it was your fault, like saying 'Pasensya na po, nagkaroon lang ng problema with the contractor.' Instead, own the resolution confidently by framing it as a proactive risk management action. Say something like 'The vendor issue was a challenge, but I immediately activated a backup plan.'
Situation
We were rolling out a fiber-to-the-home (FTTH) expansion in a new district, and our primary civil works subcontractor abruptly halted work due to a permitting issue with the local government, which they had assured us they had secured.
Task
My task was to get the physical network build back on track with minimal schedule slippage, while also managing the expectations of the business unit that had already started pre-selling the service in that area.
Action
I first called an emergency meeting with the subcontractor's project manager to understand the exact permitting gap and their timeline to fix it, which they estimated at three weeks. Simultaneously, I contacted two backup contractors from our approved vendor list to assess their availability and mobilization speed. I then split the delayed work: I assigned the original contractor the remaining low-risk sections they could legally continue, and I tasked one backup contractor to start the work in the blocked zone after the city engineer issued a temporary fix. I updated the stakeholder tracker with the revised timeline, including a 5-day buffer, and communicated the delay directly to the sales team so they could adjust their go-live promises.
Result
The blocker was resolved in two weeks instead of the projected three. The project completed only four days behind the original schedule, and we recovered the lost days by compressing the testing phase. The business unit was able to launch only one week late, which was within their acceptable tolerance.
Always maintain a shortlist of pre-qualified backup vendors for critical project phases, even when your primary contractor seems reliable.
Write your own answer, then get instant AI feedback graded against:
Get AI feedback on your answer — free.
3 free AI-graded answers + 1 free mock interview, no card needed.
Sign Up FreeAlready have an account? Log in
Sign in to join the conversation.
No answers shared yet — be the first to show how you'd approach this.