Real, anonymous reports from people who interviewed for Embedded Engineer at Lutron Electronics, newest first and distilled into what to expect across the loop.
After applying online, I got an email to schedule an interview with a senior employee. The conversation started with some general talk about the company before it quickly turned technical. I ended up working in a live-notepad style website rather than an IDE, and the interviewer would have me paste and run code to see whether it worked. A lot of the questions leaned toward object-oriented concepts plus pointer manipulation, which was a little uncomfortable for me since I was more of a hardware-focused programmer.
My process had three rounds, with the last two running for about two hours each. The interview flow was very much about embedded fundamentals mixed with simple-to-middling technical problems that felt close to what they actually build. Early on, I was given a set of classic light-and-switch questions, including the three lightbulbs / three switches riddle about figuring out which switch controlled which bulb.
The interview process typically consists of multiple rounds, starting with a technical phone screen followed by longer onsite interviews that may include both technical and behavioral components. Candidates should expect a structured flow with a mix of embedded fundamentals and problem-solving tasks.
Candidates should prepare for a strong emphasis on technical skills, particularly in C programming, pointers, and embedded systems concepts, with questions often involving real-world scenarios like light switch problems and memory management.
Expect to encounter logic-based problems and practical coding tasks that assess your reasoning and debugging skills, often in a live coding format where you explain your thought process as you work through problems.
While the interviews are primarily technical, some rounds may include behavioral questions to assess cultural fit and communication skills, especially in later stages of the process.
Candidates should be aware that GPA may be treated as a hard requirement, and discrepancies can lead to abrupt cancellations of later interview stages, regardless of performance in earlier rounds.
The overall difficulty of the interviews can vary, but many candidates report feeling a high technical bar from the start, which can create a challenging atmosphere; reflections often indicate a disconnect between performance and outcomes.