Just finished a loop for a senior backend role on their core server team. Sharing the full picture because I couldn't find good recent intel.
Round structure: Recruiter screen: 30 min, comp range check + timeline Technical phone screen: 45 min, one leetcode-medium (sliding window), one question about how you'd design an index for a specific query pattern. That second part caught me off guard. On-site (virtual, across two days): coding x2, system design x1, behavioral x1, hiring manager chat
Coding rounds: both were language-agnostic, I did Python. Standard difficulty, nothing wild. One of them had a follow-up about concurrency that I half-fumbled.
System design: this is where it gets interesting. The prompt was pretty open but the interviewer kept steering back to: how would your data model actually look, what's the schema, what happens at scale when documents get large. Very clearly a MongoDB-flavored systems question, not a generic "design Twitter" run.
Behavioral: they asked about a time I disagreed with a technical direction and stuck with my position. classic, but they wanted receipts. not just "I had concerns," they wanted the specific outcome.
Total timeline was 5 weeks from first message to offer. Offer was competitive. Team seemed legit.