Real, anonymous reports from people who interviewed for Software Engineer at Itw Performance Polymers, newest first and distilled into what to expect across the loop.
I started with a recruiter call that was quick and mostly about fit. The director joined as well, and the vibe was less about deep technical evaluation and more about whether I matched what they wanted and whether the job aligned with what I was looking for. After that, they booked me for a plant tour and an in-person interview with their chief chemist.
I started with a short recruiter call over Microsoft Teams that mainly went over the Standard Products team—what the role would cover and walking through my resume. The meeting felt about 30 minutes, but I left concerned because the recruiter didn’t seem to understand the engineering side of the responsibilities. When I asked about projects and how the team was structured, I didn’t get clear, concrete answers; instead, I got pushback that I was unprepared and didn’t fully understand the vague job description.
The initial recruiter call often focuses on fit and logistics rather than deep technical evaluation, with some candidates reporting a lack of technical understanding from the recruiter. Be prepared to discuss your resume and clarify any questions about the role's responsibilities.
Candidates can expect a technical interview that emphasizes practical skills and past projects, particularly in languages like C++ and tools like Docker. Be ready to discuss your technical strengths and specific experiences in detail.
Behavioral questions are integrated into the interview process, focusing on how candidates have handled specific situations in their past work. Use the STAR method to prepare clear examples that demonstrate your problem-solving and teamwork skills.
The interview process may include multiple rounds, often starting with a pre-screen call followed by technical discussions and possibly a panel interview or job shadowing. Be prepared for a longer day with various interview formats and participants.
Candidates have reported delays and unclear communication during the selection process, with some experiencing frustration over waiting for decisions. Stay proactive in following up, but be prepared for potential delays.
The overall difficulty of the interviews is described as manageable but requiring clarity and depth in responses. Candidates should be ready for a mix of straightforward and challenging questions that assess both technical and behavioral competencies.