I started with a recruiter conversation, and shortly after that I had a technical screen with an engineer where the flow felt very execution-heavy. The centerpiece was a HackerRank-style assessment, followed by an implementation discussion. During that implementation portion, the interviewer gave very little feedback, and I had to push through while I was trying to write and reason in real time.
What threw me off most was the interviewer’s behavior while I was coding—he was effectively messing around in my editor while I was typing, which introduced distractions and extra mistakes on my side. I also remember a specific frustration around language choice: I was told to solve in any language, but the interviewer became extremely dissatisfied that I didn’t use the other option I had discussed, and even more so that I didn’t pick Python.
5 months ago
Average Negative India
My process began with a recruiter call where the questions stayed fairly general—my background, the kinds of tech stacks I’d worked with, and my experience. Later the conversation shifted to compensation. They asked about my current remuneration from my organization, and I paused because I wasn’t sure about any NDA restrictions around salary disclosure.
When I pushed back with that, I also tried to reframe the question by asking what compensation band the role was aligned to. The recruiter’s response was essentially that they couldn’t proceed without current comp information, and the process stopped immediately.
5 months ago
I went through Roku for a Senior Software Engineer (Backend) role, and the biggest takeaway from the whole thing was how unpredictable it felt. Up unt…
6 months ago
Average Positive United Kingdom
I started with a recruiter call where we covered what the role was about. A short time later I moved into two technical rounds: one with a manager bas…
6 months ago
Easy Negative United States
I talked with the recruiter first, and then I met the hiring manager. That interview went really well, and I got invited into what sounded like a full…
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
Recruiter Interaction
The initial recruiter call often covers general background and compensation expectations, but candidates have reported rigid responses regarding current salary disclosures, which can lead to immediate rejections without further evaluation of technical skills.
Recruiter callCompensationRigid process
Technical Assessment Format
Candidates typically face a HackerRank-style coding challenge, often focusing on LeetCode-style problems, which can feel more like a filtering mechanism rather than a true assessment of job-relevant skills, leading to frustration if expectations aren't aligned.
HackerRankLeetCodeTechnical assessment
Interview Structure and Flow
The interview process can be unpredictable, with varying levels of organization and communication, leading to confusion about the format and pacing of interviews, which may affect candidates' ability to prepare adequately.
UnpredictableInterview structureCommunication
Technical Rounds and Topics
Candidates often experience multiple technical rounds covering algorithms, system design, and domain-specific knowledge, but the breadth and depth of topics can vary significantly, leaving some feeling unprepared or misaligned with the role's requirements.
Technical roundsAlgorithmsSystem design
Interview Environment and Pressure
The interview environment can be stressful, with some candidates reporting distractions during coding segments and a lack of supportive feedback, which can hinder performance and lead to a negative overall experience.
Interview pressureDistractionsFeedback
Follow-Up and Communication
Many candidates express dissatisfaction with the follow-up process, citing poor communication and lack of transparency regarding next steps, which can leave them feeling undervalued and frustrated after the interviews.