Marvell Technology Analog / Mixed Signal Engineer Interview Questions
& Process

I had a one-on-one interview with an engineer. It was about an hour long and included some quick behavior questions, questions about my classwork, a question about a previous project, and a question about a basic circuit.

The interview for the Analog IC Design Engineer position was really good and informative. The interviewers knew their stuff and asked a lot of technical questions and practical problems. It started with me talking about my background and why I want to do analog IC design, which was a good way to start. Then came the technical part, which was tough but fair. They asked hard questions about circuit design, transistors, noise, and frequency response. I liked that they asked deep questions that showed they really know the field and want to find the best person. They also focused on practical stuff, asking me how I'd handle real design problems, which shows they care about real-world application.

I'm sharing my experience interviewing with Marvell Switzerland last year, initiated through a friend's referral. Despite it not leading to an offer, partly due to my situation, it was a valuable experience. It began with a call from a director and an HR person to discuss salary and assess general responses. Next was an on-site visit, including a morning tour with the manager. I inquired about long-term plans and received a vague answer about future developments. Then, the main interviews, five in total, spanned most of the day. With about 10 years of experience in RF IC design, I noted that while my academic background involved circuit calculations from 15 years ago, my current strength lies in practical problem-solving and RF/analog design, not rote memorization of textbook equations. I advise anyone seeking a job there, especially if you truly need one, to prepare thoroughly with textbook questions, as Marvell Switzerland seems to place significant importance on them. Don't expect your CV to be a primary focus; they might start with a textbook question, like defining MOSFET mismatch or discussing L vs. W for better matching. The initial recruiter was strict, unwilling to elaborate or offer help with unclear questions, making the process feel arduous. Subsequent recruiters were more flexible but still focused on textbook material. I managed to answer most questions correctly, even when unsure of the exact prompt, like deriving the input impedance of a common-emitter amplifier. I used the small-signal model, derived the equation, and explained its behavior at different frequencies. This process might have suggested I wasn't deeply expert, as it took time. Notably, out of the six people I spoke with, only two introduced themselves properly – the manager and the final recruiter. Others immediately launched into technical questions about PLL or LDO design without preamble. The engineers did little to make me feel comfortable. Technically, they made a good impression. I acknowledge I didn't prepare adequately. The experience was eye-opening, prompting me to dedicate daily time to 'trivial' questions and to improve. I've even considered how to counter such interviewers by creating a shareable resource of common interview questions and answers.