Project Delivery and Accountability Questions
How you ensure projects stay on track, handle scope creep, communicate delays to leadership, recover from setbacks, balance technical excellence with delivery, and take ownership of outcomes even when multiple factors are involved.
EasyTechnical
0 practiced
Define "scope creep" in the context of a software project and explain why it undermines delivery. Provide two concrete, measurable signals you would monitor during a two-week sprint to detect scope creep early (for example: number of added unplanned story points, frequency of mid-sprint story additions). For each signal describe the specific immediate action you would take as the engineer responsible for delivery (e.g., freeze scope, re-estimate, escalate to PM) and how you would record that action.
MediumTechnical
0 practiced
A critical engineer with unique domain knowledge announces resignation two sprints before a major release. Create a knowledge transfer plan that balances speed and thoroughness: include documentation checklist, pairing schedule, code ownership updates, temporary backup assignments, and a minimal acceptance criterion that indicates the team can proceed without that engineer.
MediumTechnical
0 practiced
You own a feature where three other teams (API, Auth, Billing) provide critical inputs. Midway through your sprint, one dependency team signals a 6-business-day delay. Draft a mitigation plan covering: immediate actions (0–48 hours), medium-term actions (this sprint and next), how you would update stakeholders (format and cadence), and how you'd adjust sprint commitments and acceptance criteria to preserve delivery confidence.
MediumTechnical
0 practiced
Write pseudocode or a short Python function to estimate a project's ETA using remaining story points and the last three sprint velocities. Show how you would compute a simple confidence interval (e.g., using sample mean and sample standard deviation) and explain limitations of this approach for stakeholders who ask for a single date.
HardTechnical
0 practiced
Propose a set of SLIs, SLOs, and an error budget policy for a high-throughput service that must innovate quickly while maintaining reliability. Provide example numeric thresholds (e.g., availability 99.95% monthly, p99 latency < X ms), describe how you would measure and aggregate these metrics, and explain how error budget consumption would gate releases or trigger mitigation actions.
Unlock Full Question Bank
Get access to hundreds of Project Delivery and Accountability interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.