LumiraDx Interview Questions
& Process

Had one technical interview with a team member where we did a coding problem (reverse a string) and a couple bitwise questions. Then, two more soft technical interviews with teammates where we talked about a bug I solved, how SPI works, and my favorite project. There were system demos and I got a lot of time to ask questions. Lastly, one soft technical/behavioral interview with the team manager where we really dove into the software development process and philosophy, like what makes good code, how to design, what's important to consider in a design, what makes bad software, scalability, modularity, and diagramming. Total interview time was about 2 calls and maybe 4-6 hours.

First, I had a phone interview. Then, it was a face-to-face interview. The face-to-face part was weird because the main interviewer was on a one-way video call, which was a bit uncomfortable. Two other people were in the room. They briefly showed me the product I'd be working on. They didn't seem very interested in my past experience, sticking to a pre-planned script instead. This was my first interview in 10 years, so maybe this is the norm now. They didn't give me a tour or introduce me to anyone. The interview felt very one-sided, focused on whether I was a good fit for them, with no real effort to sell the company or the role to me. I realized pretty quickly I wasn't interested, so I just treated it as practice. After that, there was a written test. I was given paper and a pen, with 9 questions, and left alone, though I suspect the guy on the video call was still watching. All the questions were in C, even though I've been doing a lot of C# (which was clear from my CV), and I hadn't realized how much I'd forgotten. Mostly, there were 7 questions about pointers, like writing a function or predicting the output of a function. There were also a couple of database questions, like designing a database for a specific scenario. Since I didn't have a computer and had to write code on paper, I couldn't check if it worked, which made it tough. In hindsight, I should have studied more, but I had already decided the job wasn't for me, so I wasn't fully committed. Afterward, the paper was scanned and emailed to the person on the video call, and I had to explain my answers. Then, the HR person in the room asked standard questions like 'explain the project lifecycle,' 'what would your current employer miss about you?,' 'what words would your current colleagues use to describe you?,' 'which career achievement are you most proud of and why?,' 'why are you looking for a new job?,' 'why are you suitable for this job?,' and 'why should we employ you?' That was it, and they said they'd let me know in a couple of days. I never heard back, so I guess I didn't get the job. Honestly, after that experience, I realized my current job isn't so bad.

I interviewed for a Procurement Specialist position and found the process a bit of a letdown, though I liked the company mission. The interview was only 30 minutes and felt really general with just three questions. I was expecting more technical depth for the role, but they didn't specify what they were looking for, so I couldn't show what I can do. They called it a 'professional casual interaction' and said a more in-depth in-person interview would happen, but then they rejected me right after without more interviews. This made me wonder about their hiring process. Even though it didn't go well for me, LumiraDx seems like a good company, and I'd tell future candidates to ask about the technical details they want during interviews.

Had a video call interview with the Process Engineering Manager, a Senior Process Engineer, and the HR Manager. The interview was about 1 hour and 50 minutes long. It included some technical questions and then questions about cultural fit. They mentioned they had about 3 weeks of interviews remaining and I'd likely hear back within that time. I never heard back after 8+ weeks, so I assumed I wasn't selected. I had no contact details for them, and calling the HR department number just rang out. It was pretty disappointing given how long the interview was and the effort I put in.