HeliosX Group Software Engineer Interview Questions
& Process

The interview process had four rounds spread out over a few weeks. First was a recruiter call to go over the role and basic requirements. Then, a technical chat with the hiring manager that was really about system design and architecture for their current software. They asked about development methods, scaling plans, and managing different product/market needs with shared tech. They didn't really dig into my resume much. Round 3 was a take-home project, a medical API thing, which took way longer than they said it would and seemed bigger than a typical take-home. Finally, Round 4 was a code review of my take-home work, with deep dives into my coding decisions, followed by another problem to solve on the spot. This whole thing felt too long and not very efficient, like it took up a lot of candidate time for no good reason. The interviewers were a bit tough to connect with, which made me wonder about working with them daily. The technical part was fine for the job, but the way they ran the interviews wasn't great for candidates or managing time.

It started with a standard screening call with someone non-technical. Then, there was a semi-technical interview with a higher-up, which was actually a good experience. After that, a take-home exercise that took about 3-6 hours realistically. Finally, a technical interview with two senior engineers. This last interview wasn't really about nitty-gritty details but more about domain and architectural knowledge. It would have been nice to show some problem-solving/coding skills live! If you're good at drawing architectural diagrams (like ER diagrams) and can model domains on the fly, you'll do well. They really value this, which makes sense. I have a feeling they might be trying to get senior experience/skill at a mid-level salary, as they mentioned they have enough seniors. Sadly, no feedback was given, even though I've been trying to get it and was even asked for my availability for feedback multiple times over weeks by the initial screener. This lack of feedback is why I had a negative experience.

The interview process was really well organized and moved quickly. It started with a screening call that gave me a good idea of what to expect. The process had three main parts: a chat with the Engineering VP, a technical interview, and then an interview focused on values and culture. I was impressed by how fast I got feedback after each interview. My recruiter, Nicole, was great, checking in after each stage and usually letting me know if I was moving on within a day. Overall, it was a good experience, mostly because of the clear communication and speed.