Commure Software Engineer Interview Questions
& Process

This was one of the most uncomfortable interviews I've ever had. The interviewer seemed totally uninterested, barely engaged, and there was no real conversation or back-and-forth. It felt cold and off from the beginning. I finished the problem, covered edge cases, and discussed trade-offs, but there was hardly any follow-up, no deep dives into my reasoning, and no real collaboration. It felt more like I was just silently doing a task for someone who had already mentally checked out. A good engineering interview should test communication, problem-solving approach, and collaboration. This, however, felt very transactional and rigid, like they were just looking for a specific answer they had in mind instead of having a genuine engineering discussion. The interviewer was also based overseas, which for a US healthtech company, makes me wonder if their engineering investment and hiring plans match their domestic growth. Communication issues and cultural differences can really hurt interview quality and team chemistry. All in all, it left a bad impression, not because it was hard, but because of the disengagement and unprofessionalism.

It was a pretty standard interview process. I had a recruiter screen first, then two technical interviews, followed by one system design interview, and finally three interviews with the hiring manager and executives. The technical interviews weren't like typical LeetCode problems; they were more focused on implementation details. The other parts of the interview were pretty standard, asking about my previous technical projects.

It started with a phone screen where I talked about my background and why I was interested. Then, there was a python technical interview, which was a live coding challenge. I managed to get the implementation working, but we ran out of time before I could refactor or put it into classes. Near the end, they asked how I'd make it production-ready, and I talked about refactoring, using a DB, handling errors, and deploying with AWS Lambda. I think I could've explained that part better, maybe more structured or with a template. The interviewer was helpful when I was stuck, pointing things out. My mistakes were using a reserved word as a function name, messing up a key when getting expiration data, not explaining my production approach clearly, and possibly not refactoring live even though I said I would.