The interview process was pretty standard and drawn out. It started with an online application followed by a recruiter screening. Nothing particularly exciting — just going over the resume and answering basic questions like why I want the role and what my current situation is. After that came a technical screening (aka the LeetCode gauntlet). Typical algorithmic questions that don’t reflect anything I’d actually do on the job. Expect medium/hard problems on arrays, graphs, or DP — nothing domain-specific. Next was a "technical deep-dive" or system design round. They wanted a full-blown architecture for a vague problem in 45 minutes, with buzzwords flying everywhere. Felt more like a performance than a conversation. The final round was with the team. A few engineers asked more technical and behavioral questions, but it was clear they were checking boxes off a list. Got a few questions like "Tell me about a time you had a conflict" and "How do you handle deadlines?" Nothing surprising.

Overall it was okey. There were questions about deep topics of golang, high load systems and managung these systems. Also about kafka cluster . If cluster has a problem while reading messages how to handle it or manage failure