DOMAIN D
Delivery and ongoing operations
How to turn a goal into dependable action, then run, correct, and close the loop.
See this capability domain in stage expectations. Open the capability model
Choose a capability first. Each preview shows up to three questions; open it for focused batches.
162 questions · 5 capabilities
Problem decomposition26
Breaking a vague goal into estimable, verifiable work.
- For three consecutive quarters, several teams underestimated integration and acceptance time. How would you use forecasts and actuals to determine whether the error comes from estimation, scope change, or scheduling, and improve the next forecast?
- The business asks to “improve customer experience” without a clear pain point or deadline. How would you decompose it into verifiable problems, workstreams, and milestones? Follow-up: If a critical dependency slips by one cycle, how would you re-sequence the critical path, reset commitments, and reduce waiting?
- The requester has prescribed a service rewrite, but incident data points to several possible causes. How would you return to problem definition and decide the validation order?
- A business partner brings you a problem that is not clearly defined. What sources would you check, whom would you consult, and how would you separate confirmed facts from assumptions? How would you turn the findings into an actionable plan?
- Different teams provide conflicting data and explanations for the same business problem, while the project is already planned for this quarter. How would you decide what to investigate first and what to defer?
- Tell me about the most complex feature you owned. How do you break a vague business request down, step by step, into a requirements document without logical gaps, and how do you design fault tolerance and interaction for edge cases such as a lost connection or an abnormal account?
- Halfway through a project, available capacity suddenly drops by half while the deadline stays fixed. How would you resequence work and reset expectations?
- A customer asks for “a real-time dashboard,” but their examples suggest they only discover inventory errors later in the day. How would you guide the discussion?
- You receive a request in an area you have never worked in. How do you break it down and give an estimate that can be checked later?
- An identity-field change affects clients, APIs, the warehouse, and external partners, but the initial plan lists only server development and a front-end update. How would you decompose the dependency graph and find missing migration, rollback, and acceptance work?
- A request says only “reduce user form time,” without explaining optional fields, consequences of bad data, or workflow differences. How would you decompose research, interaction design, technical validation, and outcome acceptance?
- The goal is to improve purchase conversion, but traffic quality, page comprehension, payment options, and inventory can all affect it. How would you split the goal into diagnostic work, leading signals, and staged decisions?
- The team plans to move order data to new storage, switching reads first and writes later; the plan includes development and launch but lacks data-difference checks and rollback criteria. How would you complete the migration breakdown?
- Product considers a feature complete when it launches, Operations requires training and monitoring, and the customer expects successful migration from the old flow. How would you clarify outcomes, deliverables, and acceptance ownership?
- A new system depends on unverified third-party capabilities, so the full implementation cannot be estimated accurately; leadership still needs a credible time range. How would you sequence technical probes, risk validation, and delivery stages?
- The business wants fewer complaints, but issues arrive through apps, phone support, and partner handoffs; existing data cannot identify the same problem across channels. How would you decompose instrumentation, identity linkage, workflow changes, and outcome measurement?
- A regulatory requirement has a fixed effective date, while Product wants to improve the experience; both depend on a backend change, but experience research is unfinished. How would you separate mandatory compliance scope from iterative experience work?
- A delivery goal spans client, server, data, and operations, and the outcome depends on all parties being ready. How would you split the workstreams, identify the critical path, and plan integration checks?
- A cross-team project receives new business feedback every week, invalidating parts of its task breakdown. How would you distinguish stable goals from changing assumptions and design work slices that can absorb change?
- A new system must gradually replace a legacy one while both serve real users, with data and functionality switching in batches. How would you decompose the migration, validation points, and rollback conditions?
- The team believes rework is excessive, but some count bug fixes, others requirement changes, and others code rewrites. How would you define the problem and set an improvement target?
- Leadership asks for higher engineering productivity next quarter without defining it. Some propose increasing commits; others want fewer meetings. How would you establish an improvement direction?
- Several product teams aim to reduce complaints, but categories, channels, and ownership differ. How would you define a shared measure and team actions?
- The team lists release quality as a quarterly priority, but some focus on rollbacks, others on defects, and others on speed. How would you define a shared outcome?
- Identity, frontend login, and support tools all shipped on time, yet new customers still cannot open an account. How would you define integration ownership and end-to-end acceptance?
- A shared component already has many variants, and a new use case requests another special state. How would you weigh reuse, complexity, accessibility, and maintenance?
No questions in this section match your target. ·
Capacity and dependencies34
Capacity, dependencies, commitments, and resource conflicts.
- A serious production incident pulls two specialists from a project team for a full week, putting a milestone at risk. How would you update the forecast, separate incident and project responsibilities, and help stakeholders make trade-offs?
- A project depends on another team for an interface or data contract, but there is no clear delivery owner, plans keep changing, and the work may not fit next quarter’s schedule. How would you establish a commitment, prepare alternatives, manage critical-path risk, and decide when to escalate or change scope?
- Faced with a large problem that is still unclear, how do you plan how many people and resources are needed? How do you estimate under uncertainty, invest in stages, and ask upward for resources?
- A team has held delivery for months only by working overtime. How do you tell whether it is a people problem or a capacity gap, and what do you do?
- Incidents and recovery work interrupt every iteration, and roadmap commitments keep slipping. Leadership wants the dates preserved without adding staff. How would you propose capacity and goal changes?
- For several quarters, production support, customer escalations, and cross-team requests have displaced roadmap work. Someone proposes a universal 20% reserve, though interruption rates vary. How would you set the reserve?
- How do you work out what your team can really commit to next cycle, rather than headcount times working days?
- When you made this decision, what resources did you have and how wide was your scope of collaboration? How did those limits shape your choices?
- Three projects list the same platform team as a critical dependency, and all buffer time is allocated. A new regulatory requirement must ship before quarter-end. How would you reallocate capacity and commitments?
- One owner is responsible for four high-priority projects. Status reports look normal, but risk handling, cross-team decisions, and retrospectives are all delayed. How would you decide whether to add support, reassign ownership, or reduce the portfolio?
- Several teams list the same domain expert as a critical-path resource and each plan assumes full-time support. How would you establish capacity facts, compare dependency risk, and negotiate a deliverable arrangement?
- Every initiative in the quarterly portfolio is labeled top priority, but Product, Data, and Security lack capacity to support them all. How would you standardize priority definitions, expose dependencies, and make resource trade-offs?
- The plan allocates one week for design before development, but the work includes user research, accessibility review, and interaction validation; designers also support several products. How would you re-estimate design capacity and dependency order?
- A team owns product changes and customer-support rotations; support demand rises in peak seasons, while plans still reserve a fixed percentage. How would you use workload evidence to create flexible capacity and service priorities?
- A mobile release depends on app-store review with variable duration; backend and web can launch earlier, but a marketing campaign has a fixed date. How would you plan release windows, feature flags, and cross-platform degradation?
- Several teams use one deployment pipeline and fixed maintenance windows, but their changes differ in size and rollback readiness; one team's delay steals validation time from others. How would you plan release capacity and resolve conflicts?
- Several teams rotate on-call for core services, but plans count only project hours; incident investigation and drills displace planned work, and service loads vary widely. How would you forecast capacity and create a fair cross-team model?
- A project estimates only two weeks of implementation but often takes two months because design review, legal approval, and data access queues. How would you separate work time from wait time and negotiate capacity changes to reduce queues?
- Only one senior engineer understands a core module. The team wants that person to deliver roadmap work and onboard two successors, while the business worries about short-term output. How would you estimate capacity for knowledge transfer and its long-term risk and value?
- Annual project funding is approved, but critical roles remain unfilled and outsourcing is limited by security requirements; another team has available people but needs role changes. How would you compare delay, scope reduction, internal transfer, and budget reallocation?
- After a project starts, a key domain expert leaves and no replacement is ready. The team can wait, change sequencing, or narrow the first release. How would you assess capacity and dependencies and update commitments?
- The team has been interrupted by unplanned support work for three quarters and commitment completion has fallen. Leadership wants everyone fully booked to raise utilization. How would you propose a more reliable plan?
- A vendor’s committed throughput is below peak-season forecast, and migration to an alternative takes two months. How would you plan capacity and business constraints?
- A shared platform team is preempted weekly by new business requests, delaying reliability and migration commitments. How would you design intake, capacity, and prioritization?
- After a hiring freeze, the team has 30 percent fewer hours next quarter, but the business goal and date remain unchanged. How would you offer credible commitments without defaulting to overtime?
- The team plans all capacity for new features, while incidents and customer escalations interrupt delivery. How would you use historical data to set and review a support reserve?
- A migration needs two weeks of platform support, but that team can offer only half a day each week. How would you compare waiting, parallel work, interface freezes, and scope reduction?
- After hiring, throughput remains flat while review queues and coordination time rise. How would you separate onboarding cost, work allocation, and system bottlenecks?
- A strategic project has consumed senior engineers for two quarters, delaying maintenance and security work. How would you show opportunity cost and present capacity options?
- The plan assumes three shared workdays each week, but local holidays and support rotations reduce overlap. How would you build a realistic calendar and response agreement?
- After a key operations lead leaves, the team wants to spread the work evenly. Some tasks require specific access and experience. How would you route, pause, and escalate the work?
- Four plans underestimated review and rework time. Leaders demand more accurate estimates. How would you improve the process, record uncertainty, and avoid turning estimates into a blame metric?
- Two business units promised customers the same delivery window, but shared capacity can support only one. How would you present scope, timing, quality, and customer-risk choices?
- Five channels have different levels of maturity, so their short-term returns are not directly comparable. How would you allocate baseline funding, exploration budget, and review dates?
No questions in this section match your target. ·
Project and PMO practice35
Cadence, risk, change control, and cross-project coordination.
- Project requests backed by senior sponsors tend to move ahead, while compliance and infrastructure work without executive sponsorship repeatedly slips. How would you create a transparent portfolio intake and prioritization process?
- The organization requires every project to use the same weekly reports, reviews, and approval gates; a small exploratory effort now spends more time reporting than executing. How would you design tiered governance without missing high-risk work?
- A project depending on a platform interface is already integrating when the upstream team announces a semantic change this quarter and cannot support both formats indefinitely. How would you decide compatibility, migration order, and release boundaries across projects?
- Four months after delivery, the targeted cost reduction has not appeared in financial reports. The sponsor says the system is still in a learning period, while finance considers the project closed. How would you clarify benefit ownership and the validation window?
- A new service launches on schedule, but the project team is moving to other goals; on-call ownership, documentation, cost monitoring, and follow-up improvements have no clear owners. How would you determine whether the project is ready to hand off?
- After a strategic shift, several in-flight projects no longer support the new goals, but teams have invested effort and made external commitments. How would you decide what to stop immediately, what to close out, and how to transfer knowledge, contracts, and capacity?
- A new regulatory requirement makes the original scope impossible, yet teams still cite old milestones. How would you update baselines, dependencies, and external expectations?
- A project stays green until a critical data migration is found untested just before launch. How would you improve status signals and decision cadence?
- Three projects independently build similar permission and notification capabilities, each seeming reasonable alone. How would you detect portfolio-level duplication and change governance?
- Five projects flag the same platform dependency as a possible delay, yet each remains green. What evidence would tell you to change the portfolio instead of following up project by project?
- Two weeks before launch a stakeholder asks for one more feature. How do you decide to accept, defer, or decline, and what do you record?
- What was the biggest challenge in this project? Why was it hard, how did you push it forward at the time, and how did it end?
- A business lead says change approval slows market opportunities and asks teams to insert requests outside review. Past urgent work has caused rework. How would you design an exception path?
- A release date has been promised externally, but teams keep requesting features and fixes. How would you decide when to freeze scope, which exceptions to allow, and who owns replanning consequences?
- Engineering tells you that, because of the underlying architecture, the feature you specified will slip two weeks, while the business side wants it tomorrow. How do you cut half the features in a short time and keep a minimum viable version that can ship, and what do you rely on to decide what stays and what goes?
- How do you measure engineering effectiveness? Which metrics do you choose, how do you keep the numbers from being gamed, and how do you turn the measurement into real improvement?
- You are leading a project across engineering, design, and operations. How would you clarify the shared goal and responsibilities when each group defines success differently?
- A key vendor has delayed an interface twice, but the project plan still uses the original date. Internal teams are building a temporary adapter in parallel. How would you reset the baseline, account for added work, and show leadership which commitments remain credible?
- Two projects' schedules collide and both need the same people. What do you do, how do you turn the conflict into options that can be discussed, and how do you get both sides to accept the result?
- Three weeks into a project you find two risks nobody owns. How do you make them manageable?
- Five projects each look reasonable by their own value ranking, but they share three sequential dependency teams and cannot finish within the quarter. How would you identify portfolio bottlenecks, resequence work, and decide whether to split delivery?
- A business sponsor leaves before a project is complete; the replacement values different measures, yet the team continues spending to the old plan. How would you reconfirm benefit assumptions, ownership, and continuation criteria?
- Project plans list dependent teams but no delivery owners or confirmed dates; each project looks feasible alone, while the portfolio may compete for the same capacity. How would you build dependency commitments and a risk view?
- Several projects use budget and time as planned, but key business outcomes show no visible change; status reports mainly count completed tasks. How would you redefine portfolio progress measures and support resource changes?
- A project has requirements, design, testing, and launch reviews, but complete documents do not prove key assumptions; risks often surface only in the meeting. How would you make stage gates real decision checks?
- A vendor failure blocks a critical project. Business, Engineering, Legal, and Finance need information, but several status meetings delay action. What information would you send to whom, and in what order, to identify a decision owner and next steps quickly?
- Halfway through a project, several stakeholders keep adding important requests while the launch date and team capacity stay fixed. How would you establish change decisions and keep scope, risk, and commitments transparent?
- The plan calls for a full launch by quarter end, but core data authorization and compliance review are unresolved. How would you set stage gates so preparation can continue without creating irreversible investment before key conditions are met?
- Several departments share a project, and no one owner can allocate all resources. Issues stay in meeting notes without anyone confirming the decision. How would you clarify decision rights, escalation, and follow-up?
- The main feature is live, but edge cases, operating documentation, and one downstream integration remain unfinished. The team wants to close and free capacity; the business worries the leftovers will be orphaned. How would you decide closure criteria and assign follow-up ownership?
- A project is nearly complete, but the business sponsor has left and the receiving team has no clear owner. How would you handle acceptance, handoff, and unresolved risk?
- Three projects need an integration environment that cannot be shared concurrently. Release dates are close and they depend on the same test team. How would you set scheduling rules and contingencies?
- Scope is frozen and acceptance is underway when compliance identifies a new mandatory requirement. Releasing as planned creates audit risk. How would you respond?
- Engineering reports risk weekly, while the monthly business dashboard remains green and leadership commits resources based on it. How would you align reporting semantics?
- The feature shipped as planned, but approval came after the enrollment season, so meaningful use waits six months. How would you review commitments, critical path, and staged delivery?
No questions in this section match your target. ·
Operational execution43
Landing a strategy, running experiments, and sustaining operations.
- An onboarding experiment does not change overall signup-to-activation conversion, but activated users complete their first key task sooner. How would you decide whether to roll it out and revise the definition of success?
- During a major promotion, landing-page traffic meets expectations but add-to-cart and order rates are far below target. How would you quickly distinguish traffic quality, page information, pricing rules, inventory, and fulfillment issues?
- A limited-time promotion launches, but popular products run short. Some channels have already promised availability while others continue sending traffic. How would you adjust promotion, page promises, replenishment, and customer communication?
- A brand campaign has delivered its planned total impressions, but actual reach among the core target audience is below expectation, and one-third of the budget remains. How would you decide whether to continue, change the media mix, or revise the objective?
- A community event has strong registration and interaction numbers, but participants rarely continue using the product or contributing content afterward. How would you locate where the connection to product value breaks and design the next operating cycle?
- To meet a quarterly goal, a partner asks to expand promotion delivery at short notice. An initial check suggests the new audience may exceed agreed authorization and brand boundaries. How would you move the decision forward within the deadline?
- A campaign creative gets high engagement on social channels but almost no conversion in search or stores. Another version has ordinary engagement but stronger sales. How would you decide on creative iteration and channel allocation?
- A broad discount meets the overall sales target, but valuable existing customers view it as unfair, and some users delay purchases they would have made anyway. How would you adjust future audiences and offers?
- A discount briefly increases volume, competitors follow, and category prices and margins decline. How would you decide whether to keep matching, change the value proposition, or exit the promotion?
- A new product misses its first-week sales target, yet trial users show strong usage depth and referral intent. How would you determine whether the issue is reach, a longer purchase cycle, price threshold, or positioning, and decide what to invest in next?
- A new-customer offer generates many registrations, but most users do not complete the first key action and the discount cost has already been incurred. How would you plan follow-up and decide which users merit further investment?
- A channel has a low acquisition cost in a small test, but lead quality and conversion fall as spend increases. How would you validate the cost definition and true incrementality, distinguish channel saturation from audience or sales-capacity changes, and set a limit for additional spend?
- A campaign brings in many new users, but support, moderation, and plans for following up with users and helping them complete a key action are not ready. How would you design ownership and capacity before and after the campaign?
- Operations staff directly change customer states, and later no one can explain who changed what or why. How would you design for efficiency, permission, and auditability?
- Describe a re-engagement or referral campaign you contributed to as an engineer. Which systems, data, or delivery work did you own, how did you clarify budget and key user behavior with operations, and how did you verify incremental impact and your actual contribution?
- The promotion strategy is set and you are responsible for execution. What goals, rules, resources, risks, and acceptance criteria would you confirm before launch?
- Sales, support, and engineering can all label customer issues top priority, so the queue cannot distinguish business outages from general dissatisfaction. How would you design severity and escalation?
- When managing a large platform ecosystem, gray areas such as fake orders, abusive bonus hunting, and borderline content often appear. How do you build a governance mechanism that does not harm the healthy ecosystem, and how do you build the defense together with risk control, legal, and technology teams?
- You are about to run a growth experiment in production. What checkpoints and stop conditions do you prepare first?
- How would you move from one-off campaigns and acquisition toward automated, data-informed lifecycle operations? Describe a case where data tracking and algorithms turned manual work into repeatable rules.
- A two-sided platform has a local supply-demand imbalance: peak-time orders exceed available providers, or a new city has providers but too few users. How would you identify the main constraint and adjust pricing, incentives, or supply while controlling cost and long-term effects?
- A strategic change requires you to shut down at once a business that brings many users but has lost money for years. How do you, in the shortest time, reassure thousands of affected partners, complete the wind-down compliantly and smoothly, and prevent a group public-relations crisis?
- A critical operations playbook is still used by multiple regions, but its author has left and recent system and policy changes were never incorporated. How would you identify which steps remain safe, establish temporary controls and ownership, and verify that frontline teams can use the new version correctly?
- An automated approval service stops working, so the operations team temporarily switches to a spreadsheet and limits user impact. Two weeks later, the service is still down, and the spreadsheet has inconsistent permissions and records. How would you manage the temporary process, restore automated approvals, and decide when to shut it down?
- A new manual-review policy is deployed across regions, but teams handle edge cases differently and outcome data is delayed. How would you set up training, frontline feedback, sample review, and policy adjustment?
- A major campaign overlaps with holidays, and support, review, and supply teams expect to run short on capacity; the campaign is already public. How would you plan staffing, control incoming demand, inform users, and escalate exceptions?
- The operations dashboard produces many low-value alerts, so on-call staff begin ignoring notifications; a critical fulfillment failure is also missed. How would you tier signals, assign response ownership, and verify alert quality?
- An acquisition campaign over-delivers on some channels while assets fail to launch on others; Operations wants immediate normalization, but Growth needs a valid control. How would you coordinate containment, record deviations, and continue evaluation?
- An external provider's response time and first-contact resolution worsen for several weeks, but the contract specifies only a monthly average SLA; internal teams repeatedly compensate. How would you design segmented monitoring, reviews, remediation, and contract changes?
- Operations manually grants replacement benefits to resolve complaints quickly, but weekly compensation volume keeps rising and causes are classified inconsistently. How would you protect users now and turn compensation data into product-fix signals?
- A business process success rate has declined for two weeks without obvious data alerts, and support feedback is fragmented. How would you organize operational diagnosis, interim action, and validation?
- An operations team uses multiple shifts, and important issues are often lost at handoff with inconsistent records. How would you design handoff information, ownership confirmation, and exception escalation?
- Customer escalations have risen sharply over the past month. Frontline staff blame a few complex customers, while leaders suspect a broken process. How would you distinguish isolated cases from a systemic issue and validate it?
- The company updates its refund policy, but support, finance, and regional operations use inconsistent guidance, and some customers have received different outcomes. How would you drive adoption and verify execution?
- A human-operated pilot worked in two regions, but after expansion to ten, handling time and error rates both rise. How would you identify scaling bottlenecks and adjust the operating model?
- A team spends two weeks clearing a backlog and metrics briefly recover, then deteriorate again over the following months. How would you embed effective parts of the intervention into daily operations while controlling ongoing cost?
- When channel reports conflict, how would you find differences in their counting rules, time windows, and data sources?
- The same remediation command has different effects in two regions, but the runbook describes only the default topology. Responders may use it in the wrong environment. How would you revise and prevent recurrence?
- Disaster-recovery drills notify every team a week in advance, and special scripts make the exercise succeed while real recovery still fails. How would you redesign the drill?
- The monthly cloud bill is under budget, but cost per transaction keeps rising; temporarily lower volume hides efficiency regression. How would you govern cost?
- Monitoring automatically restarts unhealthy services, but this incident originates in a shared data layer and mass restarts could amplify connection storms. How would you bound automation?
- A promotion increases orders but also increases return inquiries and manual reviews. The budget has room left. How would you decide whether to expand the campaign, limit new traffic, or improve the process first?
- A new approval flow reduces average handling time, but employees seek exceptions through private messages and audit records decline. How would you determine whether the process truly improved?
No questions in this section match your target. ·
Reliability and incidents24
Observability, incident response, containment, and follow-through.
- A data-write incident has stopped and service metrics look normal, but users still report missing records. How would you organize recovery validation and follow-up communication?
- A release project has capacity, vendor-delivery, and data-quality risks, each below its individual escalation threshold, but all may converge in the same week. How would you assess the combined risk and decide what action to take?
- When a payment-risk dependency slows, checkout times out. The business wants to preserve conversion without bypassing critical safety checks. How would you decide which checkout functions can be temporarily disabled and which checks must remain?
- A campaign goes live overnight, but heavy traffic stalls the system. Users cannot claim coupons and start complaining. As an engineer involved in the campaign, how would you coordinate with operations and support on temporary business measures while restoring the system?
- A system keeps having problems again and again, and each fix is followed by another failure. How do you find the root cause, how do you move the team from firefighting to real repair, and how do you show it no longer recurs?
- A production service suddenly fails widely. In what order do you act during the first hour?
- A major incident produces 18 actions across architecture, monitoring, training, and process, but teams already have quarterly commitments. How would you select actions that reduce recurrence risk?
- How do you keep the same kind of personal mistake from happening again? Did you improve the process and tooling, or just remind yourself to be careful? How do you know the improvement works?
- During an outage, engineering wants to disable a feature, business wants to keep accepting orders, and support has promised a recovery time. Responders receive conflicting directions. How would you organize the response?
- A mobile release goes to 5% of users. The crash rate appears to double, but active devices are few and mostly one older model; a marketing campaign is near. How would you limit harm, gather evidence, and decide whether to continue, pause, or roll back?
- An incident is resolved, and the review lists more than ten actions for monitoring, capacity checks, and documentation; earlier actions were never verified. How would you assign owners and dates and confirm whether improvements worked?
- After a mobile release, network failures rise while server metrics remain normal; affected users cluster on older OS versions and weak connections. How would you scope the incident, reduce impact, and decide whether to pause or roll back?
- A core service is partially unavailable and the cause is unknown; customers, executives, and partners request updates, while the team worries that early communication could mislead. How would you separate known facts, hypotheses, actions, and the next update time?
- A critical dependency vulnerability needs prompt remediation, but the patch may conflict with the current release candidate; delay prolongs exposure, while immediate rollout could disrupt service. How would you plan validation, temporary mitigation, and release authorization?
- A consumer failure leaves a queue hours behind; after repair, many old messages will replay into billing, notifications, and analytics, which have different capacities and side effects. How would you control recovery rate and protect consumers?
- After a core dependency outage, most functionality has returned, but errors remain above baseline and upstream backlogs keep growing. The business wants full traffic restored quickly. How would you set recovery criteria and traffic ramp-up?
- A failure went unnoticed because monitoring missed a critical user path until support escalated it. The review calls for more monitoring, but the team must show it detects issues earlier without creating excessive noise. How would you validate the change?
- After a release, login, payment, and notification services fail in succession. Each team believes its incident is most urgent, and some alerts may share one root cause. How would you coordinate response, prioritize, and avoid interference?
- An outage did not meet the threshold for a major customer incident, but affected a small group and exposed process gaps. How would you decide whether and how much to publish?
- Upstream events are delayed by hours, while downstream reports still show success and customers make incorrect decisions. How would you design freshness states and notifications?
- The business depends on a third-party API with no formal SLA and inconsistent support. How would you set internal continuity goals and fallback options?
- A third-party service has recovered, but callbacks may have been lost during the outage. Customer-visible state differs from the platform record. How would you confirm impact and communicate?
- The outage is resolved, but some customers still have incorrect balances and promised compensation is pending. How would you define closure and continuing ownership?
- A release breaks reads, but the previous version cannot read the new data format. How would you contain impact and compare rollback, forward fix, and a compatibility layer?
No questions in this section match your target. ·