ROLE
Frontend
Compare this role’s stage expectations →
These are the same questions found in the library, grouped here by the capability each one mainly examines.
1121 questions
Questions 101–150 of 1121 on this page.
A · Professional problem solving and implementation24
- How should coupons, discounts, and flash sales integrate with a trading system without slowing the core transaction flow? How would you calculate, combine, and reconcile discounts?
- The product wants confident AI conclusions, but evidence supports only probabilistic judgments. How would you design communication and traceability?
- After AI output causes actual user harm, product, model, operations, and review teams all take part in the response. How would you divide incident handling and follow-up improvement?
- After replacing a foundation model, overall metrics remain similar but some users report worse results. How would you identify what changed in model behavior and decide whether to roll back?
- Average AI quality meets the target, but a few high-risk errors can cause harm. How would you set the release gate?
- An AI assistant can call internal tools, but tasks require different permissions. How would you design authorization and audit?
- When the model cannot establish an answer, should the product refuse, return a low-confidence result, or escalate to a person? What distinguishes the choices?
- Overall AI accuracy passes, but one language or user segment has a higher error rate. How would you assess and respond?
- A build registry must clean up years of images, but production services may still roll back to old versions. How would you define retention and artifact recoverability?
- A payment-creation API must support safe client retries. How would you define the idempotency-key scope, retention period, and conflict behavior to avoid duplicate charges without suppressing valid requests?
- In an admin console, inserts and deletes while paging by creation time cause duplicate or missing rows. How would you compare offset and cursor pagination and define the consistency expectation?
- An organization must move several repositories from an old CI system to a new platform without pausing delivery across teams. How would you sequence migration and decide which repositories enter each wave?
- A user opens a protected order-detail page from an external link. How would you design route parsing, login return, and authorization so the deep link cannot bypass in-app controls?
- A list screen scrolls poorly even though network metrics are normal and memory is stable. How would you determine whether main-thread computation, layout/drawing, or lock waits are responsible?
- Implement a map with concurrent reads and writes, per-entry expiration, and expired-entry cleanup. How would you define expiration semantics, synchronization boundaries, and deterministic tests?
- Implement deep equality for inputs that may contain nested arrays, shared references, and cycles. Define equality semantics first, then avoid infinite recursion and accidental confusion of reference structures.
- Implement a small task queue with concurrent workers, cancellation, and retries; tests must not depend on real sleeps. How would you design the scheduling interface and state transitions?
- Implement an incremental UTF-8 log parser that receives chunks which may split multibyte characters, reorder fields, contain multiple records, or include an exceptionally long line. Define parser state, error recovery, and memory limits, then implement repeatable core logic.
- Hundreds of repositories pin different third-party versions, and security teams struggle to identify exposure when a severe vulnerability appears. How would you establish dependency updates and risk handling?
- A service has moved to a new address, but some users still reach old nodes and recovery varies by network. How would you check DNS caches, client caches, and existing connections?
- A defect appears only in production and cannot be reproduced in development or staging. How would you determine whether the cause is environment, traffic shape, or data characteristics, and improve environment design?
- Several services read feature flags and audience rules on request paths. How would you design the control plane and local evaluation so behavior remains predictable when the control service fails?
- A critical end-to-end test fails intermittently: it passes alone but fails in a parallel suite, and the team has started rerunning it until it passes. How would you determine whether it exposes product risk, isolate shared state, resource contention, clock or ordering dependencies, and improve the test workflow?
- A third-party SDK callback updates data, but the UI does not refresh; forcing a refresh causes duplicate updates. How would you identify the framework’s change-detection boundary and choose the right integration point?
No questions in this section match your target. ·
B · Business understanding and domain modeling25
- Renewal fell by six percentage points this quarter, while the share of small customers among new accounts rose. How would you segment customers, usage periods, and service cost to determine whether product value fell or the customer mix changed?
- Besides your product, what else could users do to get the same job done? What does each alternative compete for, and when is it actually the better choice?
- A premium service tier earns more revenue but consumes more human support, and renewal has not improved. How would you determine whether it creates incremental value?
- A product is sold once but requires long-term support and upgrades. Revenue is growing while the service queue accumulates. How would you decide whether these sales still create value?
- Pick a module you own. Explain who it serves, what input it takes, what output it provides, and follow the user task through to the business result.
- When you explain a business, how do you first lay out the whole and then the position and value of the part you own within it? How does someone without a whole-picture view tell it, and what is the difference?
- A customer cancels before service begins, but the contract, product page, and support system describe the cancellation fee differently. How would you determine the refund and make future orders follow a consistent rule?
- An order may use a membership discount, channel offer, and coupon, with exceptions by product, contract, or region. How would you define eligibility and calculation order so customers see a consistent amount and finance can reconcile refunds?
- Product, finance, and growth teams each report “active users,” but the numbers differ. What would you ask before deciding whether to standardize the definition?
- A user consented to product analytics, then withdrew consent. Derived metrics already reached reports, experiments, and model-training data. How would you model consent state, purpose scope, and propagation?
- A producer plans to rename a field and change an enum’s meaning, while a dozen teams depend on the current schema. How would you manage the change?
- A user asks to have personal data deleted, while finance must retain transaction records for audit. How would you define the boundary among deletion, anonymization, and traceability?
- In a behavioral event table, what exactly does one row represent? Explain how you settle its grain, and which statistics go wrong when the grain is unclear.
- How does your own business model interact with the industry's or a partner's common model? When fields, definitions, or concepts do not line up, how do you handle it?
- Mobile events may arrive days late, while reports must reflect event time. How would you model and process late, corrected, and duplicate events?
- A company buys 100 seats used across subsidiaries. Headquarters signs the contract, but some subsidiaries want separate invoices and permission administrators. How would you distinguish customer, contract, organization, account, member, and seat so access and billing stay consistent?
- An account may hold a base plan, temporary trial, campaign benefit, and support credit. Systems implement precedence differently, so access sometimes flips. How would you define eligibility and conflict rules?
- An order has a single status field that means both fulfillment progress and payment result, and several teams read it. How would you split it into two concepts and move old data and old consumers over smoothly?
- A service changes eligibility from “current account status” to “account status at application time plus a risk-review result.” Support needs to explain historical denials, and audit must reproduce the original decision. How would you evolve rules and data models without conflating old and new outcomes?
- Duplicate registration created two customer entities later confirmed to be the same company. Reports should unify them, while contracts, approvals, permissions, and personal actions must retain original responsibility. How would you model the merge?
- A support ticket can be reopened when a customer provides new evidence and may be split into follow-up work. How would you model states and events so closure, reopening, and splitting remain traceable?
- A producer adds an order status, and an old consumer rejects the whole message because enum validation is strict. Teams disagree over who must update, and consumers have different owners. How would you design compatibility and rollout order?
- Map the area you have owned over time: what users are trying to do, where the main process obstacles are, what your module can influence, and what is outside its control.
- Write a one-page product overview for someone who just joined. How would you mark which statements are fact, which are inference, and which are simply unanswered questions?
- Where does your project sit in the wider business? Who gives it input, who uses its results, and who is affected if it is late or wrong?
No questions in this section match your target. ·
C · Value judgment and direction setting1
No questions in this section match your target. ·