Rambus logo

Rambus Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 43 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
69% Positive experience

Which role are you interviewing for?

18 roles · 43 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Rambus.

Showing 4 of 43
Rambus logo
Rambus

Digital Marketing Specialist

Marketing · more than a year ago

Mid Average Positive experience No offer 4 rounds
Interview process
Phone screen Onsite Onsite Phone screen
Interview formats
Behavioral Behavioral Behavioral Behavioral

The interview process began with a quick phone screening. This was followed by an in-person interview at the Rotterdam office with three interviewers. Next, I had an interview with the VP in person, and then spoke with the US leadership of the department via Skype. The final step was another follow-up interview over the phone with leadership. The whole process was very fast and efficient. Everyone was really nice and professional, genuinely interested in understanding my experience and how I think. The final decision took a while to hear back about because of holidays, but overall it was a good experience.

Confirmed questions1 question
  • What makes you want to work for Rambus?
Rambus logo
Rambus

Validation Engineer

Engineering

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Onsite Panel Background check Offer
Interview formats
Technical Behavioral

I got a call from HR regarding the electrical validation position. Two weeks later, I had a telephonic round. A week after that, I was called for a face-to-face round, which went well, but I didn't hear back. After three weeks, I called for an update and was told I wasn't selected. Three days later, HR called back saying she received incorrect feedback and that a Skype call with people from the US was being arranged, asking me to prepare. I got hopeful and attended it, and it also went well. Then, no response from the team after the interview. I tried multiple times for the result, and after two weeks of dragging, they informed me I was 'not selected.' This whole process took almost two months. I felt I did well in the interviews, so I waited/wasted time for the result. There was poor communication from HR and the team, which is discouraging and degrading for an applicant; it makes things difficult for someone in need.

Confirmed questions4 questions
  • Can you describe the Serdes characterization process for both transmit (TX) and receive (Rx)?
  • How is Parbert used and what are its applications?
  • What are the various types of jitter and what are the methods to measure them?
Rambus logo
Rambus

IT Support Engineer

Operations

Entry Difficult Neutral experience No offer 2 rounds
Interview process
Recruiter call Onsite Background check
Interview formats
Behavioral

I think the recruiter messed up my chances for an offer. They initially said it was a direct hire role, but then I found out I had to be a contractor, which they weren't upfront about. They were unclear about the job specifics from the start, even though they're apparently a preferred vendor for Rambus. The office itself was nice, and the employees seemed pleasant. They offered good benefits, free food, and drinks. After the interview, I talked to my recruiter, and after that, I heard nothing back – no calls, no emails, and they didn't respond to mine. I ended up emailing the hiring manager to find out what happened.

Confirmed questions1 question
  • Can you describe what a successful day looks like for you at work?
Rambus logo
Rambus

Embedded Software Engineer

Engineering

Mid Average Negative experience No offer 7 rounds
Interview process
Recruiter call Phone screen Take home Onsite Phone screen Background check Offer
Interview formats
Behavioral Technical Coding

So the interview process started off pretty standard, with an HR phone screen and then a hiring manager phone interview. After that, I had a take-home coding test, which wasn't too bad, took me about an hour and a half because I was being extra careful. They said I did great on that and flew me out to San Francisco for an onsite. The onsite involved a mix of technical interviews, mostly whiteboard coding, and some general background questions. Most of the coding problems were pretty straightforward, though one near the end tripped me up a bit. I flew home after that. The next day, the hiring manager emailed me, saying the team liked me but one person who missed the onsite wanted to chat over the phone. I had that interview the day after and it seemed to go well. Then, the day after that, they emailed saying the team was happy and wanted to move forward, asking for references. I sent those over (2 previous managers, 1 lead). A few days later, I heard from my references that they'd been contacted. I figured the offer was next, but four days later, they called to say they were passing. I initially worried it was a reference issue, so I checked with them, and they confirmed they'd given good feedback. The hiring manager and HR reached out again within a couple of days to assure me it wasn't the references, but something about the 'hiring process.' They apologized, saying I was a 'victim of the process,' and that the team's assessment inexplicably went from 'very good' to 'don't hire him' during reference checks, which seemed odd. They seemed sincere, but the whole thing still doesn't quite make sense to me.

Confirmed questions1 question
  • Could you identify the top 3 results within a significantly large list?

Rambus Interview Questions

Quoted word for word from Rambus interview reports.

Solve the two sum problem: find pairs in an array that equal the target.

Read reports

Can you explain the cause of offset voltage due to threshold voltage mismatch in differential pair transistors?

Read reports

What's the difference between combinational and sequential circuits?

Read reports

What are the various types of jitter and what are the methods to measure them?

Read report

Could you write Verilog code to determine the clock frequency?

Read report

Could you explain the difference between a latch and a DFF?

Read report

Suppose you have a black box with a voltage source inside, and you can only measure the resistance connected to it. How would you determine the voltage and current?

Read report

Formats, difficulty and experience

Across all 43 Rambus interview reports.

Interview formats

Technical 44.2%
Behavioral 38.4%
Coding 16.3%
Group 1.2%

Interview difficulty

Easy 25.6%
Average 53.5%
Difficult 20.9%

Candidate experience

Neutral 14.3%
Positive 69%
Negative 16.7%

Reports by job function

Engineering 35
Other 2
Design 1
Finance 1
Marketing 1
HR 1