Aug 3–10 interview digest: Uber design, Stripe AI coding, and Google process friction
Current reports from Uber, Capital One, Bloomberg, Stripe, Google and CoreWeave point to mixed-format loops, sparse question repetition, and compensation that only becomes comparable after separating base, bonus, equity and vesting.
The week in one read
The selected reports span coding, system design, AI-assisted implementation, and slow or incomplete decisions after the loop. That mix is useful for preparation, but it does not establish a change in any company's interview bar. The strict window here is Aug 3–10, 2026, ending at the Monday 09:00 publication cutoff in the channel's display timezone.
Nine report-level pages cleared the date and detail-page checks: three Glassdoor reports, five Blind posts, and one Reddit offer discussion. The selected set is recent and concrete, but it is not a verified top-voted ranking: Glassdoor did not expose report-level engagement, while Blind's pages exposed relative age and, on its ranking surfaces, mixed engagement markers. Reddit supplied the clearest ranking signal: the Google offer post had 138 score, 182 comments, and a 78.5% upvote ratio when retrieved. 123456789
Loading stats card…
Signal strength: enough to change a prep plan; nowhere near enough to declare a company-wide bar, pass rate, or hiring reopening.
Report cards: what actually appeared
| Company and role | Posted / age shown | Format and rounds visible | Outcome | Engagement and evidence limits |
|---|---|---|---|---|
| Uber — Software Engineer | Aug 6, 2026 | About 30-minute phone screen; coding tasks; design prompt on a real-time driver-rider matching service; LRU cache; weighted directed-graph shortest path | Accepted offer | Glassdoor page did not show report-level votes or likes. Level and location were not disclosed. 2 |
| Capital One — Software Engineer | Aug 5, 2026 | Self-described four-hour "power hour" interview; one visible question was a systems-design whiteboard interview | Accepted offer | No report-level engagement, level, or location shown. 1 |
| Bloomberg — Senior Software Engineer, New York | Aug 6, 2026 | One-hour coding screen with two questions; onsite coding on intervals and graph paths, then system design for an underground subway system | No offer | The interview itself was in Jul 2026; the report was posted Aug 6. No report-level engagement shown. 3 |
| Google — L4, Sunnyvale | Blind displayed 2d | Offer-evaluation post; 5 YOE; no interview-round details | Offer in hand; poster says Google called it final | Blind's ranking surface showed visible markers of 24 / 1,646; their exact labels were not exposed in the page text. 410 |
| CoreWeave — Senior Software Engineer | Blind displayed 6d | Offer-evaluation post; 8 YOE; no interview-round details | Offer disclosed | Blind page did not expose a post-level vote count. Location and vesting schedule were not disclosed. 5 |
| Stripe — Staff engineer candidate, current Amazon L6 | Blind displayed 3d | Mini-onsite system design; AI-assisted coding, 3/3 parts; virtual integration round, 2/3 parts; technical project discussion; hiring-manager and adaptability rounds | Pending; poster asks whether the integration round was enough | No post-level engagement shown. The poster gives India context and current Amazon TC, but no Stripe offer. 6 |
| Google — post-onsite feedback delay | Blind displayed 3d | Onsite completed 15 days earlier; one interviewer had not submitted feedback; team match and hiring committee had not started | Pending; candidate had another offer | No post-level engagement shown. This is a process report, not evidence of a failed loop. 7 |
| Robinhood — mobile/web hiring process | Blind displayed 3d | No round questions disclosed; post describes candidates being told they had strong positive feedback, then stalled or ghosted | No final outcome disclosed | Blind's ranking surface showed 55 / 4,112 visible engagement markers. The post is an anonymous complaint about a recruiter, not proof of company-wide behavior. 810 |
| Google — AI/ML candidate from a government lab | Aug 10, 2026 | Interviewers discussed a three-day office expectation, but the post gives no coding or design prompt; team match was still pending | Offer; corrected disclosure says $212K base, 15% target bonus, and stock | Reddit post had 138 score, 182 comments, and 78.5% upvote ratio at retrieval. The stock amount was not disclosed. 9 |
The ranking numbers need careful reading. Blind's two visible values vary by page and the site does not label them in the returned text; they are engagement markers, not comparable upvote counts. Reddit's score and comment count are explicit. Glassdoor exposes current report dates and outcomes, but not a trustworthy report-level popularity field.
Question bank: the loop is wider than DSA
No named prompt appeared in two independent current-window reports. That is a useful negative result: this week's evidence gives a set of prep targets, not a frequency-ranked question bank.
| Round | Prompt or task | Count in this week's selected reports | What to practice |
|---|---|---|---|
| Uber system design | Design a real-time driver-rider matching service at Uber scale | 1 | Matching logic, location freshness, dispatch latency, hot partitions, failure handling, and how to define the quality metric. 2 |
| Uber coding | Implement an LRU cache with O(1) get and put | 1 | State the invariant before coding, then test eviction, duplicate keys, capacity zero, and pointer updates. 2 |
| Uber coding | Find the shortest path in a weighted directed graph | 1 | Choose the algorithm from edge assumptions, explain why BFS is insufficient when weights vary, and test unreachable nodes. 2 |
| Bloomberg coding screen | Find the deepest string in parentheses; decode a secret message in a binary tree | 1 report, 2 questions in one hour | Practice parsing depth and tree traversal under a clock, then say what input assumptions you need. 3 |
| Bloomberg onsite coding | Merge intervals; graph problems about planes and airports and all start/end paths | 1 | Separate interval normalization from graph modeling. Ask whether the graph is directed, weighted, or required to enumerate paths before choosing the method. 3 |
| Bloomberg system design | Design an underground subway system | 1 | Model stations, routes, transfers, real-time service changes, and the read/write pattern before discussing storage. 3 |
| Capital One system design | Systems-design whiteboard interview | 1 | Practice drawing a complete request path on a whiteboard and naming the first bottleneck, rather than jumping to component names. 1 |
| Stripe integration / AI-assisted coding | Solve 3/3 parts in an AI-assisted coding round; 2/3 parts in integration | 1 | Confirm the tool policy before the round. Practice reading an unfamiliar codebase, scoping the smallest correct change, and recovering cleanly after a misread requirement. 6 |
The practical shift: one interview loop can now test algorithmic correctness, production judgment, system boundaries, tool use, and communication under a changing prompt. Preparing only by LeetCode difficulty leaves several of those surfaces untouched.
The Google posts add a process question rather than another coding prompt. One candidate received an offer while still waiting for team matching; another had finished an onsite but was blocked by one missing interviewer feedback form before team matching and hiring committee review. 47
Outcomes and pass-rate read
Five of the nine selected pages show an offer or accepted outcome: Uber, Capital One, the Google L4 offer, CoreWeave, and the Reddit Google offer. Bloomberg shows no offer. Stripe and the Google feedback post are pending, while the Robinhood post describes process friction without a final outcome. This is a selected report mix, not a company pass rate; the denominator is neither random nor complete, and three pages have no final outcome.
The aggregate Glassdoor figures provide context but still do not become pass rates. The current company pages report that 56% of Capital One Software Engineer interview experiences were positive, 48% of Uber's were positive, and 46% of Bloomberg Senior Software Engineer experiences were positive. Those are user ratings of interview experience, based on historical submissions, not the share of candidates who passed. 123
Do not turn this week's 5-to-1 visible offer/no-offer split into an 83% pass rate. The posts were selected because they were discoverable and specific, and the underlying interview dates, levels, and response behavior differ.
The defensible read is narrower:
- Uber and Capital One each add a current accepted report with a concrete loop shape.
- Bloomberg adds a detailed senior loop ending in no offer, with both coding and system design.
- Google has mixed signals: two offers, a team-match / feedback bottleneck, and a separate process with an unresolved level question.
- Stripe has the clearest current AI-assisted coding and integration signal, but no outcome yet.
- Robinhood supplies a recruiter-responsiveness warning, not proof of a changed technical bar.
Compensation: two real disclosures, one partial, then the benchmarks
The complete current-window offer breakdowns are sparse. The first-person disclosures below are separate from aggregate Levels.fyi benchmarks.
| Company and role | Base | Bonus | Equity | Total comp | Other disclosed details |
|---|---|---|---|---|---|
| CoreWeave — Senior Software Engineer | $235K | $35K | $160K | $430K | 8 YOE; location, sign-on, and vesting not disclosed. 5 |
| Google — L4, Sunnyvale | $200K | 15% target ($30K from the stated base) | $300K over 4 years ($75K annualized) | About $305K implied annualized package | 5 YOE; the poster says the offer was final. No sign-on listed. The annualized figure is arithmetic from the post's components, not a stated TC. 4 |
| Google — AI/ML offer, level not disclosed | $212K | 15% target ($31.8K from the stated base) | Amount not disclosed | Not calculable | Reddit poster corrected an initial typo: $212K is base, not first-year total; relocation to SF or NYC was under consideration. 9 |
Compare components, not headlines. A $430K CoreWeave package, a Google L4 package with annualized equity, and a Google offer with undisclosed stock are three different negotiation objects. Ask for level, refresh assumptions, vesting, sign-on, and the date each figure becomes cash.
The Reddit Google discussion also surfaces the cost side that a compensation table cannot settle. The poster compared a roughly $100K government-lab job in Washington, DC with the Google offer, a possible move to San Francisco or New York, and a change from five office days to the three-day expectation described by interviewers. The comments split between career-option value and the risk that a high-cost move can erase much of the base-salary increase. 9
Aggregate TC anchors updated this week
Levels.fyi pages are useful for level calibration, but they aggregate reported compensation. The current pages do not turn into signed offers and do not supply a component breakdown for every row below.
| Company | Representative software-engineer levels | Current total-compensation anchor | What the page says about equity |
|---|---|---|---|
| L4 / L5 / L6 | $299K / $408K / $618K | Component breakdown not shown in the current page extract; page last updated Aug 10. 11 | |
| Meta | E4 / E5 / E6 | $297K / $444K / $701K | Four-year RSU schedule shown as 25% per year; page last updated Aug 10. 12 |
| Amazon | L5 / L6 / L7 | $274K / $431K / $700K | Page shows a backloaded 5% / 15% / 40% / 40% four-year schedule; last updated Aug 9. 13 |
| Databricks | L5 / L6 | $669K / $1.24M | Page shows both 40% / 30% / 20% / 10% and 25% / 25% / 25% / 25% schedules; last updated Aug 10. 14 |
| Stripe | L3 / L4 | $444K / $683K | Page shows one-, two-, and four-year RSU options and says refresh is available after nine months; last updated Aug 10. 15 |
| Microsoft | 64 / 65 / 66 | $283K / $351K / $409K | Component breakdown was not shown in the current page extract; page last updated Aug 10. 16 |
Company read-through: what candidates should and should not infer
| Company / group | Current-window signal | Safe interpretation |
|---|---|---|
| Two offer disclosures, one unresolved team-match / feedback case, and one L4 level question | Active candidate signal with process friction. It does not establish a broad reopening or a uniform level bar. 479 | |
| Stripe | One staff-level candidate reports system design, AI-assisted coding, integration, project, HM, and adaptability rounds; outcome pending | The loop may test practical integration and tool use, but one pending post is not a company standard. 6 |
| Uber | One accepted SWE report with phone screen, coding, and design | Concrete prep signal; no hiring-volume inference. 2 |
| Capital One | One accepted SWE report with a long power-hour format and systems-design whiteboard | Concrete format signal; no pass-rate inference. 1 |
| Bloomberg | One senior no-offer report with a two-question coding screen and subway system design | Useful senior prep target; no claim about a changed bar. 3 |
| Robinhood | Anonymous report of delayed or missing recruiter responses after positive feedback | Candidate-risk signal worth asking about; not a verified company-wide pattern. 8 |
| Amazon, Meta, Apple, Microsoft, Netflix, Databricks | No additional current-window report card met the strict detail-page threshold in this pass | Absence from this digest is a coverage result, not evidence of no interviews or no hiring. Current compensation anchors for several of these companies are listed above. 131416 |
What to do before the next interview
- Run one mixed-format practice block. Do a timed medium, then spend 15 minutes reviewing a deliberately buggy solution, then sketch one system-design request path. The Uber and Bloomberg reports put those modes close together. 23
- Practice a system-design whiteboard without slides. Start with users, request volume, consistency, and the failure you are optimizing for. Capital One's report names the whiteboard format; Bloomberg's names a subway-system design. 13
- Clarify AI-tool rules before the round. The Stripe post describes an AI-assisted coding round, but it does not establish the policy for every Stripe team. Ask what tools are allowed, what must be written unaided, and how the final code is evaluated. 6
- Put process deadlines in writing. Ask who owns feedback, when team matching begins, when the hiring committee meets, and how long an offer can remain open. The Google and Robinhood posts show why a technically successful loop can still become expensive to manage. 78
- Negotiate from a component sheet. Write base, target bonus, grant value, vesting schedule, refresh timing, sign-on, level, location, and start-date conditions on separate lines. Use the Levels.fyi rows as calibration, then compare them with the first-person offer disclosures rather than calling every headline TC equivalent. 1112131415
The week's usable conclusion is modest but specific: prepare for a loop that can move from a medium algorithm to an LRU cache, graph reasoning, a whiteboard design, AI-assisted implementation, and a process handoff that may not happen on schedule. The current data supports those drills and a component-level compensation conversation. It does not support a broad pass rate or hiring-status call.
Coverage note: Glassdoor supplied three current report pages with dates and outcomes but no report-level engagement. Blind supplied current first-person offer, interview-process, and interview-experience posts, but several native pages exposed only relative age such as 2d, 3d, or 6d and no absolute timestamp. The current r/cscareerquestions interview-discussion thread had zero comments when retrieved, so it was not used as an interview-question source. A high-engagement Blind Google coding post displayed 7d at the boundary and was excluded from the nine-page count because its exact publication time was not exposed. Levels.fyi supplied current aggregate compensation anchors, not first-person weekly offer letters.
References
- 1Capital One Software Engineer interview report
glassdoor.com
- 2Uber Software Engineer interview report
glassdoor.com
- 3Bloomberg Senior Software Engineer interview report
glassdoor.com
- 4Google L4 offer in Sunnyvale
teamblind.com
- 5CoreWeave offer for Senior Software Engineer
teamblind.com
- 6Stripe offer chances — Staff engineer role
teamblind.com
- 7Google interviewer not submitting feedback
teamblind.com
- 8Don't interview at Robinhood
teamblind.com
- 9
- 10Blind trending and August ranking pages
teamblind.com
- 11Google salaries, Levels.fyi
levels.fyi
- 12Meta salaries, Levels.fyi
levels.fyi
- 13Amazon salaries, Levels.fyi
levels.fyi
- 14Databricks salaries, Levels.fyi
levels.fyi
- 15Stripe salaries, Levels.fyi
levels.fyi
- 16Microsoft salaries, Levels.fyi
levels.fyi
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.