Situational & Hypothetical
Prioritization Scenarios
23 practice questions. Free questions open a full answer guide; the rest unlock with Pro.
- You find a bug in production code that you didn't write and that's outside your current sprint scope. What do you do?
- You committed to finishing a task by Friday because another team is blocked on it, but by Wednesday you realize it'll take until the middle of next week. What do you do?Go Pro
- A senior stakeholder wants to ship a model you don't think is ready — the offline metrics look fine but you have real concerns about fairness or edge-case behavior. They're pushing hard on the timeline. What do you do?Go Pro
- Your team is asked to cut scope by 30% to hit a budget reduction target. How do you decide what to cut without killing the product's strategic momentum?Go Pro
- You discover that a developer accidentally committed AWS credentials to a public GitHub repository 3 hours ago. What do you do?Go Pro
- Mid-year, the CFO tells you to cut your engineering org's operating budget by 20% within the quarter, with no specific guidance on where. Your teams are already fully committed. How do you decide what gives?Go Pro
- You're two days from a launch deadline when you discover that one of the input features your model relies on is actually leaking the target — it's only available after the outcome you're predicting has happened. What do you do?Go Pro
- A managed service you depend on heavily across many production systems announces end-of-life with a hard cutoff date, and there's no drop-in replacement. You have to drive the migration across several teams that don't report to you. How do you approach it?Go Pro
- Your team has limited capacity and you have to choose between building a flashy new model the business is excited about and paying down unglamorous data-quality or pipeline debt that's been slowing everyone down. How do you make that call?Go Pro
- The company decides to adopt a new technology stack that half your engineering org has little experience with. You have 18 months before the old stack is deprecated. How do you approach the transition?Go Pro
- A daily data pipeline you own feeds a dashboard the leadership team reviews every morning. It fails silently overnight and serves stale numbers, and an exec makes a call based on yesterday's data before anyone notices. How do you respond in the moment and afterward?Go Pro
- You're mid-task when you realize your approach won't work and you need to start over with one day left before the deadline. What do you do?Go Pro
- A model you deployed three months ago is still hitting its accuracy target on the weekly batch eval, but the product team reports that user complaints about its recommendations have been climbing. What do you do?Go Pro
- Your product VP wants to accelerate a major feature launch by six weeks by cutting the QA phase entirely. You believe this will cause serious customer-facing issues. How do you handle it?Go Pro
- A key engineer on your team just told you they're leaving in two weeks. The team is mid-sprint on a critical launch. How do you handle it?Go Pro
- You're asked to build a model to flag accounts for additional review, and you realize the historical labels you'd train on were generated by a past human process that may have been biased against certain account types. The team just wants you to 'train on the data we have.' How do you proceed?Go Pro
- Your A/B test for a new ranking model has run for two weeks. The primary metric is up 1.2% but the result isn't statistically significant, and a secondary metric the business cares about is slightly down. The PM wants to ship it. How do you handle this?Go Pro
- A senior engineer on your team begins missing deadlines and seems disengaged. They were previously your strongest performer. What do you do?Go Pro
- It's the middle of the fiscal year and the flagship product line your org owns is tracking at roughly 40% of its annual revenue target. The CEO wants a recovery plan in two weeks. How would you approach it?Go Pro
- You're convinced a piece of reliability or security work is critical, but leadership has deprioritised it for the next quarter in favour of feature delivery. How do you handle that?Go Pro
- You're three weeks from a major launch when engineering tells you a key feature will not be ready. You can delay the launch, ship without the feature, or descope something else to free up capacity. What do you do?Go Pro
- After a model has been live for a month, you discover the offline evaluation that justified shipping it was flawed — say, label leakage made the metrics look far better than reality. How do you respond?Go Pro
- Your team is about to ship a feature and you spot a potential security issue in the last hour before deployment. What do you do?Go Pro
Want questions matched to your role? Paste a job title, job description, or CV for a personalized set, or go Pro to unlock the full bank.