Jul 27–Aug 3 interview digest: Amazon's three-card split, Scale AI's LLM loop, and fresh comp anchors

The week in one read

Signal strength: high enough to change this week's prep plan; too thin to call a hiring bar, pass rate or reopening trend.

Report cards

Question bank: practice the work, not just the label

Amazon: coding is still the gate, but the wrapper varies

1. Solve a medium problem under hidden-test pressure, then state the invariant and complexity before coding.
2. Take a working solution and attack it as a bug-catching exercise: malformed input, duplicate state, boundary geometry and a plausible but asymptotically weak approach.
3. Prepare a 90-second project explanation. Another Jul 28 Amazon report names “Explain a project of yours in depth” and says the interviewer asked about experience, projects, technical work and refined knowledge. 2

Scale AI: the strongest new signal is practical implementation

Spotify: process handling is part of the candidate experience

The repeated pattern across the five reports is format stacking: coding can sit beside bug finding, behavioral judgment, system design and recruiter coordination. A prep list organized only by “easy, medium, hard” misses most of that surface area.

Pass-rate read: no defensible company estimate

• Amazon has the only multi-report cluster in the window, and its visible formats range from a three-question test to OAs plus a three-engineer panel.
• Scale AI contributes the only fully described LLM evaluation design prompt and the only report centered on debugging plus backend practical work.
• Spotify contributes a process-friction signal, not evidence of a changed interview bar.
• No current report supports saying that Google, Meta, Apple, Microsoft, Netflix, Stripe or another top SaaS company broadly reopened, froze, or raised its bar this week. Direct Google, Meta and Stripe Glassdoor fetches returned access-challenge pages with no visible report entries, so absence here is not evidence of absence on the platforms. 678

Compensation benchmark: fresh anchors, no signed-offer proof

Compensation is a range-setting tool here, not an offer letter. Ask for base, sign-on, target bonus, equity value, vesting, refresh assumptions and level in separate lines before comparing packages.

What to do before the next loop

1. Run a two-mode Amazon session. Spend 25 minutes on a medium problem with hidden-test thinking, then 15 minutes finding defects in an already-working solution. Finish with a project explanation that names your decision, constraints, failure and measurable result.
2. Build one small async evaluator. A file-in, JSON-out API, a queue-backed worker, an LLM call, retries, rate limiting and a dead-letter path will exercise the same seams exposed by the Scale AI report. Explain how you would test output quality instead of treating a model response as ground truth.
3. Make process cost explicit. Ask Spotify-like loops for round count, feedback ownership and a decision date. If the answer is vague, do not silently assume the process will be short.
4. Negotiate with component-level anchors. Use the Levels.fyi table to set a range, then match level and vesting before comparing Google, Meta, Amazon, Databricks, Stripe, Spotify or Salesforce.