HR reached out to schedule a Zoom call with herself and a director. The call was fairly short, and the director mainly wanted to sanity-check that I fit what they were hiring for and that the role made sense for me. After that, they booked me for a plant tour and an additional interview with their chief chemist, and that chemistry-focused interview ran for the full hour it was scheduled.
I was flown out with expenses covered, which turned out to be a bit of a headache because the rental and hotel weren’t prepaid, so I had to put my own card down and then handle reimbursement later. The plant tour and the in-person interview both went well—I felt like I presented myself clearly, and the director even said he expected to make a selection by the next week.
8 months ago
Average Negative United States
My process started with a Microsoft Teams call that lasted around 30 minutes. It was framed around the Standard Products team—what the responsibilities were, and a discussion of my resume.
The part that stood out was that the recruiter didn’t seem to have much engineering context. When I asked about projects and how the team was structured, I didn’t get reasonable answers, and I was left with the impression I was being judged as unprepared even though the description of the role was vague. Overall it didn’t feel like a technical conversation I could meaningfully win, and it ended without moving forward.
> 1 year
Easy Negative Houston, TX
I went through a fairly typical multi-round screen that leaned heavily on practical software skills. First, there was an HR call where we went over my…
> 1 year
Easy Negative United States
My first contact was a phone call with a recruiter who didn’t have technical experience. Early on, the conversation turned into relocation expectation…
> 1 year
Easy Positive Padua
My interview experience stretched over a longer, more process-heavy stretch than I expected. It started with an HR-driven setup and then moved into st…
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
Initial HR Screening
The interview process typically begins with a short HR call to discuss the candidate's resume and fit for the role, but candidates noted that the HR representatives often lacked technical knowledge, which could lead to vague discussions and a lack of clarity about the role.
HR callRecruiter experienceRole clarity
Technical Interviews
Candidates should expect technical interviews that focus on practical software skills, including discussions about past projects and core engineering topics like C++ and Docker, often mixed with behavioral questions to assess problem-solving abilities.
Technical skillsC++Behavioral questions
Hands-On Experience & Facility Tours
Some candidates reported a structured interview process that included hands-on experiences or facility tours, which required them to analyze design details and demonstrate their technical knowledge in practical settings.
Hands-onFacility tourDesign analysis
Lengthy Process & Communication Delays
The overall interview process can be lengthy, with candidates experiencing significant delays between rounds and a lack of timely communication regarding their status, which can lead to frustration and uncertainty about the outcome.
TimelineCommunicationProcess length
Evaluation & Decision-Making
Candidates felt that the evaluation process involved multiple decision-makers, which could complicate the experience; some reported feeling judged unfairly or not having a fair chance due to the evaluators' lack of technical understanding.
EvaluationDecision-makersFairness
Relocation Expectations
Candidates should be prepared to discuss relocation expectations early in the process, as there may be an expectation to cover relocation costs themselves, which could lead to uncomfortable conversations with recruiters.