Real, anonymous reports from people who interviewed for Software Engineer at Marvell Technology, newest first and distilled into what to expect across the loop.
Get your personalized Marvell Technology Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My first impression from the hiring process was pretty negative: the interviewers came across like they were hunting for flaws instead of actually evaluating my skills. I felt like the questions were being used to test what they themselves expected to hear, rather than exploring whether I could solve problems well.
Technically, the conversations leaned on my resume experience and the smaller details behind the processes I’d mentioned. I could tell they were trying to gauge how deep my understanding went, and some questions drilled down into specifics that weren’t just surface-level. Overall, the vibe was tense enough that it didn’t feel like a fair exploration of my approach.
2 months ago
Average Positive San Jose, CA
My interview journey started with an HR conversation where the recruiter worked through my experience, education, and other logistics like visa details. After that, I moved into a set of technical rounds that were tied closely to what I’d worked on. The interviewer(s) guided the conversation using my projects as the anchor, which made it feel less like guessing generic topics and more like walking through my own decisions.
On the behavioral side, I was asked questions that probed how I work with others and how I think about collaboration. Then the technical interviews dug into C and object-oriented programming ideas and even pushed into the fundamentals enough that the questions felt like they were designed to check precision, not just whether I’d heard terms before. At times it felt like the round was an assessment of my whole programming foundation, not a single narrow skill.
3 months ago
Average Neutral Santa Clara, CA
My process started with the usual recruiter touchpoint, but once I got into the technical portion it quickly felt less like a narrow interview and mor…
4 months ago
Average Positive Westborough, MA
My process followed a fairly consistent rhythm: an HR/resume screening first, then technical interviews, and a final stage where I ended up speaking b…
4 months ago
Average Positive Santa Clara, CA
My screening began with a short phone call that felt mostly about narrowing the pool. It wasn’t deep, more of a quick shortlist step, and the timeline…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically begins with an HR screening, followed by multiple technical rounds that can include both coding and project discussions. Candidates reported varying timelines, with some experiencing long waits for feedback after interviews.
HR screeningtechnical roundsfeedback delay
Technical Evaluation Focus
Technical interviews often emphasize foundational knowledge in programming, data structures, and specific technologies like C, Verilog, or DSP, with a focus on both theoretical understanding and practical application. Candidates noted that questions can be challenging and require precise answers.
C programmingVerilogdata structures
Behavioral & Collaboration Questions
Behavioral interviews assess candidates' teamwork and collaboration skills, often using project experiences as a basis for discussion. Interviewers seek to understand how candidates approach working with others and their communication style.
teamworkcollaborationproject experience
Presentation Component
Some candidates were required to prepare and deliver a technical presentation, which tested their ability to communicate complex ideas clearly. This stage was noted as both nerve-wracking and crucial for demonstrating understanding and communication skills.
The atmosphere during interviews varied, with some candidates feeling a tense or pressured environment, while others reported friendly and engaging interactions. The energy of interviewers appeared to impact the overall experience.
interview atmosphereengagementpressure
Feedback & Outcome Variability
Candidates experienced inconsistent feedback and outcomes, with some receiving offers quickly while others faced long delays or no offers despite seemingly strong performances. This variability contributed to frustration for some candidates.