SICK Software Engineer Interview Questions
& Process

First, there was a recruiter screening for 30 minutes. Then, a 30-minute hiring manager chat. After that, 3 rounds of panel interviews, each lasting an hour. These panels included the recruiter and manager, engineers, and product teams. They really emphasized behavioral questions. The first panel focused on behavioral questions to gauge how you handle various situations. The engineer interview covered resume points, design questions, and one LeetCode medium problem (they weren't great with the coding interview setup, using copy-paste on an IDE and screen share was clunky and sometimes wasted time; better communication from the interviewer would help). The product team interview also had behavioral questions but felt more pleasant, discussing scenarios of collaboration between product and engineering teams. Overall, it was a decent experience.

It was a lengthy interview process, spanning 1.5 months with six rounds in total. The interviewers were all very friendly. I encountered two technical rounds, a discussion with the project manager, one with the product manager, and two rounds with recruiters. I felt I answered most of the questions well and even discussed my answers with some experts who were impressed. Ultimately, it was quite disappointing not to receive an offer.

There were 2 in-person interviews. The first interview was with an HR person, the direct manager, and a third technical person. The process was: HR presented the company structure. Then the candidate presented themselves. Then the job was presented. The second interview was with an HR person, the direct manager, and the department head. Here, first another self-presentation, then critical questions about sales skills and getting to know the team.