Real, anonymous reports from people who interviewed for Software Engineer at Thermo Fisher Scientific, newest first and distilled into what to expect across the loop.
After a recruiter reached out, I went through a pretty typical sequence: a recruiter call first, then a mix of manager and team interviews, sometimes with multiple people in the room and a group involved in the final decision. Across those conversations, I noticed the process stayed focused on my background, how I’d handled past work, and how I fit the team’s expectations. When the rounds were with the team, I also talked about how everyday problems get solved there, and the interviews felt welcoming rather than adversarial.
My process felt lighter on the formalities and more focused on targeted technical fit. I went through about two rounds total, with an interactive setup: first there was a written component, and then there was an online interview with a panel where at least two people participated. The questions leaned into practical familiarity—especially working with SAS—and also a basic understanding of clinical trials.
The interview process typically follows a structured sequence starting with a recruiter call, followed by technical interviews with managers and team members, often culminating in a final round with higher management. Interviews generally last between 30 to 60 minutes and are designed to be conversational and welcoming.
Candidates can expect a blend of technical questions that emphasize practical knowledge and familiarity with core concepts, such as data structures, algorithms, and specific programming languages relevant to the role. The interviews often connect questions to the candidate's past projects and experiences.
Interviews include behavioral questions aimed at assessing cultural fit and alignment with the company's values, often using the candidate's previous experiences as a basis for discussion. The tone is generally friendly, focusing on how candidates approach problem-solving and teamwork.
Some candidates reported inconsistencies and poor communication throughout the interview process, including scheduling issues and lack of follow-up after interviews. This can lead to frustration and a negative overall impression, regardless of the interview content.
Candidates may face coding challenges that require them to implement solutions under pressure, sometimes with unexpected twists that can disrupt their thought process. The experience can vary significantly depending on how the interviewer conducts the coding session.
The overall difficulty of the interviews can vary, with some candidates finding the process manageable and others feeling overwhelmed by specific technical questions or the interview format. Many candidates noted that the experience felt more relaxed than adversarial.