CoreWeave logo

CoreWeave Software Engineer Interview Questions
& Process

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

Based on 12 interview experiences · FREE TO READ

3.9 Rounds average
Average Typical difficulty
58.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at CoreWeave.

Showing 3 of 12
CoreWeave logo
CoreWeave

Software Engineer

Engineering · nearly a year ago

Senior Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Recruiter call
Interview formats
Behavioral Technical

I had an initial chat with the recruiter, who could only schedule it for 3 weeks out. After talking with them, I was set up for a technical interview, which was scheduled for 2 weeks later. On the day of the interview, the meeting invite disappeared. I emailed them and after 3 days of waiting, I got an auto-reject. The same recruiter contacted me again 2 months later about the same job. I took their call, explained what happened last time, and asked to just proceed to the next stage. They got really aggressive with me and told me to explain the role and everything we talked about in detail. I pulled out my notes and a list of all the things we discussed last time. They got a bit angry and asked a few questions, and then the interview concluded. The recruiter clearly had an ego issue.

Confirmed questions1 question
  • What's your reason for leaving your present employer, and what motivates you to join CoreWeave?
CoreWeave logo
CoreWeave

Software Engineer

Engineering · nearly a year ago

Entry Difficult Negative experience No offer 4 rounds
Interview process
Phone screen Technical screen Onsite
Interview formats
System Design Technical Behavioral

The interview process involved 2 phone screens, followed by a manager round and a system design interview, and a final random q&a session. The overall experience felt unprofessional because they frequently rescheduled and had different interviewers throughout. It seemed like they weren't serious about hiring, as they kept messing up the schedule.

Confirmed questions1 question
  • Could you design a system that ingests events from various clients, ranging from hardware to APIs, and enables other clients to subscribe to these events? The design needs to accommodate future changes without requiring a complete redesign.
CoreWeave logo
CoreWeave

Software Engineer

Engineering · more than a year ago

Mid Difficult Positive experience Accept offer 5 rounds
Interview process
Recruiter call Onsite Technical screen Onsite Onsite
Interview formats
Behavioral Behavioral Coding Technical Behavioral

The process had a 30 minute recruiter screen, then a 90 minute culture fit interview with a director, followed by a 60 minute coding assessment on CoderPad, then a 60 minute domain knowledge interview with a senior SWE, and finished with a 45 minute interview with the hiring manager. It was all as expected from the interview packet, which also gave descriptions of what to expect and how to prepare. Everyone was professional, kind, knowledgeable, and proactive. The questions checked my domain knowledge, technical depth, and cultural fit. I think it'll be a good place to work if you like owning your project's technical direction and being in an engineering-focused culture.

Confirmed questions3 questions
  • What is your interest in CoreWeave?
  • Describe what you are seeking in a company.
  • What conditions would lead to your happiness in your upcoming position?

CoreWeave Software Engineer Interview Questions

Quoted word for word from CoreWeave interview reports.

Could you design a Kubernetes-based platform that lets users upload their application runtimes and scales automatically based on load?

Read reports

Were there questions about GPU Optimization asked multiple times?

Read reports

Could you design a system that ingests events from various clients, ranging from hardware to APIs, and enables other clients to subscribe to these events? The design needs to accommodate future changes without requiring a complete redesign.

Read report

Can you design a notification system and detail the design steps according to the requirements?

Read report

Can you explain how to implement concurrency and threading in code, including scenarios for their use?

Read report

Formats, difficulty and experience

Across all 12 CoreWeave interview reports.

Interview formats

Behavioral 34.3%
Technical 28.6%
Coding 22.9%
System Design 11.4%
Presentation 2.9%

Interview difficulty

Easy 8.3%
Average 50%
Difficult 41.7%

Candidate experience

Negative 41.7%
Positive 58.3%