Interview Experiences

Recruiter reached out cold on LinkedIn. Phone screen was a medium graph problem — DFS on a grid with a twist. Onsite had two LC-mediums, one LC-hard variant, one design-lite, and Googleyness. Interviewers were friendly but the hard problem was a curveball involving union-find I hadn't seen in months.

Loop was tight — 45 min coding rounds where they expect 2 problems each. System design was a news feed variant; interviewer kept pushing on hot-key handling and write amplification. Behavioral was the standard 'tell me about conflict / driving impact / ambiguity' trio.

Stripe's format is different — no leetcode. Integration round had me consuming a flaky webhook API and reconciling payments. API design was extending an existing service. I bombed bug squash because I went too deep on one trace instead of bisecting. Got the rejection in 3 days.

Bar raiser was the hardest — 60 minutes of leadership-principle stories with deep follow-ups. They want STAR but compressed; if your answer is over 4 minutes they cut you off. LLD round was designing a parking lot with payment + reservation extension.

Take-home was building a small RAG eval harness — fun but took ~10 hours. Technicals were pair-coding on the take-home, extending it live. Research deep dive was 90 minutes on my past LLM work with one MTS grilling assumptions. Withdrew at team match — comp negotiation stalled.

UI round was building an autocomplete with keyboard nav and aria — they care about accessibility, not just whether it works. FE system design was 'design Airbnb search filters' with state sync across URL/cache/store. Very chill interviewers throughout.

Tech screen had a question on memory coalescing — half my prep was useless because I'd focused on PyTorch internals not GPU mental model. Onsite ML rounds were a mix of theory (attention math) and applied (debug a training loss curve). Got the offer in a week.

OA had 3 problems in 90 min — tight. Tech rounds were LC-hards, one on segment trees. Manager round felt positive — they said 'we'll be in touch this week'. That was 4 weeks ago. Recruiter stopped replying.

Architecture deep dive was the standout — 90 minutes on a real system I'd shipped, with two principals tag-teaming on trade-offs. They were not interested in surface design; they wanted to know what broke and how I knew. Coding was a refreshing whiteboarding exercise — actual data structures, not a leetcode lookup.

OA was 2 problems — easy + medium. Final loop was virtual, 4 back-to-back rounds with no break. Two were LC-mediums (DP and graph), one was a design-lite (URL shortener at new grad level), one was full behavioral. Interviewers were kind and gave hints when I got stuck.

Take-home was a small expense-categorization service. Pairing round extended it live — they wanted to see how I handled their feedback in real time. Sys design was 'design corporate card transaction processing' which mapped neatly to their product. Founder chat was a vibe check — they care a lot about ownership stories.

Coding round was building a small dashboard widget with their own UI primitives — no leetcode at all. FE sys design was 'design the analytics dashboard for a deployment platform' — basically their own product. They cared a lot about edge / streaming awareness given their stack.

Two back-to-back DSA rounds — one was a sliding window problem, the other was a trie-based autocomplete. LLD was designing a UPI payment flow with idempotency. HLD was scaling notification service to 10M users. Process was fast — 2 weeks from first call to offer.

Take-home was 'add a small feature to a mock issue tracker we give you'. They explicitly said no time limit but to keep it scoped. Pairing was the team picking apart my code choices — they care about taste more than algorithmic skill. Founder chat was about product instincts.

Coding screen was a tree problem — clean. Onsite coding was harder: collaborative cursor sync simulation. Sys design was 'design a block-based document editor with offline sync' — heavy CRDT territory. Got dinged on the design round; reviewer feedback said I didn't engage with consistency trade-offs.

The take-home was the best interview I've ever done — they gave me SSH access to a sandbox with a deliberately broken deploy pipeline and 2 hours to fix it. Sys design was 'design a multi-tenant container scheduler'. Team chats were genuinely chats, not stealth interviews.

Take-home was a small order-matching service in any language — I did Go. Tech discussion was them poking holes in my concurrency choices. Sys design was 'design real-time market data feed for 1M users'. CTO chat was about why I wanted to work somewhere bootstrapped vs VC-funded — they really filter on this.

SQL portion of the tech screen was hard — window functions with gaps-and-islands logic. Python part was lighter — pandas transformations. Take-home asks for a small ETL with tests and a README explaining trade-offs. Onsite next week; will update.

Payments domain round was unique — they asked about double-entry accounting, idempotency keys, and reconciliation edge cases. Coding was standard LC-medium. Sys design was 'design issuer-processor for prepaid cards'. Pleasant process overall, recruiter was responsive.

JS/React round went deep on event loop, microtasks, React reconciliation. Sys design was 'design API response viewer with large payload virtualization'. The bar for FE platform was high — they expected me to know browser internals, not just framework APIs.

No leetcode at any stage — refreshing. Coding round was implementing a small parser. Take-home was a 4-hour banking-style problem with explicit anti-patterns to avoid (no leaking PII, no race conditions on balance). Process was clean and well-communicated.

No traditional interviews. They paid me for a one-week part-time trial where I shipped a small feature into their actual codebase, opened a real PR, and joined standups. Team chats were honest two-way conversations. By far the most representative process I've ever done.

Tech screen was practical — debug a Prometheus query, fix a noisy alert. Sys design was 'design a multi-tenant metrics ingestion path'. I got rejected at team match — they said strong technically but no team had headcount for my level. Got referred internally 3 months later.