After an online application, a recruiter reached out to me for an HR screen, before giving me a take-home assignment. Shortly after the assignment submission, I was scheduled for a technical screen with an engineer to discuss and expand on the take-home assignment.
From this I assumed that I did well on the assignment to move forward.
During the technical screen, I was asked to explain my code. The interviewer then added more requirements / constraints to the original question, to which I successfully answered, coded up a solution, and passed all test cases.
There was still quite a bit of time left, so the interviewer expanded a little more on the original question, but told me no implementation / coding was required. I explained my thought process and how I would implement it, and based on the interviewer's responses he seemed satisfied with my answers.
I was rejected shortly after the interview.
While the interview process was quick and smooth, I found the entire experience a bit baffling and it left me a bit confused. I take every rejection well because I see learning points from them, but this was a rare case in which I thought I did fine and there wasn't much I could do better.
I wouldn't say I felt misled but if there were any glaring mistakes or issues that I did during the interview it might be helpful if the interviewer corrected me or told me what he didn't like about my solution.
The task was a take home assignment.
The following metrics were computed from 1 interview experience for the Cockroach Labs Software Engineer role in Norway.
Cockroach Labs's interview process for their Software Engineer roles in Norway is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Cockroach Labs's Software Engineer interview process in Norway.