Real, anonymous reports from people who interviewed for Software Engineer at Molex, newest first and distilled into what to expect across the loop.
I went through a more structured three-step sequence after I was shortlisted: a technical round, then an advanced technical round, followed by an HR conversation. What stood out immediately was that every stage leaned heavily on engineering fundamentals and tied back to my resume. Even when the questions were “technical,” the way I explained my work and the way I approached each problem mattered as much as the answers.
After my resume was shortlisted, the process felt pretty laid-back. I first did a phone screen with a recruiter who kept things conversational rather than sounding like a typical HR script. That call lasted about half an hour and even ran a few minutes long, and I could tell they were genuinely trying to understand my background. They asked behavioral questions and pushed me to give different examples for each situation, so I had to pick specific moments and explain what I learned from them.
The interview process typically consists of a recruiter call, followed by technical evaluations and an HR conversation. The flow is generally organized, with each stage building on the previous one, allowing candidates to showcase their experience and skills progressively.
Candidates can expect a strong emphasis on engineering fundamentals during technical rounds, with questions often tied closely to their resume and past projects. The interviews assess both theoretical knowledge and practical problem-solving skills, often progressing from basic to more complex concepts.
Behavioral interviews are a key component, focusing on candidates' past experiences, achievements, and soft skills. Interviewers look for clear communication, confidence, and cultural fit, often using storytelling techniques to gauge motivation and alignment with company values.
While the interview process is generally respectful and organized, candidates have reported issues with follow-up communication and feedback after interviews. Many experienced delays or a lack of closure, which can lead to frustration and uncertainty about their application status.
The overall difficulty of the interviews is described as average, with a focus on assessing depth rather than trick questions. Candidates should prepare for a thorough evaluation of their technical knowledge and reasoning abilities, but the experience is not typically perceived as overly intense.
Some candidates reported an onsite interview experience that included panel discussions with multiple interviewers. This format can increase the intensity of the evaluation, as candidates must consistently demonstrate their skills and fit across different perspectives.