
Two candidates describe the early stages of the ClickHouse Software Engineer interview: a recruiter-led screen focused on background and a recent project, and a one-hour video call that opened with a resume walkthrough and a Kubernetes question.
$183K
Avg. Base Comp
$232K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Two candidates describe the ClickHouse Software Engineer process, and both ended without an offer. Neither got far enough to report a coding exercise or a system design round, so what follows is a picture of the first conversations rather than the whole loop.
One candidate applied through the careers site, heard from a recruiter within a few weeks, and had a 30-minute screen. It centered on background, motivation and one recent project discussed in depth. The interviewer was friendly and the tone was collaborative, with no coding or system design. A generic rejection email followed, and a request for feedback went unanswered.
The other candidate had a logistics-style phone screen where someone explained the role and the company, then a one-hour video call. The interviewer joined five minutes late, seemed to have the wrong resume open, started with a request to walk through the resume, asked about Kubernetes experience, and ended the call early because of a busy workload. The candidate felt they never got a chance to show how they work through technical problems.
To prepare, build a tight resume walkthrough and pick one project where you can explain your own contributions and the decisions behind them. Have a clear answer for why ClickHouse and why this role, and if Kubernetes is on your resume, be ready to discuss it concretely. With only two reports, treat this as a limited view of the process.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the ClickHouse process.
This one didn't go the way I'd hoped, and the reason was mostly the interviewer rather than the questions. The phone screen was mostly logistics. Someone walked me through the role and the company, and that was it. The real round was a one-hour video call, and it started badly. The interviewer joined five minutes late, and it quickly became clear they had the wrong resume pulled up. The first question was simply to walk through my resume. I was happy to do that, but I could tell they weren't following along. Partway through, they said it was a really busy time and they had work to do, and they ended the call early.
Because of that, I didn't get much of a chance to show how I think through technical problems. From what I'd heard going in, ClickHouse's loop is a fairly standard layout with a code screen, systems design, and behavioral rounds, and the interviewers are more interested in how you reason through a problem than in catching you out. I didn't get to experience that part. I was also asked about my experience with Kubernetes, which was a more specific question than I expected for a first conversation.
The outcome was no offer. I don't think a single rough round tells you much about the company as a whole, but it was a reminder that a poorly run interview can end things regardless of how well you've prepared.
Prep tip from this candidate
Have a concise, well-practiced walkthrough of your resume ready, since that was the opening question, and be prepared to talk concretely about your Kubernetes experience.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at ClickHouse
Design the backend and data model for a notification system
| Question | |
|---|---|
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Subscription Overlap | |
| Random SQL Sample | |
| Raining in Seattle | |
| Top 5 Turnover Risk | |
| Monthly Customer Report | |
| Largest Salary by Department | |
| Find the Missing Number | |
| Upsell Transactions | |
| Longest Streak Users | |
| Top 3 Users | |
| String Shift | |
| Scrambled Tickets | |
| Find the First Non-Repeating Character in a String | |
| Find Bigrams | |
| Size of Joins | |
| Comments Histogram | |
| N-gram Dictionary | |
| Customer Orders | |
| Rolling Bank Transactions | |
| Prime to N | |
| Minimum Change | |
| P-value to a Layman | |
| Get Top N Frequent Words | |
| Last Transaction |
Synthesized from candidate reports. Individual experiences may vary.
One candidate applied through the ClickHouse careers site and heard back from a recruiter within a few weeks. That contact led into a short first conversation. Having your resume and a clear reason for applying ready before the recruiter reaches out makes that first call easier.
One candidate had a 30-minute screen on background, interest in the role and a deeper dive into a recent project, with no coding or system design. Another described a phone screen that was mostly logistics, with someone walking through the role and company. Prepare a concise story about your motivation and one project you can explain in detail.
One candidate reports a one-hour video call that opened with a request to walk through their resume and included a question about Kubernetes experience. The interviewer joined late, appeared to have the wrong resume, and ended the call early, so technical problem-solving was never tested. Practice a clear resume narrative and be ready to speak specifically about Kubernetes work you list.