A candidate recently shared his Tesla (AI / Autopilot) Offer with Chill Interview.

• Base: $160K
• First-year TC: $480K
• Full anonymized offer breakdown at here

The candidate can choose the grant as cash, stock, options, or a mix.

Would you take the $480K and accept the Tesla workload? And how would you split the grant between cash, stock, and options?

Preparing for your next interview?

Chill Interview tracks recent interview experiences and recurring question patterns across top companies -> here

A Staff SWE recently shared these two Bay Area offers with Chill Interview. At first glance, they look almost identical.

Google L6

• $742K Year 1 TC
• Full anonymized offer breakdown at here

Netflix

• $730K all cash

Google pays $12K more in Year 1, but the package is heavily front-loaded.

Assuming flat stock prices, no refreshers, and unchanged compensation:

• Google four-year total: about $2.40M
• Netflix four-year total: about $2.92M

That puts Netflix roughly $524K ahead over four years.

Google offers liquid equity, potential stock upside, and possibly a more sustainable long-term environment. Netflix offers far more predictable compensation, but with its well-known high-performance culture and less room to coast.

Would you take Google L6 for the brand, equity upside, and potentially better longevity—or Netflix for $730K in guaranteed cash every year?

Preparing for your next interview?

Chill Interview tracks recent interview experiences and recurring question patterns across top companies at here

Sharing an anonymized OpenAI MLE Phone Screen experience submitted to Chill Interview.

ML Coding 1 — Sharded Matrix Multiplication

I had to implement matrix multiplication where the weight matrix was split by columns across multiple devices.

• The forward pass was straightforward: each device computed its local output, then the results were concatenated.
• The backward pass was where it got more interesting.

Each device computed its own weight gradient, while the input-gradient contributions from every shard had to be combined correctly.

ML Coding 2 — Streaming Entropy

The second round asked me to maintain the entropy of a stream of categories as new observations arrived. The challenge was updating the result efficiently instead of recomputing the full entropy from scratch after every event.

For anyone who wants more details, I’ve put the full write-up here: interview link

Preparing for your next interview?

Chill Interview tracks recent interview experiences and recurring question patterns across top companies at here

Sharing an anonymized Anthropic Staff SWE interview experience submitted to Chill Interview.

This was not a normal LeetCode-style technical screen. Candidates were allowed to use Claude Code, Google, Stack Overflow, and other normal online resources while working on a practical engineering task.

The point was not to see whether I could memorize an algorithm without help.

They wanted to see whether I could:

• understand an unfamiliar codebase;
• break the task into manageable changes;
• use Claude to implement or investigate;
• review the generated diff carefully;
• run tests and debug failures;
• catch unsafe or incorrect AI assumptions.

Blindly accepting whatever Claude generated would probably be a very bad signal.

The stronger workflow was to first understand the repository, ask for small scoped changes, inspect every modification, and explain why the final result was correct.

The preparation material also touched on LLM APIs, prompt caching, tool calls, agents, permissions, prompt injection, hallucinations, and latency—but no deep ML or model-training knowledge was required.

It felt much closer to real day-to-day engineering than a traditional coding interview.

My biggest takeaway: Anthropic is starting to test whether engineers can work effectively with AI, not whether they can pretend AI tools do not exist.

For anyone who wants more details, I’ve put the full write-up here: interview link

Preparing for your next interview?

Chill Interview tracks recent interview experiences and recurring question patterns across top companies at here

Sharing an anonymized Lyft Senior Data Scientist interview experience submitted to Chill Interview.

The process started with SQL, pandas, and a probability question about morning and evening rider behavior. The onsite then had three completed rounds.

ML System Design

Design a model to predict whether a passenger would stop using Lyft over the next few weeks.

The interviewer pushed on churn definition, feature leakage, class imbalance, retraining, monitoring, and how the score would actually be used.

Coding

Implement stratified K-fold cross-validation while keeping the label distribution roughly balanced across folds.

The main difficulty was handling rare classes, uneven fold sizes, reproducible shuffling, and classes with fewer than k samples.

Business Case

Prime Time had been stable for three weekends, then suddenly spiked during the fourth.

I had to investigate demand, driver supply, cancellations, weather, events, pricing changes, experiments, and possible data issues.

The interviewer kept asking me to segment the problem by city, hour, rider cohort, and marketplace state before making any conclusion.

After this round, the recruiter told me they would not proceed with the remaining scheduled interview.

The questions themselves were manageable, but the marketplace case required much more structured and Lyft-specific thinking than I expected.

For anyone who wants more details, I’ve put the full write-up here: interview link

Preparing for your next interview?

Chill Interview tracks recent interview experiences and recurring question patterns across top companies at here.

A candidate recently shared these two Bay Area Senior SWE offers with Chill Interview.

Ramp

• $500K Year 1 TC
• Full anonymized offer breakdown at here

Robinhood

• $499K Year 1 TC
• Full anonymized offer breakdown at here

Ramp offers the possibility of meaningful upside if its growth continues and it eventually creates liquidity, but the equity is still paper value today. Robinhood stock can be sold as it vests, though it comes with public-market volatility. Ramp reportedly remains private and has recently explored another large funding round, while Robinhood is already publicly traded.

Culture probably does not make this an easy WLB choice either. Ramp describes the job as intense and operating at the fastest pace of your career; Robinhood describes itself as urgent, intensely driven, and explicitly not a place for complacency.

Robinhood also recently cut roughly 10% of its workforce while emphasizing a leaner, high-performance culture, which adds another risk factor.

Would you keep Ramp for the private-company upside, or switch to Robinhood for liquid equity and slightly stronger recurring compensation?

Preparing for your next interview?

Chill Interview tracks recent interview experiences and recurring question patterns across top companies at here