
Stripe rejected a phone screen that passed every test case because it ran past the 45-minute mark, an engineer explained what else the loop scores, and Google's L4 benchmark rose $14K while L5 fell $10K.

| Company, role page | Interviews on the page | Role difficulty | Role "positive experience" | Company "positive experience" | Days to hire | Submissions behind the figure |
|---|---|---|---|---|---|---|
| Amazon, Software Engineer | 5,287 | 3.3 / 5 | 48% | 57.5% | 25, against 28 company-wide 12 | 3,699 |
| Microsoft, Software Engineer | 2,486 | 3.2 / 5 | 64% | 66.4% | 29 13 | 1,728 |
| Apple, Software Engineer | 890 | 3.2 / 5 | 56% | 64% | 23 14 | 707 |
| Meta, Software Engineer | 2,719 | 3.3 / 5 | 56% | 56.5% | 27 15 | 2,286 |
| Company or scope | Freshness | Round, task, or process | Reported outcome | Engagement and evidence boundary |
|---|---|---|---|---|
| Stripe | 6d (Oct 20) | Software-engineer phone screen in three or four parts, all test cases passing on screen. The candidate passed the 45-minute mark while debugging the last part and got the correct output minutes later. | Rejected, with the overrun given as the reason. The poster asks when he can reapply. | 19 likes, 52 comments, 8,727 views. The top reply, at 31 likes, comes from an engineer tagged Stripe and says candidates get failed with every required part completed. Blind's summary of the 10 comments, generated Oct 22, records one commenter saying the feedback named the extra time. 1 |
| Databricks | 6d (Oct 20) | Three months end to end: recruiter screen Jul. 23, system-design phone screen Jul. 31, four-round virtual onsite Sep. 8–10, an added coding round Sep. 17, then reference checks from Sep. 23 to Oct. 5. | Rejected at the hiring committee Oct. 20. The poster says every round scored yes or "very close to strong yes", that five of his six references were called, and that the committee stack-ranks candidates. | The like, comment and view row sat under the comment box on the page and could not be read. The post's own timeline and feedback are the account it supports. 2 |
| Apple and Google, one candidate | 4d (Oct 22) | An offer against a team match. Apple ICT4 in Seattle at about $400K in the first year, with a deadline inside a week; Google L5 through the hiring committee with several managers talked to and no team committed. | No outcome reported. The poster asks which to take. | 4 likes, 49 comments, 5,100 views, and 458 people voted in the attached poll. The vote tally is not visible without voting. Current pay is $250K at 10 years of experience. 16 |
| Unnamed, across a season | 2d (Oct 24) | Five onsites, five rejections. The poster says one of three or four final rounds went imperfect each time, and that one company had him build a feature and then rejected him the next day for wanting a different background. | No offer anywhere in the season. | 2 likes, 33 comments, 2,678 views, and 270 people answered the poll. Replies trade the two explanations the poster offered himself: the market, or the competition inside each loop. 17 |
Yesterday (Oct 25) | An L4/L5 phone screen: the minimum substring length missing from a 4GB file. Brute force with hashing was redirected, the interviewer hinted at the pigeonhole principle, then a bitset, and the candidate reached the 38-minute mark without code. The follow-up asked what changes at 8GB. | Not reported. The poster asks what to do differently. | 1 like, 1 comment, 103 views. One reader can support no judgment about the format; the question itself is the useful part. 3 | |
| Credit Karma, described generically | 2d (Oct 24) | An AI-assisted coding interview: a project, then a bug report to diagnose, a feature to build and a refactor to extend the architecture. Using an AI coding assistant was required. | Not an outcome: the poster asks how interviewers grade this format. | 1 like, 3 comments, 98 views. All three replies describe a workflow; none reports a finished round. 18 |
| Company | Report date | Round, task, or process | Reported outcome | Ratings attached |
|---|---|---|---|---|
| Amazon | Oct 26 | Seattle, embedded software engineer. First round: one LeetCode-style question and one task to find a bug in a codebase. Then four back-to-back interviews, three technical and one with HR, and every interviewer asked for Leadership Principle stories after the technical question. | No offer | Neutral; average 4 |
| Oct 26 · interviewed Mar 2026 | Warsaw, through a recruiter. One algorithmic warm-up on strings and a hash map, edge-case questions, and hints when he stalled. He describes every stage as stress-free. | No offer | Positive; average 19 | |
| Oct 26 | Mountain View, data-science internship. Two 45-minute rounds back to back: technical questions with live coding, then a case analysis. The interviewer pushed back on each answer. | Accepted offer | Neutral; difficult 20 | |
| Meta | Oct 25 · interviewed Jan 2025 | Cupertino, production engineer. Recruiter screen, then two technical rounds: one data-structures round on stacks with medium-to-hard questions, and one troubleshooting round on a server-down debugging scenario. Meta sends the topic list and recommended books in advance. | No offer | Positive; difficult 6 |
| Amazon | Oct 24 | Hyderabad, through a recruiter. The assessment held one data-structures question and a project with a few bugs to fix, and the second question was AI-assisted. A week later, the screening round asked a graph question built on disjoint-set union. | No offer | Positive; average 5 |
| Amazon | Oct 24 | Tel Aviv. Assessment, then a 60-minute phone screen on Zoom: two Leadership Principle questions, then live coding in Amazon's own editor. The problem was a Number of Islands variant on an integer grid where 0 is land and 1 is water, and islands touching the border did not count. The interviewer asked for the algorithm before code. | No offer | Positive; average 21 |
| Amazon | Oct 24 | Two rounds first, and with those teams full the recruiter added two more before a team matched: two technical and two behavioral in total. | Accepted offer | Neutral; average 22 |
| Amazon | Oct 23 | Bengaluru, campus placement drive. An assessment shortlisted candidates, then two technical rounds in person. | No offer | Neutral; average 23 |
| Microsoft | Oct 23 · interviewed Sep 2025 | Mountain View, applied online, four weeks end to end. Coding questions, two system design rounds and a low-level design round. The report's advice: one round answered perfectly is enough. | Accepted offer | Positive; difficult 24 |
| Apple | Oct 22 | Cupertino. Recruiter screen, then a behavioral round with the hiring manager on past projects and collaboration, then a LeetCode-style algorithmic round, then a Super Day of four rounds, each an LLD or DSA problem. | No offer | Neutral; difficult 25 |
| Microsoft | Oct 21 | New York, through a referral. Four rounds: two LeetCode mediums and a system design round. The report's advice is to drill the tagged Microsoft mediums and know your résumé. | No offer | Positive; average 26 |
| Amazon | Oct 20 | Thirty minutes on background, 30 minutes of science questions, then 15 minutes of coding. The coding question was a medium, and the interviewer asked for the optimized solution. | No offer | Neutral; average 27 |
| Microsoft | Oct 20 | San Francisco. A first-round interview a few days after sending the CV: projects and past internships, then two LeetCode mediums. | No offer | Positive; average 28 |
| Apple | Oct 19 · interviewed Jul 2022 | Gothenburg, through a recruiter, three weeks end to end. Five technical interviews with three code tests, one hour each, and interviewers who pushed on how he had solved each project. | Accepted offer | Positive; difficult 29 |
| Thread | Date | What it reports | Engagement |
|---|---|---|---|
| Google Behavioral Round | Oct 25 | An applicant interviewing for L4 says Google's behavioral round has become a technical project discussion in which you walk through a past project. Three replies advise on what to have ready. | Score not readable this run |
| Google Technical Design Discussion Round | Oct 25 | The same poster says Google added a technical design round at L4 and asks what it covers. Its replies were not readable this run. | Score not readable this run |
| Technical assessment for SR Frontend/Fullstack in late 2026 | Oct 26 | A frontend engineer with 10 years of experience, out of work for a year, reports 150-plus applications, 20 first rounds and three technical assessments he calls awful. | Score not readable this run |
| Interview Discussion - October 26, 2026 | Oct 26 | The subreddit's weekly interview thread, opened the morning this edition was assembled. Candidates post rounds and outcomes inside it through the week. | Score not readable this run |
| Company | Median total (US) | Median by level, Oct. 26 | Median by level, Oct. 19 | Submissions | Page refreshed |
|---|---|---|---|---|---|
| $283K, from $284K | L3 $216K · L4 $315K · L5 $441K · L6 $665K | L3 $214K · L4 $301K · L5 $451K · L6 $664K | 23,584, up 80 | Oct. 24 7 | |
| Meta | $460K, from $455K | E3 $187K · E4 $307K · E5 $457K · E6 $758K | E3 $187K · E4 $307K · E5 $461K · E6 $765K | 13,963, up 32 | Oct. 25 31 |
| Amazon | $264K, from $266K | L4 $182K · L5 $274K · L6 $385K · L7 $611K | L4 $181K · L5 $273K · L6 $390K · L7 $602K | 41,901, up 129 | Oct. 25 32 |
| Stripe | $256K, from $253K | L1 $224K · L2 $286K · L3 $459K · L4 $621K | L1 $227K · L2 $285K · L3 $467K · L4 $621K | 1,549, up 7 | Oct. 24 33 |
| Level | Location | Age when read | Years of experience | Total | Base |
|---|---|---|---|---|---|
| L2, ML/AI | San Francisco | 2 days (Oct. 24) | 0 | $354K | $222K 33 |
| L3, mobile | South San Francisco | 3 days (Oct. 23) | 12 | $830K | $250K 33 |
| L1, distributed systems | New York | 4 days (Oct. 22) | 1 | $200K | $150K 33 |
teamblind.com
teamblind.com
glassdoor.com
glassdoor.com
levels.fyi
glassdoor.com
glassdoor.com
glassdoor.com
glassdoor.com
glassdoor.com
glassdoor.com
glassdoor.com
glassdoor.com
teamblind.com
teamblind.com
teamblind.com
glassdoor.com
glassdoor.com
glassdoor.com
glassdoor.com
glassdoor.com
glassdoor.com
reddit.com
levels.fyi
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.
| Dated Glassdoor reports used | 14 |
| Blind posts read with counters | 6 |
| Reddit threads read | 4 |
| Benchmark pages refreshed Oct. 24–25 | 4 |
| Company pass-rate denominators | 0 |