Real, anonymous reports from people who interviewed for Software Engineer at Lutron Electronics, newest first and distilled into what to expect across the loop.
I interviewed for the Software Engineer role with a very OOP/classes-and-undo style coding focus, and the difficulty hovered around average.
I interviewed for the Software Engineer role and went through a short, code-and-schedule-app style process that felt light-to-average overall.
Candidates can expect a strong emphasis on object-oriented programming (OOP) concepts and foundational electronics knowledge, often including coding tasks that require building classes or understanding circuit fundamentals.
Interviews often include scenario-based questions that assess decision-making in real-world contexts, alongside behavioral questions that evaluate communication and fit with company values.
Some interview paths incorporate hands-on assessments or engineering-style questions that require practical problem-solving skills, including disassembly tasks or applied engineering scenarios.
The interview process can vary significantly in structure and clarity, with some candidates reporting poor communication and scheduling issues that can lead to a frustrating experience.
Candidates may experience a high level of intensity during technical evaluations, with some interviews feeling unforgiving and focused heavily on technical depth under pressure.
Feedback can be inconsistent, with some candidates receiving little to no information post-interview, and outcomes often leaning towards rejection despite seemingly adequate performance.
