Enter the PIN separately for each Pro question or lesson. Opening one item does not unlock other items or topics.
Interview practice studio
5 free of 5 questions / lessons
1 · Debugging and code review
A checkout endpoint has intermittent duplicate charges during client retries. Inspect the snippet, identify the root issue, and state how you would fix and test it.
Scenario: A request can time out after the payment provider processes a charge. The client retries the same POST. The database order row has a unique order ID, but the payment call has no idempotency key.
public async Task<Receipt> CheckoutAsync(
CheckoutRequest request,
CancellationToken cancellationToken)
{
var order = await orders.CreateAsync(request, cancellationToken);
var charge = await payments.ChargeAsync(
order.Total, cancellationToken);
await orders.MarkPaidAsync(order.Id, charge.Id, cancellationToken);
return new Receipt(order.Id, charge.Id);
}
2 · SQL reasoning and query review
A production endpoint needs the latest 20 orders for one customer. The table contains millions of rows. Write a parameterized query and explain the index and plan evidence you would inspect.
Schema:Orders(Id, CustomerId, CreatedAt, Status, Total). Return only the columns needed by a history list; newest first. Assume SQL Server syntax for this exercise.
This is a deterministic checklist, not a SQL engine. It does not execute your query or prove the plan is fast.
3 · Interactive system-design interview
Design an order-status service for a marketplace. Talk through the stages in order; record assumptions before choosing infrastructure.
Prompt: Customers and support agents need current order status and a history of status changes. The system starts at 2,000 requests/second peak, must isolate tenants, and should remain useful during a downstream carrier outage.
4 · Production incident simulation
Triage first, mitigate safely, then verify. Choose an action at each stage and observe the scenario consequences.
5 · Senior project deep-dive builder
Build a truthful, evidence-based project story. Use “I” for your contribution and “we” for team outcomes; never invent metrics or claim work you did not do.
Follow-up questions to rehearse: What was the hardest trade-off? What did you personally change? How did you measure impact? What failed? What would your teammate say you could have done better?