USE CASE
Designing as an interviewer
Start with reviewed core questions. The extended library remains available below for broader exploration.
994 questions
Extended library · not reviewed question by question
These questions remain useful for discovery, but have not received the same question-specific review as the core set.
Extended questions 701–750 of 931 on this page.
A · Professional problem solving and implementation7
- An operations table uses red, yellow, and green for risk. Some users cannot distinguish the colors, and screen readers announce only values. How would you redesign the information?
- A feature targets people who have never used the product, but all usability participants are core users. Which design decisions can the current evidence support?
- After submitting a form, users see “validation failed,” with no field identified and no entered data preserved. How would you redesign the error and recovery path?
- A desktop admin table has 14 columns, while mobile users need to handle exceptions in the field. How would you decide what to retain, hide, or move to details?
- A dashboard flags anomalies but shows no magnitude, baseline, or related events. Users export data to interpret it themselves. How would you improve diagnosis?
- Review feedback centers on “not premium enough” or “I dislike this color,” but the team has no shared user goal. How would you run the next review?
- Several product teams override shared component styles with CSS, causing frequent regressions after upgrades. How would you choose between adding configuration, splitting the component, or keeping exceptions?
No questions in this section match your target. ·
B · Business understanding and domain modeling8
- Revenue was recognized for an order last month, and a partial refund occurs this month. Finance and growth disagree on order count, net revenue, and refund-month treatment. How would you establish consistent data semantics?
- A service rebuilds state from an event log, but the live snapshot differs and responders cannot tell which to repair. How would you define authority and the repair process?
- A promotion starts at local midnight, services run in UTC, and customers may move regions. How would you represent effective time and handle boundary invoices?
- After a feature definition is fixed, the modeling team wants a historical backfill. Training reproducibility requires the original version, while business reports want corrected values. How would you design both views?
- Last month’s usage arrives this month. The contract bills monthly and paid invoices cannot be silently overwritten. How would you handle adjustments and notification?
- Payment is authorized but not captured, and goods are not fulfilled. The business report counts an order, while finance records no revenue yet. How would you define and reconcile order, payment, revenue, and cash metrics across domains?
- Risk teams need to reproduce decision inputs from three months ago, but the online feature store keeps only the latest state to save cost. How would you balance reproducibility and storage cost?
- High-revenue customers frequently request urgent support, consuming team capacity and delaying critical issues for others. How would you define service prioritization?
No questions in this section match your target. ·
C · Value judgment and direction setting9
- Task completion reaches 95%, but half of users rely on support or colleagues. The team plans to use completion as its launch-success metric. What would you add?
- The same customer submits changing feature requests, all pointing to delayed month-end reconciliation. How would you uncover the underlying problem and validate priority?
- Three teams propose shared-capability projects, each citing different future benefits with no near-term customer commitment. How would you validate and sequence platform investments?
- The team completed its top-ranked projects, but engineers with critical skills are idle while other teams are overloaded. How would you improve allocation?
- During a randomized experiment, the platform changes pricing policy and affects treatment and control differently. How would you decide which conclusions the experiment still supports?
- Sales promised a customer a feature, but the roadmap has no capacity and the dependency team has not scheduled it. How would you handle expectations and internal decisions?
- A new feature reaches only half its adoption target, but many target users have not received training or access. How would you diagnose and adjust the plan?
- Brand advertising expands reach, but short-term direct conversions do not change and the sales cycle may last months. How would you decide whether to wait, change creative, or stop?
- A recommendation algorithm changes content ranking and creator supply, so treatment behavior changes what the control group can see. How would you assess the experiment design?
No questions in this section match your target. ·
D · Delivery and ongoing operations11
- 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?
- 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?
- 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?
- 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?
- 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?
- 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?
- 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?
- Scope is frozen and acceptance is underway when compliance identifies a new mandatory requirement. Releasing as planned creates audit risk. How would you respond?
- The monthly cloud bill is under budget, but cost per transaction keeps rising; temporarily lower volume hides efficiency regression. How would you govern cost?
- 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?
- 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?
No questions in this section match your target. ·
F · People and organization building7
- A normally reliable teammate has slowed down while carrying three cross-team projects and mentoring a newcomer. How would you diagnose and respond?
- The organization expects a fixed number of promotions this quarter, but candidates show uneven scope and impact evidence. How would you facilitate calibration?
- After a key leader leaves, a potential successor handles most responsibilities, but pay, decision rights, and external title have not changed. How would you manage the transition?
- A critical vacancy delays delivery and the business wants an offer within a week. A candidate has strong experience but unclear integrity signals. How would you balance speed and standards?
- Interviewers give referred candidates more benefit of the doubt for vague answers and score others strictly. How would you reduce this bias?
- A first-round interviewer writes “not capable,” so later interviewers only probe weaknesses. How would you design evaluation and information sharing?
- After a reorganization, projects continue but interfaces and informal coordination links disappear, and issues bounce between teams. How would you restore accountability?
No questions in this section match your target. ·
G · Learning, adaptation, and sustained growth5
- A teammate repeatedly delivers through crises, but recovery takes longer each time and routine errors are increasing. How would you respond?
- The team correctly identifies an incident’s root cause and records improvements, but operating habits have not changed months later. How would you evaluate the retrospective?
- The organization has no clear promotion timeline, but you want to keep growing. How would you choose learning, influence, and delivery goals without chasing visibility alone?
- Several teams have adopted a plan you championed, then you discover a key assumption is false and continuing will increase rework. How would you correct course?
- A project was cancelled for insufficient market demand, but its technical capability may be reusable. How would you decide what to retain, transfer, or stop investing in?
No questions in this section match your target. ·
H · Professional responsibility and work style3
- A quarterly update describes correlation as causal growth. The owner wants to publish on time and validate later. How would you respond?
- A role offers significant growth but repeatedly requires night responses and shifting priorities. How would you assess staying, renegotiating, or leaving?
- After proactively taking on a cross-team issue, your original project begins slipping. The team also depends on you for the new issue. How would you address priorities and boundaries openly?
No questions in this section match your target. ·