Commure 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 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.

I had an initial chat with the recruiter. Honestly, he seemed really unprepared and quite arrogant, which was a turn-off. The way he talked about the job made it sound more like a junior Project Coordinator role that requires travel. He kept saying he'd only been there 10 months when I asked him questions. He boasted about hiring a lot of people from the big 4 consulting firms, acting like that was supposed to be impressive. The salary they offered was surprisingly low for this industry and location. I'm guessing people from those big firms are just using it as a temporary gig until they find something paying way more. Also, the salary range he mentioned didn't line up with the job posting. Again, super unprepared; he should know the salary and the job details. He also wouldn't even describe the job until I first explained my background. Since the actual job details ended up being different from the posting, I highlighted parts of my experience that I might have otherwise skipped. And now that I know what the job really entails, I'm definitely not interested. I'd already told friends that the only reason I'd agree to talk to the hiring manager would be to give them feedback on how their company is being presented.

The VP of Growth Ops reached out to me directly about this role, which I hadn't applied for. After checking out the company and seeing their strong market position, especially after merging with Athelas and their backing from General Catalyst, I decided to take the call. It was a good chat, we clicked, and he fast-tracked me. I was given a take-home assignment focused on prompt engineering, which seemed a bit unusual for a CSM role, but I enjoyed it and completed it. I assumed the next step would be the panel interview they mentioned for the following week. After submitting the assignment, I didn't hear back. Since I was in final stages with another job, I followed up. They eventually replied, saying my take-home wasn't strong enough. I asked for feedback on how I could improve, but got no response. I also followed up with the VP directly, using the same informal tone he used when he first contacted me, as I was genuinely surprised and wanted clarity. Still no reply. The whole experience felt unnecessarily vague and impersonal. If you reach out to someone first, a little professional courtesy and constructive feedback goes a long way, especially when they've invested time in a process they didn't initiate.