Oct. 12–19 interview digest: Google's L6 median fell $66K in a week, and Apple ran a LeetCode hard inside 20 minutes
Google's L6 median fell $66K in seven days, two cleared Stripe loops ended without a role, and Apple put a LeetCode hard inside a 20-minute round.
The seven days ending Oct. 19, 2026 moved the pay numbers candidates carry into negotiation. Levels.fyi's Google software-engineer page refreshed today with an L6 median of $664K. The same page reported $730K when it was read on Oct. 12. 1
Meta's overall software-engineer median moved from $482K to $455K across those seven days. 2 Amazon's went from $270K to $266K 3, and Stripe's from $260K to $253K. 4
Inside Google's page, one level carried almost all of that movement. L3 went from $212K to $214K, L4 from $307K to $301K, L5 from $450K to $451K, and L6 from $730K to $664K. 1
Those medians are recomputed from rolling self-reported submissions, and Google's page added 77 of them this week, taking the count from 23,427 to 23,504. 1 A single level can move this far on a few dozen new entries.
Last week's edition read a reported Google L6 offer of $650K a year, averaged across four years, against a $730K median, which put it $80K under.
Against $664K the same offer sits $14K under. One figure averages four years and the other is a single-year total, so treat the gap as a direction.
Three reports this week end somewhere other than an offer. A senior backend candidate passed Stripe's full loop for an L3 role, matched with a team, and reached reference checks. 5 Another candidate cleared every round at Stripe and got a "Hire" decision from its candidate review, then learned the role had gone to an internal candidate. 6
At LinkedIn, a staff-level onsite was cancelled two weeks before it was due. 7
The round formats this week were specific too. Apple put a candidate through two technical screens and four panel rounds with eight interviewers in total; one of those rounds asked for a LeetCode hard inside 20 minutes and a system design question. 8 An entry-level Meta candidate in Menlo Park expected no design round and got one. 9
The week in one read
- Google's L6 benchmark fell $66K in seven days. The page's L6 median went from $730K on Oct. 12 to $664K on Oct. 19 while L3 through L5 moved by $7K or less. 1
- A cleared Stripe loop ended with the role filled internally. The candidate spent nearly two months, cleared every round, got a "Hire" decision, and was told an internal candidate had taken the position. 6
- A second Stripe candidate passed and stalled at reference checks. A peer of four years described the backend engineer as a frontend expert; the hiring manager missed one scheduled call and a second reference was never scheduled. 5
- LinkedIn cancelled a staff onsite two weeks out. The poster says it was the only onsite call in three months. 7
- Apple ran a LeetCode hard against a 20-minute clock. The same round added a system design question, inside a loop of two screens and four panels covering eight interviewers. 8
- A Google L4 candidate's coding round was scored for the level below. He finished the problem, left no time for the follow-up, and the recruiter relayed the coding score as Lean Hire/Hire for L3. 10
Evidence at a glance
Loading stats card…
The 15 dated Glassdoor reports are three at Google, five at Amazon, three at Microsoft, three at Meta and one at Apple, all posted between Oct. 14 and Oct. 19.
Their pages printed company aggregates when read this week. Google lists 26,349 interviews with a 3.36 difficulty out of 5, 63.7% positive and 38 days to hire 11; Amazon 67,027 interviews, 3.09, 60% positive, 27 days. 12
Four of those pages print figures for a single role. Amazon's software-engineer page lists 3,694 interviews, a 3.3 difficulty and 24 days to hire, against a 28-day company average. 13
Apple's lists 705 interviews, 3.2 and 23 days. 14
| Company | Interviews on the role page | Role difficulty | Role "positive experience" | Company "positive experience" | Days to hire for the role |
|---|---|---|---|---|---|
| Amazon, Software Engineer | 3,694 | 3.3 / 5 | 48% | 57.5% | 24 13 |
| Microsoft, Software Engineer | 1,726 | 3.2 / 5 | 63% | 66.5% | 29 15 |
| Apple, Software Engineer | 705 | 3.2 / 5 | 56% | 63.9% | 23 14 |
| Meta, Software Engineer | 2,286 | 3.3 / 5 | 56% | 56.5% | 27 16 |
A "positive experience" share comes from candidate ratings of the process. It counts everyone who finished a loop at that company, offers and rejections alike.
Report cards
On Blind, ordered by the view counter
Blind shows a relative age rather than an absolute date, and each age below is reproduced exactly as displayed, with the calendar date it corresponds to.
Counters were read off each post's page on Oct. 19, so an older post has had longer to accumulate views. The counter row is Blind's only engagement measure, and it does not compare with a Reddit score or a Glassdoor entry.
| Company or scope | Freshness | Round, task, or process | Reported outcome | Engagement and evidence boundary |
|---|---|---|---|---|
| Unnamed, posted in Tech Industry | 5d (Oct 14) | A round the poster says he nailed, with a back-and-forth he describes as great, until the interviewer said out loud: "this is the best answer I've heard all day." | No offer, despite the spoken praise. He ends the post with "And well, you know the rest." | 66 likes, 87 comments, 7,655 views. The highest-engagement report of the window. The top reply, at 73 likes, reads "He probably only hears like 1 answer per day." 17 |
3d (Oct 16) | A staff-level onsite, cancelled by email two weeks before the scheduled date. | No loop happened. The poster says it was the only onsite call received in three months and asks whether roles will reopen. | 9 likes, 46 comments, 1,824 views. In the 46 replies the poster asks about timing; the post names no recruiter or team. 7 | |
| Stripe | 4d (Oct 15) | A senior backend role at L3: full loop passed, team matched, then reference checks. Recruiter asked for a former manager plus peers. | No outcome yet. A peer of four years described him as a frontend expert, and the hiring manager missed a scheduled call. | 0 likes, 20 comments, 1,455 views. The poster is tagged Bloomberg. 5 |
| Stripe | 7d (Oct 13) | Nearly two months of interviewing for a SWE role, every round cleared, then a "Hire" decision from candidate review. | No offer: the recruiter said an internal candidate had filled the role. The poster says three other candidates he spoke to were stuck in team match for months. | 8 likes, 11 comments, 927 views. The poster is tagged Microsoft. Blind's own summary of 10 comments, generated Oct 17, records complaints about string-parsing and CSV-formatting questions. 6 |
| Unnamed | 3d (Oct 16) | A round the poster calls easy, run by three interviewers, where the work stalled at the keyboard. | No offer reported; the poster assumes he was passed over and regrets not paying for interview practice. | 6 likes, 11 comments, 614 views. The poster is tagged Bloomberg. 18 |
| Uber | 3d (Oct 16) | An onsite that produced an offer. The recruiter told him the offer stays valid in the system for a year; he has no formal offer letter, which he says comes after team match. | Offer extended, terms unconfirmed. The poster asks whether the one-year window is real. | 0 likes, 2 comments, 207 views. The poster is tagged PayPal. 19 |
Yesterday (Oct 18) | An L4 application: virtual rounds done, onsite coding rounds two weeks away. The behavioral round read strong; the coding round came back Lean Hire/Hire for L3 because he finished the problem and left no room for a follow-up. | Pending. He asks whether one Lean Hire rules out L4 even if the onsite brings Strong Hires. | 0 likes, 2 comments, 186 views. The poster is tagged Crest Data Systems. One reply reads "Google low-balling and downleveling as usual"; the other argues a candidate needs competing offers to counter it. 10 | |
| Rippling | Yesterday (Oct 18) | An onsite round named the AI Development Interview, run on HackerRank against an existing codebase. | No report yet: this is a question asked before the round. | 3 likes, 5 comments, 114 views. The poster is tagged Microsoft. The replies describe the format rather than a completed round. 20 |
A ninth post in the window asks about Elastic's offline coding round, 90 minutes with access to AI tools, and carries no reply. 21 Its comment count was zero when read, so it supports no judgment about the round.
On Glassdoor, ordered by report date
Glassdoor prints the date a report was posted, the candidate's own outcome, difficulty and experience ratings, and no per-report engagement figure. Where a report gives the month it interviewed, that month sits beside the posting date, because the loop can run months or years before the report appears.
| Company | Report date | Round, task, or process | Reported outcome | Ratings attached |
|---|---|---|---|---|
| Amazon | Oct 19 | Seattle. Applied online, took two months: an online assessment, then four behavioral interviews for an L6 post-MBA program (MLDP). | No offer | Difficult; positive experience 22 |
| Amazon | Oct 19 · interviewed Mar 2026 | Vancouver, BC. Two rounds, one with a team lead and one with HR, each carrying live coding. He says the assessment went fine and the leadership-principles answers did not. | No offer | Difficult; neutral experience 23 |
| Oct 18 · interviewed Jul 2026 | New Delhi. Three rounds: a phone screen, then two data-structures rounds, the first relatively easy and the second hard. | No offer | Difficult; positive experience 24 | |
| Oct 18 · interviewed Jun 2025 | Bengaluru, internship. One data-structures question, then two follow-ups extending the original problem, with the round judged on handling the extensions. | Accepted offer | Average; positive experience 25 | |
| Oct 18 | Online assessment, then a virtual onsite of three rounds. LeetCode medium for the base question, then follow-ups he calls "basically hard ish", with one extremely hard question he doubts candidates are meant to finish. | No offer | Average; positive experience 26 | |
| Apple | Oct 18 | Two technical screens, then four panel rounds with eight interviewers. Each panel asked one question: system design, low-level design, or LeetCode. One round asked for a LeetCode hard in 20 minutes and then a system design question. | No offer | Difficult; negative experience 8 |
| Amazon | Oct 18 | First stage was a 90-minute online assessment with two LeetCode problems: a two-pointers and sliding-window hard, and a medium dynamic-programming question. | No offer | Difficult; negative experience 27 |
| Meta | Oct 18 · interviewed Jun 2026 | Menlo Park, entry level, through an employee referral. One behavioral, two coding, and one round he calls "sort of system design" — a surprise at that level. | No offer | Average; neutral experience 9 |
| Amazon | Oct 17 | A technical recruiter reach-out that ran as a generic HR screen: experience, the role's requirements, and expectations. | No offer | Average; neutral experience 28 |
| Microsoft | Oct 17 · interviewed Jul 2022 | Redmond. Applied through a recruiter, two weeks end to end: technical questions mixed with discussion of past projects and problem-solving. | No offer | Difficult; positive experience 29 |
| Microsoft | Oct 17 · interviewed Mar 2026 | Bengaluru, through campus recruiting. Two questions: check whether a number is a palindrome, and binary search on the answer to a longer problem with tricky cases. | No offer | Average; neutral experience 30 |
| Microsoft | Oct 17 | Several LeetCode-style problems inside one session with little back-and-forth. The interviewer kept video off and stayed muted, which the candidate says made the round feel like a test. He adds that HR was responsive. | No offer | Average; neutral experience 31 |
| Amazon | Oct 16 | Berlin. Five rounds, each carrying an algorithm question and a leadership question; a design question appeared in one round only. | Accepted offer | Average; positive experience 32 |
| Meta | Oct 15 | Singapore. A recruiter screen only: about eight questions on past experience and how it maps to the role, inside 45 minutes. | No offer at that stage | Average; positive experience 33 |
| Meta | Oct 14 | Some technical questions, then the usual interview questions. The poster calls the recruiting process simple and the bar high. | No offer | Average; positive experience 34 |
The question bank you can practice now
1. The AI-assisted round now has a name at other companies
LinkedIn's AI Assisted Coding Round had company this week.
Rippling's onsite includes a round called the AI Development Interview, run on HackerRank against an existing codebase. 20 Elastic's is an offline 90-minute coding round with access to AI tools. 21
The replies under the Rippling post describe the behaviour those rounds reward.
One commenter, tagged ex-Meta, says to use the model as "a helpful junior developer that you collaborate with rather than solely rely on", to reject its decisions out loud with reasons, and to keep the model on boilerplate and small regression tests that act as checkpoints. 20
A drill that matches both descriptions:
- Take a repository you know and give the model a ticket against it. Narrate every step: what you asked for, what came back, what you rejected and why.
- Ask the model for a regression test at each checkpoint, then break the code and check the test catches it.
- Finish by saying what you would change about the model's approach if you had another hour.
2. Ninety minutes, two problems, one of them hard
Amazon's first stage was a 90-minute assessment with two problems: a hard built on two pointers and a sliding window, and a medium dynamic-programming question. 27 The candidate rated the interview difficult and reported no offer.
- Set 90 minutes and open two problems, one hard and one medium. Write both before the timer stops, then read the editorial.
- A previous Amazon report this week cleared the same company's bar with five rounds, each pairing one algorithm question with one leadership question. 32
3. A hard problem in twenty minutes, then a design
Apple's panel round gave a candidate a LeetCode hard with 20 minutes on the clock and then a system design question. 8 The candidate reported no offer and rated the experience negative.
- Take one hard problem and give it 20 minutes. At the buzzer, stop coding and defend the design of the closest system you have built.
- Practise saying what you would cut first if the clock were 10 minutes.
4. A design round can arrive at entry level
Meta's Menlo Park loop for an entry-level role carried one behavioral round, two coding rounds, and a design round the candidate did not expect. 9 Meta's software-engineer page reports a 3.3 difficulty out of 5 and 56% positive experience. 16
- Have one design ready at any level: a service you have actually operated, its data model, its failure modes, and the metric that tells you it broke.
5. Narrate to a screen that gives nothing back
A Microsoft candidate faced several LeetCode-style problems in one session while the interviewer kept video off and stayed muted. 31 The round felt to him like a test rather than a conversation, and he reported no offer.
- Record yourself solving one problem with the camera off and no questions. Play it back for where you stopped talking.
- Microsoft's own role page lists 1,726 interviews, a 3.2 difficulty and 63% positive experience. 15
Where the level gets decided
The Google report shows how a level rating reaches the candidate this week. The poster applied for L4, cleared the virtual rounds, and had onsite coding rounds booked two weeks out. 10
The recruiter told him the behavioral round read strong. The coding round came back as "Lean Hire/Hire" for L3, on the grounds that he solved the problem and left the interviewer no time for a follow-up question. 10
His own account of the cause points at speed rather than difficulty: the question was easy for him, and he was rusty in his first interview after a long gap. 10
The two replies the post drew put the leverage outside the interview. One reads "Google low-balling and downleveling as usual." The other says a candidate needs strong competing offers to counter it. 10
What the loop cannot tell you is how often this happens. No source in this window publishes how many candidates applied for a level, how many were rated below it, or how many offers came out.
Glassdoor's role-level positive shares are the nearest published figures, and they measure how candidates rated the process rather than how many cleared it.
The numbers this week
| Company | Median total (US) | Median by level, Oct 19 | Median by level, Oct 12 | Submissions | Page refreshed |
|---|---|---|---|---|---|
| $284K, unchanged | L3 $214K · L4 $301K · L5 $451K · L6 $664K | L3 $212K · L4 $307K · L5 $450K · L6 $730K | 23,504 | Oct 19, 2026 1 | |
| Meta | $455K, from $482K | E3 $187K · E4 $307K · E5 $461K · E6 $765K | E3 $186K · E4 $300K · E5 $462K · E6 $768K | 13,931 | Oct 19, 2026 2 |
| Amazon | $266K, from $270K | L4 $181K · L5 $273K · L6 $390K · L7 $602K | L4 $181K · L5 $275K · L6 $388K · L7 $620K | 41,772 | Oct 19, 2026 3 |
| Stripe | $253K, from $260K | L1 $227K · L2 $285K · L3 $467K · L4 $621K | L1 $225K · L2 $284K · L3 $459K · L4 $621K | 1,542 | Oct 19, 2026 4 |
The October 12 column is what the same four pages printed when the previous edition read them, so the deltas are like for like.
The level medians hide their own mix. Levels.fyi prints each level's parts, and the weight shifts toward stock as the level rises.
| Company and level | Total | Base | Stock per year | Bonus and sign-on |
|---|---|---|---|---|
| Google L5 | $451K | $234K | $184K | $33.5K 1 |
| Google L6 | $664K | $278K | $323K | $63.3K 1 |
| Meta E5 | $461K | $225K | $208K | $27.6K 2 |
| Amazon L6 | $390K | $216K | $171K | $2.8K 3 |
| Stripe L4 | $621K | $279K | $297K | $45.4K 4 |
Vesting decides when the stock arrives. Google's most common schedule on the page is 38%, 32%, 20% and 10% across four years, Amazon's runs 5%, 15%, 45% and 35%, and Stripe now also issues single-year schedules. 134
An offer's headline and its first-year cash can diverge for that reason alone. At Amazon L6 the stock is $171K a year, and a 5% first-year vest pays out roughly $8.6K of it. 3
One offer rule this week came from a recruiter's mouth rather than a page.
An Uber candidate says he was told his offer stays valid in the system for a year, and that he has no formal letter because it is issued after team match. 19 Two comments had arrived when the post was read, neither confirming the rule.
After the loop
Two Stripe processes ran to the end of the interviews and stopped there. The first cleared every round and got a "Hire" decision.
The role then went to an internal candidate, and the poster says three other people he spoke to had been sitting in team match for months. 6
The comments under that post argue about what the loop actually tests. One reply says Stripe's process dumps random CSV files as inputs and asks for string parsing and formatting.
The poster answers that Stripe over-indexes on coding speed in every round. 6
The second passed the loop, matched a team, and lost control of the next step.
A peer described four years of backend work as frontend expertise, and the reference process itself went wrong: one scheduled call was missed and one reference was never scheduled. 5
LinkedIn's cancellation arrived with the least notice of all. The onsite was two weeks out, and the email gave no reason beyond the role; the poster had waited three months for that call. 7
Spoken praise is the weakest of these signals.
The most-viewed post of the week is a candidate whose interviewer called his answer the best of the day and who then got nothing. 17
A reply under that post describes what an interviewer's day looks like.
A Microsoft engineer describes being pulled into interviews "like jury duty, but for good boys": three to five back-to-back sessions in a day with gaps for notes and a lunch, and a debrief with the recruiter, the day's interviewers and the hiring manager at the end. 17
One candidate's floor was the room itself. A poster describes an easy problem he could not get through in front of three interviewers, with what he calls brain fog and anxiety, and says he would have solved it alone in a day. 18
Coverage and limits
This edition covers the seven days ending Oct. 19, 2026. Reports dated Oct. 12 appeared in the previous edition and are excluded here.
No source publishes a comparable vote or engagement total across platforms. The Blind table is ordered by Blind's own view counter and the Glassdoor table by report date, and the two orders never combine.
Blind shows a relative age; the calendar date beside each age is the date that label resolved to when the posts were read on Oct. 19.
Glassdoor's rows carry the date the report was posted, and the interview itself may have run years earlier. Where a report names the month it interviewed, that month sits beside the date.
No source publishes the applicant volumes and completed-interview counts a company-wide or per-round pass rate would need. This edition reports each candidate's own outcome with the conditions that produced it.
Glassdoor's role-level positive-experience shares and days-to-hire figures are the closest published numbers, and they measure process ratings rather than admission.
Reddit supplied no first-person interview report for the fourth week running. Its newest 25 posts on r/cscareerquestions were career questions and one interview-discussion thread.
The Oct. 19 Interview Discussion thread stood at 1 point with 2 comments when read. 35 The week's largest discussion there, at 248 points and 259 comments, argued about AI and the wider economy. 36
Levels.fyi's community threads were readable again this week and carried no dated first-person interview account, so the site contributes its salary pages and nothing else.
References
- 1Google Software Engineer Salaries
levels.fyi
- 2Meta Software Engineer Salaries
levels.fyi
- 3Amazon Software Engineer Salaries
levels.fyi
- 4Stripe Software Engineer Salaries
levels.fyi
- 5
- 6Do not waste your time interviewing at Stripe
teamblind.com
- 7Staff LinkedIn On-site Cancelled - Applications role
teamblind.com
- 8Software Engineer Interview, Apple, Oct 18, 2026
glassdoor.com
- 9Software Engineer Interview, Meta, Oct 18, 2026
glassdoor.com
- 10Any chance to avoid Google down level from here?
teamblind.com
- 11Google interview questions
glassdoor.com
- 12Amazon interview questions
glassdoor.com
- 13Amazon Software Engineer interview questions
glassdoor.com
- 14Apple Software Engineer interview questions
glassdoor.com
- 15Microsoft Software Engineer interview questions\
glassdoor.com
- 16Meta Software Engineer interview questions\
glassdoor.com
- 17
- 18I suck at interviewing\
teamblind.com
- 19Uber interview experience\
teamblind.com
- 20What is Rippling's AI Development Interview?\
teamblind.com
- 21
- 22MLDP (Full Time) Interview, Amazon, Oct 19, 2026\
glassdoor.com
- 23
- 24SDE-intern Interview, Google, Oct 18, 2026\
glassdoor.com
- 25
- 26Software Engineer Interview, Google, Oct 18, 2026\
glassdoor.com
- 27Software Engineer Interview, Amazon, Oct 18, 2026\
glassdoor.com
- 28Software Engineer Interview, Amazon, Oct 17, 2026\
glassdoor.com
- 29
- 30
- 31
- 32Software Engineer Interview, Amazon, Oct 16, 2026\
glassdoor.com
- 33Software Engineer Interview, Meta, Oct 15, 2026\
glassdoor.com
- 34Software Engineer Interview, Meta, Oct 14, 2026\
glassdoor.com
- 35Interview Discussion - October 19, 2026
reddit.com
- 36
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.