Cirata Interview Questions
& Process

I was supposed to have a Phone Screen Interview, but then I got told that there would be a coding round instead about half an hour before the call. It ended up being a 1:1 Coding round over the phone with a Software Engineer. They asked me basic Data Structures and Algorithm Questions, the kind that are usually asked in Technical Interviews. The interviewer was nice and helped me out during the call. They even gave me some pointers on what to focus on for future interviews.

It was a two stage interview process. The first stage was pretty informal and relaxed, mostly to get to know each other and for them to assess my experience. It involved a lead developer and a product manager. The second stage was more involved, including a JavaScript exercise, a small Angular project, and interviews with lead developers and HR. The purpose of the Angular project for a junior role seemed a bit unclear, as most companies focus on coding ability. They also asked me to set up my bash profile and install Node, which I found a bit strange. With about 3 years of experience, I felt this was a bit condescending. I struggled a bit with Angular, but even the person supervising my test had trouble with the tasks, so I didn't think it would be an issue. I was surprised to find out my lack of Angular experience was the reason I didn't get the job. It's concerning that Sheffield seems to expect juniors to already have experience in specific technologies. If you don't know the tech inside out, I'd steer clear of this company.

It started with technical questions, then a 30-minute written test on a scenario. This whole thing took about 45 minutes. After that, HR came on to ask some basic HR stuff.

It was a 4 stage process. First stage was a 1 on 1 interview. Second stage consisted of 2 back to back 1 on 1 interviews. Third stage was a group interview on site at their Sheffield office. Fourth stage was a 1 on 1 interview with an American VP.