Imperative Care interview questions

The process was disjointed. It seemed like almost everyone on the team forgot they had an interview scheduled. Some were remote, some locally. Things went well once the interview process got going. But it was delayed since no-one realized I was coming. Overall. The job was for a "Systems Engineering" role. That means something in Med Device and Aerospace. As someone with years of experience in both systems engineering for Space Robotics and for Medical Device Robotics, I was confused how hard they pushed into technical domains. Not disappointed, since I'm pretty comfortable technically, just surprised. Since the job posting was for a purely "Systems Engineering" role - and was posted as such. They pushed hard on Mechanical, Electrical, and Software knowledge. (Something roboticists have much exposure too, so I wasn't too worried even if I couldn't answer just a few certain questions with certainty.) What confused me is that they clearly didn't know what they wanted. They wanted a Systems Engineer. But based on the questions, each interviewer wanted someone who is a master of all 3 domains, but will work for a mid salary in the Bay Area? There was a mismatch for the job posting. There was a mismatch between every single interviewers desired skills for the role. And there was a mismatch between compensation, for that level of skillset. I didn't get an offer, but their lack of organization (for the interview, the team and the company), and their lack of process for a medical device company, were just major red flags anyway, even before the compensation concerns. The tech is headed in a cool direction, but it's clear there is a long slog ahead - and clear direction is lacking (from even above the team I was interviewing for).

I recently completed an extensive interview process with Imperative Care that spanned over two months. I met with eight individuals, ranging from the Coordinator level to the C-Suite, totaling over six hours of interview time. Everyone I encountered was impressive—kind, intelligent, and deeply committed to the company's mission. While I have a high level of respect for the team, the conclusion of the process was disappointing. After such a significant time investment and reaching the final stages, I received only a brief, rejection email. I believe that when a candidate dedicates this level of effort, a brief feedback call is a more appropriate professional courtesy. Prospective candidates should be prepared for a rigorous, high-commitment process and the possibility of a standard email notification at the end, regardless of the round reached.