USE CASE
External job interviews
Start with reviewed core questions. The extended library remains available below for broader exploration.
1324 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 301–350 of 1229 on this page.
A · Professional problem solving and implementation14
- After deployment on a multi-socket machine, threads move across NUMA nodes and memory latency varies. How would you investigate using CPU affinity, memory placement, and scheduling behavior?
- After certificate rotation, short connections work, but some clients fail a handshake when reconnecting or resuming after a long-lived connection closes. How would you distinguish certificate-chain, resumption, connection-pool, and client-cache effects?
- When a mobile device switches from Wi-Fi to cellular, some HTTP/3 requests fail while the session still appears online. How would you investigate path migration, timeouts, and middlebox behavior?
- A program writes a data file before updating its index, but after a power loss the index points to incomplete content. How would you analyze write ordering, flush semantics, and recovery?
- Average latency is stable while p99 worsens, with large differences across tenants. How would you narrow the cause to queuing, lock contention, downstream fan-out, or resource isolation?
- At peak load, the entry service records a request but downstream events are missing, while retries amplify traffic. How would you trace the request through each service to locate loss and duplication?
- Several tenants share an asynchronous job platform, and some submit many long-running tasks. How would you define fairness, design scheduling and isolation, set quotas, and observe queue behavior?
- Some objects become hot, degrading reads while writes must remain ordered. How would you divide caching, partitioning, and write coordination?
- The business needs every state change to be traceable and safely replayable, but some old events lack fields. How would you design event versions, retention, and replay boundaries?
- A multi-region service must preserve critical functions during a regional outage, but some data cannot tolerate conflicting overwrites. How would you choose degradation, replication, and recovery policies?
- A real-time collaboration service has many long-lived connections, and slow clients accumulate updates. How would you choose between dropping, combining, limiting updates to slow clients, and resynchronizing?
- Teams share a repository but release at different cadences; shared package changes often block unrelated teams. How would you design boundaries, impact analysis, and release agreements?
- The same release behaves differently across clusters, and configuration changes are not fully audited. How would you establish configuration sources, drift detection, and rollback?
- Offline evaluations keep improving while a specific user segment regresses online. Which data leakage, slice coverage, and deployment differences would you investigate?
No questions in this section match your target. ·
B · Business understanding and domain modeling7
- The team plans to enter an adjacent market where users, payers, and fulfillment parties differ. How would you map the value chain and determine whose problem the product should solve first?
- Teams define “done,” “awaiting acceptance,” and “paused” differently, distorting roll-up data. How would you design a shared state model and transition rules?
- A user can belong to several organizations and hold different roles in each. How would you model identity, membership, and permissions without conflating accounts with business roles?
- Customers upgrade, downgrade, or pause subscriptions mid-cycle, while sales and finance disagree on revenue recognition. How would you express the rules and handle historical invoices?
- Business reports mix orders, order lines, and payment attempts, so metrics disagree across pages. How would you define the fact-table grain and validate aggregation semantics?
- The source database has deleted a customer, but a change data capture (CDC) pipeline and downstream summary views still show the old record. How would you trace the deletion event, update dependent views, and verify cleanup?
- Two models call a feature with the same name but receive different values because defaults and missing-data handling differ. How would you establish a feature contract and compatibility checks?
No questions in this section match your target. ·
C · Value judgment and direction setting7
- A feature is used often but has not improved retention or payment. How would you determine whether it creates core value, reflects habit, or rewards the wrong behavior?
- The team needs to test a growth hypothesis while customer-impacting maintenance work keeps arriving. How would you set capacity, triggers, and stop rules?
- The annual conversion target depends on an untested channel assumption. How would you separate current commitments, assumptions to validate, and checkpoints for continuing, changing, or stopping?
- The team needs months to build shared data capability, but the near-term roadmap shows no direct feature output. How would you express value, milestones, and exit criteria?
- Overall conversion improves, but new users and low-connectivity regions worsen. How would you examine segmentation, selection bias, and problems hidden by the aggregate?
- After several teams optimize the same north-star metric, duplicate content and low-quality interactions appear. How would you diagnose metric distortion and adjust guardrails?
- The team proposes pausing feature work to rebuild a core module, but past refactoring benefits were hard to quantify. How would you set a baseline, pilot, and stop criteria?
No questions in this section match your target. ·
D · Delivery and ongoing operations11
- 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?
- 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 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?
- A new regulatory requirement makes the original scope impossible, yet teams still cite old milestones. How would you update baselines, dependencies, and external expectations?
- Three projects independently build similar permission and notification capabilities, each seeming reasonable alone. How would you detect portfolio-level duplication and change governance?
- 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?
- 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?
No questions in this section match your target. ·
E · Collaboration, communication, and influence4
- A cross-time-zone team relies on chat history for handoffs, and recipients repeatedly misunderstand status and open decisions. How would you shape handoff information and verify understanding?
- Product considers the risk acceptable, while security wants a delay; each cites different impact scenarios. How would you clarify facts, decision rights, and executable options?
- The upstream team wants rapid API changes while downstream teams need long compatibility and have no spare capacity. How would you negotiate versions, ownership, and cost?
- Several teams use a metric with the same name to make opposing decisions, but you cannot mandate a definition. How would you build an influence path?
No questions in this section match your target. ·
F · People and organization building2
- A person’s output falls short, but goals change frequently and different people interpret acceptance differently. How would you distinguish skill, resource, and management issues?
- A high performer personally solves every hard problem, helping short-term delivery while others become reluctant to own work. How would you intervene?
No questions in this section match your target. ·
H · Professional responsibility and work style5
- A business lead asks you to publish a financial-rule fix without the required second-person review to meet a promotion window. You do not yet have enough information to confirm rollback safety. How would you assess and respond?
- You are writing the summary of a high-impact project, but its result came from several teams and a key decision was not yours. How would you represent your contribution, others’ contributions, and the responsibility you carried?
- You discover that last week’s configuration change made part of a report inaccurate. Worried about appearing unreliable, you tried to correct it alone first; the impact is still unknown. What would you do now?
- You deliver an interface on schedule, but the downstream team has not integrated it and the business workflow still cannot be used. Your contractual task boundary is complete. How would you decide what responsibility to take next and communicate it?
- Your quarterly outcome has not definitively failed, but new validation has sharply reduced the chance of meeting it on time. You worry early reporting will look like weak execution. How would you communicate and organize next steps?
No questions in this section match your target. ·