Correlation One Interview Questions
& Process

The recruitment process at Correlation One has three main steps. First, there's a call screening to confirm you meet the basic qualifications and are a good fit for the role. Then, an assessment to check your skills and problem-solving abilities. Finally, a one-to-one interview to chat about your experience, how you work, and if you'd fit in with the team and company culture.

The interview process was long and tiring. I had to spend 3-4 hours on a case study presentation, and then I took a technical test where I messed up the code. One of the data engineers was really rude to me during the interview, saying I had no skills and was 'a nobody.' Even though the other interviewers were nice, that interaction was bad and ruined the experience. It felt too long and stressful, and I hope they fix these things.

I applied online via LinkedIn and a recruiter reached out. I had 4 interview rounds in total. The first was with the hiring manager, who asked about my projects and technologies, why I applied to C1, my salary expectations, and daily responsibilities. He seemed impressed and I got positive feedback for the next round. Then the loop round started. An HR person contacted me via email, which was a bit weird because I wanted to discuss interview details but she only replied via email with incomplete answers, even after I requested a call. I got quick interview dates, with all 3 remaining interviews scheduled for the same day. The second round was System Design, and I wasn't sure if it was low-level or high-level design. It was a 1-hour interview, and I felt I didn't do well in either LLD or HLD. The question was to design a classroom seat blocking system for tests. I was asked about handling limited seats for popular tests (I suggested locking slots) and what to do if a third party missed sending test results (I suggested a retry mechanism). The third round was Coding, and again, there was confusion about whether it would be SQL or DSA, but they said it would be a 'logical round'. However, the question involved an array. I coded two solutions and provided test cases within the hour, receiving compliments on my speed and thoroughness. The question was to find common elements in two sorted arrays, handling duplicates. The fourth round was Behavioral, a 30-minute rapid-fire session with 10-15 questions, which I answered using real-life experiences and felt went very well. Overall feedback indicated 3 out of 4 rounds were strong, but I was rejected due to the system design round. The rejection email came two days later.

The interview process had 6 steps: First, a cultural fit chat with the headhunter. Then, a soft skills discussion with the Hiring Manager. After that, a leadership skills interview with the VP of Engineering. Following that, I had to prepare and send a Craft presentation about a distributed system I worked on (this was an offline part). Then, a live Craft presentation for the VP of Engineering, Sr. Engineering Manager, and Soft architect. Finally, a cultural fit with the Product Manager. The whole thing started Dec 3 and wrapped up Jan 12. They sent a generic rejection with no details on why.