Process
I do not remember the exact stages, but here are the approx:
- HR call (30 min).
- Technical interview (90 min).
- Take-home assignment (7 days).
- System design (90 min). 5(?) Probably some behavioral interview.
HR call: Standard questions about experience and salary expectations
Technical interview (senior + EM + HR shadowing): 20 min you speak about a project of your choice from your career; 15-20 min questions in regards to the project; 20 min questions about a programming language (Go in my case); 10 min DB and message queues; 10 min infra questions; 10 min questions from you
Downsides: HR's English level wasn't great, so I could barely grasp the overall process; the technical interview was not in English (and I did not push to speak in English, which was a mistake from my side), almost no feedback.
Tips: Do not try to make jokes or outsmart your interviewers, try to guess the expected answers; otherwise, non-matching their handbook yet correct answer might be considered as incorrect.
Questions
Golang slices/sync primitives/interfaces/threads. How to improve a "very slowly" working application? Name database index types and how they work. What is k8s? What are the Kubernetes mechanics for extending its API?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the JetBrains Senior SRE role in Berlin, Germany.
Success Rate
JetBrains's interview process for their Senior SRE roles in Berlin, Germany is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for JetBrains's Senior SRE interview process in Berlin, Germany.
