Timeline
- Recruiter reached out: July 2026 (LinkedIn)
- All 6 stages: Over 2 weeks
- Result: Pending (1 week since last round)
Background
- 5 YOE full-stack developer
- Currently at a Series B startup
- Actively interviewing at multiple companies
Stage 1 — DSA + System Design + Behavioral Mix (60 min)
Rapid-fire round covering breadth:
- Max profit single buy-sell — straightforward, expected O(n)
- Bottom view of binary tree — approach discussion more than code
- Minimum processes to allocate — resource scheduling variant
- URL parsing — given URLs with schema/host/port, group them
- Design YouTube/Netflix — focused on worldwide delivery, CDN architecture, adaptive bitrate streaming
- Logic puzzle — three bags (gold, silver, mix) wrongly labeled, identify all from one pick
- Behavioral — why looking to switch? Decision-making with limited info?
A LOT for 60 minutes. Felt like breadth assessment.
Stage 2 — System Design Deep Dive (45 min)
Question: Design a Remote Browser Isolation system for enterprises.
Deep dive into:
- Authentication & authorization (SSO, RBAC)
- Data streaming (WebRTC vs WebSocket for pixel streaming)
- Rate limiting per user/org
- Container isolation and virtual nodes
- Edge servers for latency
- Security boundaries and lateral movement prevention
Also got: Swap two variables without third variable — wanted multiple approaches (arithmetic, XOR, destructuring).
Stage 3 — Coding (45 min)
Two questions, no handholding:
- Run-length encoding compression — clean implementation expected
- Remove duplicates from sorted array allowing at most K — O(n) time, O(1) space, two-pointer approach
Medium difficulty but they wanted production-quality code. Clean variable names, edge cases handled, no shortcuts.
Stage 4 — Hiring Manager (60 min)
Full hour of behavioral. Zero coding:
- Conflict management scenarios
- Handling difficult teammates
- Why Oracle specifically?
- Walked through my side project — how I'd optimize it with AI
- "Tell me about a decision others disagreed with"
Testing for leadership signals — can you influence without authority?
Stage 5 — Bar Raiser (45 min)
More behavioral from a different angle:
- Complex project deep dive — architecture decisions, what I'd change now
- Why Oracle (yes, third time being asked)
- "What would you do if a dependency team blocks you 2 days before deadline?"
Calibrating if I'd raise the bar or just meet it.
Stage 6 — Final Coding (45 min)
Rate limiter — given sorted timestamps, count dropped requests with rolling window constraint. Sliding window approach. Discussed distributed rate limiting as follow-up.
Key Takeaways
- Behavioral is 50%+ of the evaluation at senior level
- "Why Oracle" gets asked in 3+ rounds — have a genuine, specific answer
- System design must be security-aware for enterprise roles
- Coding is medium difficulty but they want clean, readable code
- Prepare 5+ behavioral stories: conflict, limited info decisions, technical disagreement, tight deadlines, mentoring