J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Silicon Labs (Austin, TX) en mars 2024
Entretien
Very smooth process. Recruiter reached out to me. Offered first interview, very conversational and technical. Advanced to second interview, also conversational and technical. They cared about how I approached the problems. Both were in C. Received offer letter shortly after a mini HR-screen. Very friendly recruiter and interviewers.
Questions d'entretien [1]
Question 1
Asked to fix a basic C method for first interview. Asked to create a basic interrupt method for second interview in C. In both interviews they were extremely conversational. They cared about how you approached the problem and offered advice and help as well. Extremely understanding.
J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Silicon Labs (Boston, MA) en sept. 2022
Entretien
Cold applied, recruiter scheduled 1x60 technical, scheduled another 1x60 technical, then got offer. Very fast process, from technical to decision in <2 weeks. No behavioral-only rounds, and no online assessment. First technical was some discussion about my background, very light behavioral, and mostly conceptual technical questions. There was a snippet of C code that I had to fix (didn't have to compile, was in a google doc) that was riddled with errors. Second interview was a coding problem in C that related to interrupts. Also didn't have to get it running, was just testing my knowledge/communication skills. Some light behavioral sprinkled in. In hindsight, what's funny is that I answered only a decent amount of the questions correctly. Lots of stuff I should've studied beforehand that I didn't.
Questions d'entretien [2]
Question 1
Volatile, const, static keyword meanings in C. When would a variable be const and volatile? How would you debug embedded software without printing to a terminal? What's an ISR? What's interrupt latency?
First coding problem: debug this garbage function doing pointer arithmetic in C. Second coding problem: code up a pretty straightforward state machine. Only needed to understand how interrupts work.