Lam Research Software Engineer Interview Questions
& Process

We started with a recruiter call to discuss if the role and my previous experience were a good fit and to go over the salary range. Then, there was a technical interview that lasted over 30 minutes. This technical interview involved discussing a past project, specifically a frontend part of an enterprise project I had worked on. It also included a coding exercise on an online transpiler using Angular.

This was the second stage of the interview process. The first stage was a call with a recruiting agency, and they seemed more knowledgeable. This interview was the actual one with the company, but the interviewer didn't seem very prepared. He asked a bunch of questions, and I got most of them right, only missing one. That was the end of the line for me. I guess not many people develop with Plotly, so finding me seemed like a good match. Things went south when I mentioned saving my company $50K by using the free version of some software instead of the licensed one. If I hadn't been honest, I probably would have gotten the job offer.

First, recruiters will check out your background, projects, and skills. Then, you'll do an online coding test on a platform with a time limit, focusing on data structures and algorithms. After that, there's a technical phone or video call where you'll code live and talk about your experience. The next step is the on-site or virtual loop, which has several interviews back-to-back. These will involve algorithm and problem-solving questions, a system design deep-dive if you're mid/senior, and a behavioral chat about culture fit. Finally, we'll discuss the offer, including pay, benefits, team fit, and start date. Then it's on to onboarding prep, like paperwork and getting set up before Day One.