Forum
Share interview experiences, uncover company culture, and get candid advice from people who've been there.
Result: Rejected Number of Rounds: 5 Sharing my Waymo loop since data fluency stuff barely has any writeups out there. Phone screen was Car Fleet Scheduler, a scheduling problem where you process pickup requests in order and return total time. I ended up going with a min heap to track which car free...
OA was 75 minutes, stats questions then two coding problems. Second one was Minimum Idleness After K Flips, binary search on the flip count plus a sliding window check, ate most of the clock but I got both fully correct so it moved me to phone screen. Round 1 was Python heavy, decorators then a live KV...
Just wrapped up the full loop and got the offer. OA was the usual format, four stats and probability questions then two coding problems. Heap question first, pretty manageable. Then a nasty DP problem that ate way more of the 75 minutes than I budgeted for. Phone screens were mostly Python depth. Decorators came up twi...
Result: Rejected Number of Rounds: 3 Phone screen was Python, an in memory file system problem, trie based. They gave the test cases so no need to write your own. Finished with time to spare, felt good about it. Onsite was 3 rounds. The one that got me was the infra round. They tell you the system is overloaded and wan...
5 YOE. VO had 3 coding rounds, all interviewer authored, no LC originals anywhere. Bombed the follow up on round 2. Rejected a week later, no feedback. Pay would've been insane so who knows.
Was digging through Robinhood filings before taking an offer and noticed a huge chunk of revenue still comes from payment for order flow and crypto trading volume, not subscriptions or anything recurring. So quarters swing hard depending on how active the market is, and if most of your TC is RSU, you're basically ridin...
Phone screen was 45 min, distributed systems focused. Got asked to design a fault tolerant request routing layer with fallback logic, basically Design Dual Circuit Breakers, tracking failure thresholds per service and deciding when to trip vs recover. Walked through state transitions, half open logic, ho...
Got a cold LinkedIn message from a Verkada recruiter. No resume needed, straight into a 60 min phone screen, split 30 coding and 30 system design. Coding was the motion detection interval problem, find windows where a sensor value crosses a threshold, basically Merge Intervals with a twist. Got the single camera case w...
5 YOE, applying for SDE. Phone screen was SD plus a coding round, went fine, moved to onsite. Onsite coding was Toy Language Grammar, parsing rules and expression eval, pretty recursion heavy with a hash table for lookups. Second round was GPU credits, standard stuff. SD was Sora scheduling, felt kinda shak...
Result: Rejected Number of Rounds: 5 For some background, I'm 6 YOE, currently at a mid size fintech company but fully remote work is basically the only thing I care about right now, my partner and I are planning to have a kid next year and the WLB reputation Pinterest has was a huge draw for me. Phone screen was the e...
Six months out from Amazon and still processing this. Went to a company with way better WLB, way less stress, and honestly I'm bored out of my mind. At Amazon I owned my service end to end, fought for headcount, and actually felt the impact when something broke at 2am. Here everyone's scope is so diluted nobody really...
Got rejected from Perplexity right after my phone screen. Wanted to share since the coding round doesn't have much info out there yet. It's the ToDo list for AI problem, four parts in Python with TaskStatus, Task, and ToDoList classes. Part 1 is basic add and update status, fast but simple. Part 2 is the real test, dep...
Everyone acting like C1 is prestigious cause it's finance adjacent. Bro it's a bank. TC: 🥜 next to any real tech offer. Not doing 4 LC mediums in 70 min for that.
Just wrapped up the loop with Airbnb, got the rejection today. Phone screen was the account merge problem, basically DFS over connected emails, went fine with time to spare. Onsite had two coding rounds, one being the booking overlap problem where you minimize stays to cover a set of nights. Got it working with memoiza...
Phone screen was the prefix sum plus timestamp query problem. Went fine, moved to VO. VO was 2 coding rounds, both interviewer authored with zero LC originals. Also an SD on the Snap story system, an AI enabled round with Opus, and an HM chat at the end. Coding rounds ran clean, bug free both times. SD is probably wher...