Production Engineer applicants have rated the interview process at CoreWeave with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 49.2% positive. This is according to Glassdoor user ratings.
Common stages of the interview process at CoreWeave as a Production Engineer according to 2 Glassdoor interviews include:
Phone interview: 33%
One on one interview: 33%
Skills test: 33%
Here are the most commonly searched roles for interview reports -
I applied through college or university. I interviewed at CoreWeave in Feb 2026
Interview
First was a recruiter Screen, tech/coding screen (Python), a manager interview, then two technical interviews. The last three were an hour long each.
The last two technical interviews were about system design and incident management.
After the last technical interviews, there was radio silence. I followed up with the recruiter but received nothing. The recruiter also did not show up to the first screening call we had. I got a survey request for the interview process about a month afterwards, so I assume I was rejected. Very unprofessional.
Interview questions [1]
Question 1
The python screen was basically asking how to use the requests module to make POST requests.
HR round, then coding round, then a handful of panel interviews that include behavioral, systems design, incident management. Gauging to see how you think Not a bad process. Nothing too bad or crazy
The interview process started with a recruiter call, followed by a hiring manager conversation, and then a coding round. I didn’t get past the coding stage. From what I understand, there were probably a couple more rounds after that.
The coding interview was on CoderPad and began with two pages of instructions you’re expected to read and absorb upfront. The task involved installing packages, starting a server, interacting with an API through request/response, and fixing a bug. Pretty standard stuff, but the setup felt unnecessarily long-winded for a timed session.
I got the code working and answered the follow-up questions. Still, it seemed that asking for a bit of clarification — even on parts buried in the instructions — worked against me. There wasn’t much room for discussion or collaboration; it felt more like a test of how well you could skim and execute under pressure rather than a fair assessment of real-world skills.
Overall, the process didn’t leave a strong impression. It felt more like checking boxes than evaluating practical ability in a balanced way.
Interview questions [1]
Question 1
Python Coder pad questions, see description for details