Stats Perform Software Engineer Interview Questions
& Process

The interview process was simple and interesting, and although I didn't get selected, it will always remain my favorite due to the scope and what it works on. The interview had basic rounds. The first round was an online full stack coding challenge, followed by a group discussion, and then a final interview.

The interview process involved several stages. It began with an HR screening, followed by a technical interview. Next, there was a coding test on the CodeSignal platform, which included 8 questions covering various aspects of web development, some of which seemed unrelated to the role. This stage also had 3 practical coding assignments that needed to pass all tests. Unfortunately, there was no way to check the test requirements, so candidates had to make assumptions. The final stage was another technical interview where candidates met with multiple interviewers. They were asked theoretical questions about technologies relevant to the position and then given tasks to implement on a whiteboard. The interviewers posed questions like 'why let instead of const' or 'why a new variable when you can call it in a conditional operator,' which felt like nit-picking and added unnecessary stress without accurately assessing skills, especially given the time constraints for providing a working solution without real-time code refinement.

It started with HR screening our profiles, then a Java technical interview, followed by a Perl technical interview. After that, there was a managerial discussion with the Director, and finally, salary negotiation with HR. The whole process was pretty smooth and moved quickly.