ROLE
Backend
Compare expectations across career stages →
These are the same questions found in the library, grouped here by the capability each one mainly examines.
1216 questions
Extended questions 301–350 of 1216 on this page.
A · Professional problem solving and implementation8
- 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 operations9
- The business asks to “improve customer experience” without a clear pain point or deadline. How would you decompose the goal into verifiable problems, workstreams, and milestones?
- 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?
- 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?
- 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 influence5
- 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?
- The vendor contract promises average availability, while the business cares about data recovery and incident notification. How would you align internal stakeholders to drive change?
No questions in this section match your target. ·
F · People and organization building10
- 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?
- Several teams look healthy on paper, but attrition and delivery risks are never raised. How would you diagnose distorted reporting and change the management system?
- Every team meets its own targets but shifts cost and complexity onto a shared platform. How would you reset shared goals and decision rights?
- The product is organized around a customer journey while engineering teams are split by technical layer, making cross-layer work queue up. How would you assess whether boundaries should change?
- After two teams merge, overlapping roles lack clear ownership and old decision paths remain. How would you redefine responsibilities and check the result?
- The team selects many candidates from prestigious schools and companies, yet job capability does not match. How would you rewrite the role criteria and calibrate screening?
- A person completes courses and rotations but shows no independent judgment in a new responsibility. How would you redesign development evidence and practice?
- A candidate lists many project outcomes but cannot show sustained ownership at the target level. How would you distinguish results, impact scope, and responsibility evidence?
- A critical business area depends on one owner, and handoff documents do not enable anyone else to operate it independently. How would you build real succession capability?
No questions in this section match your target. ·
G · Learning, adaptation, and sustained growth4
- You completed structured learning, but your judgment and project outcomes did not change. How would you determine whether practice, feedback, or context is the issue?
- A high-risk decision produced a good outcome, but key assumptions were disproved and luck contributed. How would you reflect and change the next decision?
- A new role has no clear first-quarter goals, and the team is busy with routine work. How would you identify a problem worth owning and calibrate with your manager?
- You set a long-term capability goal, but urgent daily work keeps displacing learning and improvement. How would you create a sustainable way to make progress?
No questions in this section match your target. ·