Taro Logo

Principal Software Test Engineer Interview Experience - Plymouth, Minnesota

September 1, 2026
Negative ExperienceNo Offer

Process

I applied online for the principal software test engineer role. Shortly afterward, a recruiter contacted me unexpectedly by phone and immediately asked for my salary expectations. When I hesitated to give a number without discussing the role in more detail, he told me that if I couldn't provide a "number," he wouldn't move forward, as he had five other candidates waiting.

I eventually shared my salary expectation, but he responded that the role couldn't pay that much, even though the posted salary range included that figure. The recruiter appeared to be a consultant recruiting on behalf of Medtronic. The overall communication felt rushed and overly informal. There was no scheduled call or follow-up email, and the recruiter mentioned that things move fast in Plymouth, so he doesn't usually send emails. I was told the hiring manager could call me "anytime" that morning.

The hiring manager subsequently called me, and we had a good discussion about the role. I was then invited for an onsite interview, which was properly scheduled via email.

The onsite consisted of three rounds of mostly technical and conversational discussions with the hiring manager, team members, and technical lead. I enjoyed the conversations and felt my experience and résumé aligned well with the position. I could see several ways I could contribute value to the team.

However, despite the positive interactions, I came away with some concerns about the team's established processes and overall technical maturity. For a company of Medtronic's size, I expected a more structured and well-established approach to software testing and engineering practices.

Surprisingly, I received a call the very next day informing me that they had decided to move forward with another candidate.

I understand that hiring decisions depend on many factors, and I respect the company's decision. Nevertheless, the experience was mixed. While the interview conversations were enjoyable, the initial recruiter interaction could have been much more professional, and the team's processes did not fully meet my expectations.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Medtronic Principal Software Test Engineer role in Plymouth, Minnesota.

Success Rate

0%
Pass Rate

Medtronic's interview process for their Principal Software Test Engineer roles in Plymouth, Minnesota is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Medtronic's Principal Software Test Engineer interview process in Plymouth, Minnesota.

Medtronic Work Experiences