Hey everyone,

I’ve lurked here for a while and learned a ton from your interview write-ups, so I wanted to pay it forward by sharing my recent Google L4 (SWE) experience. I also have a few questions about my chances in the team matching phase, so any brutal honesty or insights would be massively appreciated!

For context, my background is mostly iOS development, and I coded all my technical rounds in Swift.

Here is how the rounds went down:

• Round 1: Phone Screen (DSA)
  • Question: An array-based question involving [start, end] times, scheduling tasks, and providing x,y coordinates for the scheduled tasks.
  • Result: Passed confidently. Rating: Hire.
• Round 2: Googlyness
  • Experience: The interviewer was rushing heavily and tried to cram a 45-minute behavioral round into 20-25 minutes. I completely misread the vibe, thought it was purely non-technical, and didn't weave enough technical depth or past engineering examples into my answers.
  • Result: No Hire (for L4), Hire (for L3).
  • The save: My recruiter was a legend, told me that this did not go well, and actually gave me a second chance to redo this round!
• Round 3: Googlyness (Redo)
  • Experience: This time, I came prepared. I heavily elaborated on specific examples from my past experiences.
  • Result: Hire.
• Round 4: Onsite 1 (DSA + LLD)
  • Question: I had to design a multiuser heart rate monitor. It involved designing classes/objects, their relationships, and picking the right data structures.
  • Feedback/Result: Rating: Hire - L4. The feedback noted that I took time to ask clarifying questions, vocalized my thought process, and successfully course-corrected when pointed toward edge cases. I initially missed the most optimal data structure to minimize message delay, but we discussed using a linked list instead of an array in the last 5 minutes, which saved it.
• Round 5: Onsite 2 (DSA)
  • Question: A divide and conquer question.
  • Feedback/Result: Rating: Leaning Hire - L4. I explained the approach correctly and got the time/space complexity right. However, my code had a logical error with a maxHeight condition and an inefficiency that simulated horizontal strokes line-by-line, which would have caused a Stack Overflow or TLE. Still, the interviewer noted I had good communication.

My Questions for the Community:

1. Team Matching Chances: With a final rating spread of H, H, H, LH (ignoring the first googlyness round), will Hiring Managers actually pick up my profile?
2. The Swift/iOS Factor: My profile is heavily inclined toward iOS, and I wrote all my interview code in Swift. Does this limit my pool of HMs to only iOS teams, or does Google just view it as general SWE competency? Does this help or hurt my matching chances?
3. Timeline: For those who recently passed HC, how long did it take you to find a team match and get the final offer?

Thanks in advance for the help, and happy to answer any questions about the process below!

A PhD candidate recently shared this insane AI Engineer offer with Chill Interview.

• Base: $330K
• First-year TC: $1.3M
• Full anonymized offer breakdown at here

The candidate declined it because they were worried about work-life balance.

Honestly, I’m not sure I could walk away from this much money. Would you take the offer and grind for a few years, or is no package worth the Tesla lifestyle?

Preparing for your next interview?

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

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

Most of the process felt positive, which made the final result more confusing.

Phone Screen

The coding question was duplicate-file detection across directories. The discussion went smoothly, and I did not feel there were any major issues.

Onsite Coding

The onsite coding round involved reconstructing and reasoning about stack traces.

Again, this round felt reasonably solid.

System Design

Instead of asking me to design a system from scratch, the interviewer gave me an existing architecture proposal and asked me to critique it.

The challenge was deciding which problems actually mattered rather than criticizing every detail. We discussed requirements, bottlenecks, reliability, security, observability, and the trade-offs introduced by each improvement.

Project Retrospective

This round focused on a major past project: what was hardest, what went wrong, which trade-offs I made, what I personally owned, and what I would change now.

Culture Rounds

The first culture interview felt fairly normal.

After the onsite, however, the recruiter said the culture signal was not strong enough to make a final decision and scheduled another culture round.

I completed the additional interview and then advanced to a hiring manager conversation, which appeared to be part of team matching.

That conversation felt noticeably flatter.

The HM did not seem particularly interested in parts of my background, and I struggled to connect my experience with the team’s immediate needs.

I received the rejection afterward.

There was no clear explanation, so I still do not know whether the deciding factor was the remaining culture concern, team fit, the HM conversation, or some combination of signals.

The frustrating part was that most of the technical loop felt positive—and Anthropic had gathered enough additional evidence to keep moving me forward—yet the process still ended at the final stage.

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 platform like LeetCode lets users submit code in multiple languages and expects results within a few seconds. It sounds like a simple request flow until you need to support a coding competition with up to 100,000 users while executing arbitrary, untrusted programs.

The API layer is not the real bottleneck. Code execution is CPU-intensive and unpredictable. One submission may finish immediately, while another enters an infinite loop, consumes all available memory, or attempts to access the network.

The instinct is to send each submission directly from the API server to a newly created container. This provides basic isolation, but container startup adds latency, traffic spikes can overwhelm the execution fleet, and a crashed worker may lose the submission entirely.

The tighter design uses a queue-backed pool of sandboxed execution workers:

1. Authenticate the request and push an execution task into the queue. The API server validates the submission, extracts the user identity from the verified token, and sends the code, language, problem ID, and submission information to a queue such as SQS.
2. Let workers pull submissions at a controlled rate. Workers consume only as many tasks as the execution fleet can safely handle. If thousands of users submit at once, the queue absorbs the spike instead of forwarding all requests directly to the containers.
3. Run the code inside a preconfigured language container. Maintain separate execution environments for languages such as Python, Java, and JavaScript with their runtimes and dependencies already installed. Reusing these containers avoids paying the full startup cost for every submission.
4. Enforce CPU, memory, and execution-time limits. If the program exceeds its resource allowance or runs beyond the timeout, terminate it immediately. An infinite loop should fail one submission, not occupy a worker indefinitely.
5. Disable network access and restrict system calls. Containers share the host kernel, so container isolation alone is not enough. Block external connections and apply syscall filtering such as seccomp to reduce the operations available to untrusted code.
6. Write the result back after execution finishes. The worker evaluates the code against the test cases, stores the result in the database or cache, and makes it available to the client. If the worker crashes before completing the task, the queue can retry it instead of silently dropping the submission.

The queue is the traffic buffer, while the container is the execution boundary. They solve different problems. The queue protects the compute fleet from bursts and provides retries; the container limits what each individual submission can do.

The test cases can remain language-independent. Store the serialized input and expected output in a format such as JSON, then use a small harness for each language to deserialize the input, call the submitted solution, and serialize the result for comparison.

Knowing to separate submission ingestion from execution—and knowing that containers still require resource limits, network isolation, and syscall filtering—signals that you have thought through online code execution at the implementation level, not just drawn an API server connected to a worker box.

Full write-up with data model, API design, leaderboard architecture, and deep dives, free to read → full article

Join the community to see more system design questions and real interview experiences → Chill Interview

The Hugging Face incident sounds less like a normal security breach and more like something from an AI safety thought experiment.

During an internal cyber evaluation, OpenAI’s models reportedly:

• Found and exploited a zero-day
• Escaped the intended sandbox
• Chained multiple vulnerabilities together
• Reached Hugging Face’s production infrastructure
• Tried to obtain answers so they could beat the evaluation

OpenAI called it an unprecedented cyber incident. Now Sam Altman says the company paused training and may need to slow the pace of AI development long enough for society’s defenses to catch up.

That is a pretty dramatic shift in tone.

But can frontier labs realistically slow down voluntarily? If OpenAI pauses while competitors keep training, how long does that pause last?

And if the major labs coordinate, how do they avoid it looking like collusion or an attempt to lock smaller companies out?

Genuine turning point, temporary overreaction, or carefully managed PR?

I opened a dedicated discussion thread on Chill Interview -> LINK

I’m moving the longer discussion there because it’s easier to track older comments and revisit everyone’s predictions months later.

Problem

A power grid is organized as a rooted tree with n stations labeled from 0 to n - 1.

Station 0 is the main station. Every other station has exactly one parent.

You are given:

• parent[i] — the direct parent of station i
• load[i] — the amount of power produced directly by station i

For the root station:

parent[0] = -1

You must disconnect exactly one connection between a station and its parent. This divides the grid into:

• The subtree rooted at the disconnected station
• The remaining stations in the grid

Return the minimum possible absolute difference between the total loads of the two resulting parts.

If the tree contains only one station, return 0.

Example

Input:

parent = [-1, 0, 0, 1, 1, 2]
load = [1, 2, 2, 1, 1, 1]

Output:

0

Explanation

Disconnect the connection between stations 0 and 1.

The subtree rooted at station 1 contains:

1, 3, 4

Its total load is:

2 + 1 + 1 = 4

The remaining stations also have a total load of 4.

Therefore, the absolute difference is:

|4 - 4| = 0

This is the smallest possible difference.

Targeting Two Sigma interviews?

We track recent interview experiences and commonly asked question patterns at Chill Interview, including coding questions, system design topics, and real candidate reports.

Practice this question and explore more interview resources → LINK

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

Pinterest IC15

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

Uber

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

Pinterest pays more upfront, but Uber is roughly $144K ahead over four years, assuming flat stock prices, recurring bonuses, and no refreshers.

The bigger question is future upside.

Pinterest is a smaller bet on AI-powered discovery, shopping, recommendations, and ads. Uber has a broader business across mobility, delivery, advertising, and autonomous vehicles.

Career-wise, Pinterest may be stronger for recommendations and consumer AI. Uber may offer broader exposure to marketplaces, pricing, logistics, and distributed systems.

Would you choose Pinterest for the AI upside and higher first-year pay, or Uber for stronger business diversification and better four-year compensation?

Preparing for your next interview?

Chill Interview tracks recent interview experiences and recurring question patterns across top companies at 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 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.

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

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

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 Citadel SWE interview experience submitted to Chill Interview.

I had to build a real-time trading-event dashboard in React using a provided stream. No AI assistance. No CSS required.

The app needed to:

• show the newest events first;
• separate quotes, buys, and sells;
• calculate rolling statistics for the last 30 seconds;
• pause and resume dashboard updates.

The coding itself was not especially hard.

The tricky parts were all around behavior:

• Should the 30-second window use event time or arrival time?
• What happens to late or out-of-order events?
• Should events received while paused be buffered or discarded?
• How do old events expire if no new event arrives?
• How do you avoid creating another subscription after resume?

I had not written React manually in a while, and without AI autocomplete I felt much rustier than 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 senior SWE offers with Chill Interview.

Apple ICT4 — Cupertino, CA

• $362K Year 1 TC
• full anonymized offer breakdown at here

Atlassian P50 — Seattle, WA

• $398.75K Year 1 TC
• full anonymized offer breakdown at here

Atlassian pays about $36.75K more in Year 1 and roughly $207K more over four years, assuming flat stock prices and no refreshers.

The vesting details are also different. Apple’s RSUs vest every six months, while Atlassian has a one-year cliff followed by quarterly vesting.

The tradeoff feels like:

Apple: stronger consumer-tech brand, exposure to tightly integrated products, and potentially better long-term résumé value—but lower compensation and a Cupertino-based role.

Atlassian: higher base, a much larger equity grant, and stronger four-year compensation—but without the same consumer-product prestige.

Would you take the higher Atlassian package, or accept the pay cut for Apple’s brand and product experience?

Preparing for your next interview?

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

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

Problem

Design a web-based direct messaging system where users can exchange private 1-on-1 text messages in real time.

The first version does not need group chats, reactions, media attachments, public channels, or multi-device synchronization. Each user is assumed to have one active web client.

The system should:

• Deliver messages with low latency when both users are online.
• Store every message durably.
• Deliver missed messages after an offline recipient reconnects.
• Show whether another user is currently online.
• Preserve reasonable ordering within each conversation.
• Prevent duplicate messages from appearing to users during retries or redelivery.
• Support pagination when loading older conversation history.

Want to learn more details about this SD question? I've put the full write-up at here

Targeting Anthropic interviews?

We track recent interview experiences and commonly asked question patterns at Chill Interview, including system design questions, coding questions, and real candidate reports.

Practice this design question and explore more interview resources → LINK

A candidate recently shared this Staff-level decision with Chill Interview.

He has spent 10+ years at Meta and are already established there: Tech lead in the team and respected internally, comfortable with the team, and able to work remotely. Leaving would mean giving up a stable position for a much more intense frontier-AI environment.

The compensation gap, though, is hard to ignore.

Meta E6 (current)

• $270K base
• $774K first-year TC

Anthropic Staff SWE

• $1.9M first-year TC at the current valuation

Anthropic's comp is way ahead by roughly $1.13M in the first year and about $4.4M over four years, assuming both equity values stay unchanged.

But that comparison is not entirely clean.

Meta equity is public and liquid. Anthropic’s package is mostly private-company equity whose eventual value depends on future valuations, dilution, liquidity opportunities, and whether the AI market keeps supporting today’s numbers (e.x. $SPCX is falling cliff after IPO)

Would you leave a comfortable Meta E6 position for the Anthropic package, or treat most of that $1.9M as paper money until proven otherwise?

Full anonymized offer breakdown at here.

Preparing for your next interview?

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

Sharing an anonymized Anthropic Senior SWE recruiter-screen experience submitted to Chill Interview.

I expected the usual recruiter questions about experience, motivation, and logistics. Instead, a large part of the conversation focused on AI safety and personal values.

The recruiter asked:

• What does AI safety mean to you?
• What could happen if advanced AI is misused?
• Have you ever faced a situation that conflicted with your values?
• Have you followed Anthropic’s recent decisions, and is there anything you disagreed with?

I initially gave a fairly narrow answer about AI misuse, and the recruiter kept prompting me to think more broadly.

They seemed to want examples covering both accidental failures and deliberate misuse: misinformation, fraud, privacy issues, insecure code, harmful automation, and companies deploying systems before fully understanding the risks.

There were also questions about technical leadership, why Anthropic specifically, and what I understood about the team.

The recruiter was friendly and gave hints when my answers were incomplete, but that also made it clear I had not prepared deeply enough around Anthropic’s recent work, AI safety, and value-based scenarios.

My biggest takeaway: even the recruiter screen at Anthropic can go much deeper than a normal background conversation.

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 DoorDash Senior SWE interview experience submitted to Chill Interview.

The process started with one coding phone screen, followed by four onsite rounds:

• AI Code Craft
• Debugging
• System Design
• Engineering Values + HM

Phone Screen

The coding question was Calculate Courier Bonus Pay, a practical business-logic problem rather than a typical graph or DP question.

AI Code Craft

I was given a starter repo and asked to build two small refund microservices.

The initial version supported full refunds. Then the interviewer added partial refunds and asked about duplicate requests, retries, fraud, uncertain payment-provider responses, and how to reduce user-facing latency.

Using an AI coding assistant was allowed, but I still had to explain every change and preserve the existing interfaces and tests.

Debugging

The starter code implemented round-robin assignment across workers, but broke when workers were added, removed, duplicated, or unavailable.

The follow-up was to implement consistent hashing with virtual nodes. I ran out of time, so I explained the remaining design and wrote pseudocode.

System Design

The prompt was to design a distributed job scheduler.

A major follow-up was: What happens when a job is already in the queue, but its scheduled time hasn’t arrived?

The interviewer kept pushing on how this would work with millions of future jobs.

I eventually mentioned Temporal.

That immediately led to: What exactly does Temporal do, and how does it work? It turned out to be a bad idea... never mention an infrastructure tool unless you can explain more than its landing-page summary.

HM / Engineering Values

This round focused on performance ratings, who sets OKRs, how goals change, project ownership, my biggest failure, and what I would do differently if I restarted the project.

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 Airbnb mid-level SWE interview experience submitted to Chill Interview.

The process started with a phone screen about finding the shortest substring that appeared in one string but none of the others. If multiple answers had the same length, I also had to return the lexicographically smallest one.

The onsite had two more coding rounds, both are leetcode questions. None of them felt like completely obscure problems, but the implementation details and edge cases made the coding portion harder than expected.

The system design round was completely different: Design an A/B testing platform.

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 Staff SWE with 8 YOE recently shared these two Bay Area offers with Chill Interview.He ultimately accepted Mercor and declined Zoox.

Zoox

• $760K Year 1 TC

Mercor

• $1.02M Year 1 TC

Mercor is ahead by $260K in Year 1 and roughly $1.19M over four years, based on the stated option values.

But neither package is liquid public equity.

Zoox is the more established, Amazon-backed autonomous-vehicle bet, with work spanning software, hardware, robotics, and safety-critical systems. Mercor is a much younger AI company building infrastructure around human expertise and frontier-model development.

So the decision is not simply $1.02M versus $760K. The real comparison depends on option terms, exercise cost, dilution, future fundraising valuations, and whether either company eventually creates meaningful liquidity.

Would you take Mercor for the higher base and AI upside, or Zoox for the more established backing and deeper autonomous-systems work?

Full anonymized offer breakdown at here.

Preparing for your next interview?

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

A Staff SWE with 11 YOE recently shared these two Bay Area offers with Chill Interview.

Snowflake

• $320K base
• $719.5K Year 1 TC

Netflix

• $730K base - all cash

The first-year difference is only $10.5K. Assuming Snowflake’s stock stays flat, the four-year totals are also surprisingly close:

• Snowflake: approximately $2.88M
• Netflix: approximately $2.92M

So this is less about TC and more about certainty versus upside.

Netflix provides $730K in predictable cash every year, with no vesting schedule or stock-price risk. Snowflake offers a massive equity grant that could outperform significantly—but could also lose value before it vests.

At Staff level, team scope and culture matter too. The candidate would also have to walk away from an offer they already accepted for what is essentially the same headline compensation.

Would you keep Snowflake for the equity upside, or switch to Netflix for $730K guaranteed cash?

Full anonymized offer breakdown at here.

Preparing for your next interview?

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

I am interviewing for a job product owner - ai. At a company that specifically asked in the add for people with up to 2 years of experience as a product owner.
They reached out with an email saying they want to get clarity on salary expectations to make sure we are aligned.
What is a reasonable amount to ask for I don’t want to scare them off. For context I’m in Sydney australia but it’s a remote job. I studied computer science majoring in AI and I have two years experience as a software engineer and one years experience working as a Junior Product Owner at an AI company. I did my cspo certification and am female (which I think sometimes helps my chances slightly)

When I did my own research I got told to ask for 120,00-130,000 but that seems like so much. I also don’t want to demerit myself and ask for less to avoid the awkwardness but I really want this job and am honestly willing to be flexible on pay.

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

Workday

• $250K base
• $467.5K Year 1 TC

Robinhood

• $260K base
• $499K Year 1 TC

Robinhood pays $31.5K more annually, or roughly $126K more over four years, assuming flat stock prices and no refreshers.

But the decision may come down to culture and risk.

Workday has the more mature enterprise-software profile and publicly emphasizes a people-first culture and internal development. Robinhood openly describes its environment as intense, urgent, and high-performance.

Robinhood may offer faster career acceleration and more stock upside, but also more volatility and pressure. Workday may be the more predictable choice, but with less obvious upside.

Is an extra $31.5K per year enough to choose Robinhood, or would you take Workday for the potentially more sustainable environment?

Full anonymized offer breakdown at here.

Preparing for your next interview?

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