Razer logo

Razer Software Engineer Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
73.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Razer.

Showing 3 of 15
Razer logo
Razer

Software Engineer Intern

Engineering · half a year ago

Intern Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

It was pretty relaxed overall. The people interviewing me were nice and seemed genuinely interested in my resume. Pretty much the whole interview was spent digging into my past experience and internship and how it relates to what this job entails.

Confirmed questions1 question
  • Tell me about yourself and elaborate on your resume and previous internship.
Razer logo
Razer

Software Engineer

Engineering · a year ago

Mid Easy Positive experience Decline offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Technical Coding Behavioral

The interview process was straightforward. I spoke with three engineers and one manager, and they asked a lot of C++ questions. It wasn't too hard for me because I have solid experience in the field. I got a job offer in the end, but I decided not to accept it.

Confirmed questions5 questions
  • Could you tell me about your experience with compilers?
  • What do you know about linkers?
  • Can you explain pointer arithmetic?
Razer logo
Razer

Software Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Phone screen Technical screen Onsite
Interview formats
Technical Coding

The initial phone screens went fine. Then there was a 5-hour in-person interview. The interviewers were pleasant. I had to write code for a couple of problems, which I think I did okay on. However, on one coding problem, I misunderstood an available operation, which made it impossible to solve correctly. The interviewer didn't mention I could have used that operation, and without it, the problem was unsolvable. The other problem involved a math trick that they expected me to figure out on the spot. I tried my best and was close to a solution but ran out of time to code it. After not getting the right answers, the hiring manager, who I was supposed to meet, came in and claimed there was a 'Production Emergency!' and had me escorted out. This was clearly a fabrication. I followed up with the recruiter, but they never replied. Given their dishonesty during the interview process, I can only assume their employee treatment would be similar. Thus, I'm glad I didn't get an offer.

Confirmed questions1 question
  • For an input array of integers, like [1, 2, -3, 1], determine if a sub-sequence exists that sums to zero, and return the start and end indices for each such range (e.g., [1, 2, -3] or [2, -3, 1]). Is there a solution with a time complexity better than O(n^2)?

Razer Software Engineer Interview Questions

Quoted word for word from Razer interview reports.

For an input array of integers, like [1, 2, -3, 1], determine if a sub-sequence exists that sums to zero, and return the start and end indices for each such range (e.g., [1, 2, -3] or [2, -3, 1]). Is there a solution with a time complexity better than O(n^2)?

Read reports

How would you go about transferring a large binary file?

Read report

What are some basic concepts related to threads and services?

Read report

Formats, difficulty and experience

Across all 15 Razer interview reports.

Interview formats

Behavioral 38.7%
Technical 38.7%
Coding 16.1%
Other 3.2%
System Design 3.2%

Interview difficulty

Easy 26.7%
Average 53.3%
Difficult 20%

Candidate experience

Positive 73.3%
Neutral 20%
Negative 6.7%