Oh hey, Lutron! I interviewed there coming out of college, some 10 years ago. I think I drove down from Rochester, iirc. Of all the places I interviewed at t

Oh hey, Lutron! I interviewed there coming out of college, some 10 years ago. I think I drove down from Rochester, iirc. Of all the places I interviewed at the time, it's one of the only ones where I remember a specific interviewing session because it was somewhat unique: The interview sat across from me and role-played a customer calling to complain about a vague issue happening in their home. I then had to roleplay asking the customer and various internal teams (all played by the interviewer) questions, forming hypotheses, running imaginary tests (the interviewer would tell me the outcome), and so on. I started from "The lights in this room don't work right", then clarified and trouble-shot through to the underlying issue, and finally to a root cause. At the time it seemed super weird, but looking back on it years later, it was a clear exercise in troubleshooting skill - something that remains invaluable in engineering. It's one of the only times before or since that I can recall being tested on that specifically, even though it comes up all the time in my day-to-day job. From what you describe, this challenges sounds like that was emblematic of the culture there. :)