HeliosX Group Interview Questions
& Process

The interview process included a recruiter chat, a meeting with leadership, and a technical interview. The recruiter and leadership interactions were pleasant. However, the technical interview was a negative experience. There was no introduction from the interviewers or myself, and a significant portion of the time was spent by one interviewer arguing about a fundamental concept that I was correct about, which was later confirmed by Google. I was surprised by their lack of knowledge. The interviewer's general demeanor was arrogant. Additionally, one interviewer kept their camera off throughout the entire interview, remained silent until the very end where they simply said 'bye'. Given this, I was relieved not to be moving forward.

So, the whole thing started with a chat with the recruiter, which was pretty good, felt friendly and all. Then I had a product talk. But honestly, that part felt way different. From the jump, this person seemed kinda checked out, not really into it. Like, maybe they didn't prep or just didn't care. I didn't move on, which is fine. But the feedback? Just this lazy, 'didn't go into enough detail.' Not helpful at all. If they wanted more, they should've dug deeper, you know? Especially with complicated product stuff that needs context. The biggest letdown was how little effort the feedback seemed to have. We put in a lot of time getting ready for these, so you'd think at least one solid, specific reason why you're not a fit would be decent. It's just more respectful and actually helps us get better.

The interview process started with a call with the recruiter, followed by a call with the Head of Engineering. Then, there was a take-home test which involved a multistep form. After that, I had a live coding session to discuss the take-home test and make further tweaks. Finally, there was a values interview. The whole process took about 4 weeks. I was rejected because I didn't seem enthusiastic enough about the company and role, and didn't show enough seniority in leading projects. My React knowledge seemed outdated even though I used the latest Nextjs package and documentation for the take-home test, and I'm not sure why they assumed I couldn't pick up new skills based on project-specific coding standards. Ultimately, it felt like they found someone who was a better fit, which happens in a candidate-heavy market. My advice for other candidates is to research the company thoroughly, as it seems to be as important as skills.

The interview started with a 30-minute session focused on scenario-based questions to gauge how I would handle different situations. It began with me introducing myself to the interviewer. Following that, the interviewer outlined the interview process and presented an example prescription, which we reviewed using the prescription system.