CoreWeave interview, decoded.

Updated · Sources at the end

CoreWeave tests engineers on the kind of work it does: running very large fleets of GPU machines. Candidates report coding problems such as safely rebooting a batch of machines or writing a client for an HTTP API, usually in Go or Python, and system design questions about schedulers, monitoring and machine pools. Puzzle-style problems are rare in the reports. Candidates describe four to six interviews over three to five weeks, and every engineering posting says the job needs access to U.S. export-controlled information.

CoreWeave rents out GPU computing to AI labs, startups and large companies. It went public on Nasdaq in March 2025, bought Weights & Biases in May 2025, and reported $5.1 billion of revenue for 2025 with a backlog of $66.8 billion. It had 2,189 employees at the end of 2025, most of them in the United States.

Free · 2 minutes · no account

The questions for your exact CoreWeave role and level.

See the questions CoreWeave asks ↓Run a free mock interview →

Interviewing at CoreWeave? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who CoreWeave hires

This guide follows the software engineer and site reliability engineer paths, from mid-level to senior. Most engineering roles are listed in Livingston (New Jersey), New York, Sunnyvale, San Francisco and Bellevue, with a small number in London. Postings ask for strong Python or Go, Kubernetes at production scale and a working knowledge of networked systems and GPU infrastructure.

02

What is the CoreWeave interview process?

CoreWeave does not publish its interview process. The shape below comes from candidate accounts and prep sites that collect them, and is marked as reported. The company's own job postings supply the pay ranges, the export-control rule and what each team asks for. Accounts differ in the number of rounds, and one candidate describes an extra coding round added after what they were told was the final interview.

01
Recruiter screen
About 30 minutes, video or phone

Your background, why CoreWeave, and logistics such as location. This is also where the export-control requirement comes up: every engineering posting asks that you be a U.S. person or eligible for the required U.S. export authorization.

02
Coding screen
About 60 minutes, reported in Go or Python

A practical problem rather than a puzzle. Reported examples include rebooting a batch of machines safely and a small HTTP server with a query endpoint. One senior candidate reports the coding round was in Go only and centred on concurrency.

03
Hiring manager call
30 to 60 minutes, reported

Your past work and how it fits the team. Some accounts place this before the final loop, some within it.

04
Final loop
3 to 5 video interviews, reported

More practical coding, a system design round set in CoreWeave's world (machine fleets, schedulers, monitoring), and a behavioural conversation. Senior infrastructure roles may add a Linux or networking deep dive.

05
Offer
No interview

Candidates report the whole process taking three to five weeks, and one account describes eight weeks and more than six rounds.

03

CoreWeave's practical coding rounds

What is reported and how to prepare

The coding rounds are where CoreWeave differs from most big tech loops. Candidates report problems taken from running infrastructure, often in Go or Python, and very few puzzle-style algorithm questions. The reported set is small and consistent, so the best preparation is building small, correct tools quickly.

  • Machine fleet problems: Practise batch operations with limits: rebooting, draining, marking machines offline. Say out loud what happens when a step fails or a machine never returns, because that is where these questions go.
  • HTTP APIs and JSON: Be fluent with an HTTP client, token authentication, pagination, retries and parsing JSON in your language. Reported problems include migrating records from a legacy API to a new one and making the job resumable.
  • Concurrency: In Go, practise goroutines, channels, worker pools and context cancellation. In Python, practise a bounded thread or async pool. One senior candidate reports the whole round was about concurrency.
  • Working code over clever code: Get a correct, readable version running first, then improve it. State the cost of your approach as you go.

These details come from candidate accounts and prep sites, not from CoreWeave. The exact problems change, but the reported ones all come from the same world of machines and APIs.

04

What CoreWeave screens for

Every CoreWeave posting lists five core values, and the reported behavioural questions lean on two of them: owning problems and working through conflict.

  • Be Curious at Your Core
  • Act Like an Owner: reported interviews ask about incidents you owned and decisions that protected a customer
  • Empower Employees
  • Deliver Best-in-Class Client Experiences
  • Achieve More Together: one candidate describes a strong focus on how you resolve conflicts with managers and teammates
05

CoreWeave interview questions

Candidate-reported themes

Candidates have reported a small, consistent set of problems, all practical and all about infrastructure. The practice questions below follow those reports.

Behavioural & motivation

  • How do you handle conflicts with managers and team members?Listening forA real conflict · How you handled it · The outcome
  • Tell me about an incident you owned from detection to fix.Listening forA clear timeline · The hard decision · What changed after
  • Why CoreWeave, and why this team?Listening forSpecificity · Connection · Research

Technical

  • Practice: write a tool that reboots a list of machines in batches, never taking down more than 10% of a pool at once, and handles machines that never come back.Safe batch operations on a fleetReported in the coding screen and as an SRE design questionListening forConcurrency limits · Drain before reboot · Failure handling
  • Practice: call a REST API that lists machines as JSON, find the ones with failed health checks, and mark them offline through a second endpoint. Make it safe to run twice.HTTP API clientsReported: querying machines and marking them offline, migrating records between APIsListening forParse and filter · Retries and errors · Safe to rerun
  • Practice: in Go, fetch data for 500 IDs from a slow service with at most 20 requests in flight, collect the results, and stop cleanly on the first fatal error.Concurrency in GoOne senior account: the coding round was in Go only and about concurrencyListening forBounded workers · Safe collection · Clean shutdown
  • Practice: design a service that places training jobs on GPU machines across a data centre, knowing some GPUs are linked by fast interconnects and others are not.System design for a GPU cloudReported: a website monitoring service, batch reboots, job schedulingListening forRequirements first · Topology-aware placement · Failures

These are the reported themes — your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level.

Predict my CoreWeave questions →
06

Pay

Senior software engineer · posted base, Sunnyvale / Bellevue$182K–$242K
Software engineer · Levels.fyi median, US$320K
Software engineer · Levels.fyi median, SF Bay Area$392K

CoreWeave posts a base salary range on every US job ad; the $182,000 to $242,000 range above is from a senior software engineer posting in Sunnyvale and Bellevue (read 29 September 2026). Levels.fyi's totals include stock and bonus and were read from its listing summary on 29 September 2026: a US median of $320K, $392K in the San Francisco Bay Area and $261K in New York. Since the March 2025 listing, stock is public-company stock. Calibrd benchmarks an offer against your level and location in the report.

07

How to prepare for a CoreWeave interview

  1. Check the export-control clause first. Every engineering posting requires that you be a U.S. person or eligible for a U.S. export authorization; raise it with the recruiter on the first call if it applies to you.
  2. Practise small infrastructure tools against a clock: batch operations on machines, an HTTP client with retries, a bounded worker pool.
  3. If you work in Go, be solid on goroutines, channels, locks and context cancellation.
  4. Prepare a system design answer set in a GPU cloud: scheduling jobs on scarce hardware, monitoring a fleet, handling machines that fail.
  5. Have two stories ready: an incident you owned and a conflict you worked through with a manager or teammate.
  6. Plan for three to five weeks, and ask the recruiter up front how many rounds remain.

This guide covers CoreWeave's engineering and research hiring. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Together AI, Crusoe or Harvey? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run a CoreWeave mock: spoken answers, coached on the spot. Your first mock is free.

Run a CoreWeave mock →
08

FAQ & sources

What is CoreWeave's interview process?

CoreWeave does not publish its interview process. The stages, in order: Recruiter screen; Coding screen; Hiring manager call; Final loop; Offer.

What does CoreWeave look for in candidates?

Every CoreWeave posting lists five core values, and the reported behavioural questions lean on two of them: owning problems and working through conflict. Be Curious at Your Core; Act Like an Owner; Empower Employees; Deliver Best-in-Class Client Experiences.

What questions does CoreWeave ask in interviews?

Candidates have reported a small, consistent set of problems, all practical and all about infrastructure. Technical themes: Safe batch operations on a fleet; HTTP API clients; Concurrency in Go; System design for a GPU cloud.

What coding questions does CoreWeave ask?

The coding rounds are where CoreWeave differs from most big tech loops. Candidates report problems taken from running infrastructure, often in Go or Python, and very few puzzle-style algorithm questions. Covered on this page: Machine fleet problems; HTTP APIs and JSON; Concurrency; Working code over clever code.

How do I prepare for a CoreWeave interview?

Check the export-control clause first. Every engineering posting requires that you be a U.S. person or eligible for a U.S. export authorization; raise it with the recruiter on the first call if it applies to you. Practise small infrastructure tools against a clock: batch operations on machines, an HTTP client with retries, a bounded worker pool.

Prep for a real CoreWeave role

Practise your CoreWeave interview, out loud.

Paste a real CoreWeave posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the CoreWeave prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

CoreWeave Interview Process: Coding, Infra, Pay — Calibrd