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.
Get your personalized Thermo Fisher Scientific Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I went through a pretty compact loop: three rounds total. The first two rounds were technical, and the third was a managerial discussion. Overall the difficulty felt average, but it was clearly structured.
The technical parts pulled from what I’d learned in Java and how I’d used common pieces like collections, then moved into Spring Boot. Most of the conversation centered on fundamentals rather than anything exotic, and I felt like I could follow what they wanted to test.
2 months ago
Easy Negative Washington, DC
My process didn’t feel professional from the start. I got an interview invitation at 10 PM for an interview the very next morning, which left me almost no time to prepare. Even after that, the communication stayed slow and sloppy—scheduling took a lot of back-and-forth and I often had to prompt for updates.
When I finally spoke with the interviewers, it was clear they weren’t ready; at one point they said they hadn’t reviewed my resume before we started. I stayed in the process for over a month, and then I received a generic rejection message.
3 months ago
Easy Positive United States
My interview flow was straightforward and fairly quick. I started with a recruiter connection, then moved into an HR/panel-style set of conversations …
4 months ago
Average Neutral Singapore
I applied online and heard back from the recruiter/talent acquisition team about a month later. The interviews were urgent enough that I ended up with…
4 months ago
Easy Positive United States
I ended up interviewing in a structured sequence that started with a recruiter screen. I then met the hiring team through a panel format, and the over…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically consists of a recruiter screen followed by a mix of technical and managerial discussions, often spanning 2-4 weeks. Candidates reported varying experiences with the speed and organization of scheduling, with some noting a lack of communication post-interview.
Recruiter screenManagerial discussionTimeline
Technical Assessment Focus
Technical interviews generally emphasize fundamental programming skills, particularly in Java and related technologies, with questions often centered on practical problem-solving rather than advanced or niche topics. Candidates should prepare for both coding challenges and discussions about their past projects and experiences.
JavaProblem-solvingCoding challenges
Behavioral & Values Assessment
Candidates can expect a significant focus on behavioral and values-based questions, assessing how their experiences align with the company's culture and teamwork dynamics. This includes scenario-based discussions and evaluations of past work experiences.
Behavioral questionsCultural fitScenario-based
Panel Format & Collaboration
Many candidates experienced panel interviews where multiple interviewers engaged in discussions about their background and technical abilities. This format often felt collaborative, though some candidates noted it could be more interviewer-led than interactive.
Panel interviewCollaborationInterviewer-led
Communication & Follow-up
Communication throughout the interview process varied, with some candidates appreciating clear updates while others faced delays and a lack of follow-up after interviews. Candidates should be prepared for potential gaps in communication.
CommunicationFollow-upTransparency
Overall Difficulty & Experience
The overall difficulty of the interviews is generally perceived as average, with candidates reporting a mix of stress levels. While some found the process encouraging and well-structured, others felt mismatched in expectations, particularly regarding role alignment.