CoreWeave·Software Engineer·Technical Phone Screen
May 2026
Technical screen for an Observability Engineer role at CoreWeave, focused almost entirely on building a web crawler in Go. The whole session orbited error handling and concurrency, which makes sense for infra work but I wasn't expecting them to go this deep on a single problem.
- Design a web crawler in Go that starts from seed URLs, fetches pages, extracts links, and crawls recursively. How do you structure it end to end?
- How do you handle error cases in the crawler: network failures, non-2xx HTTP responses, malformed HTML, redirects, timeouts, and partial reads?
- Worker pool versus unbounded goroutines: which concurrency model do you use for the crawler and why?
- How do you implement retry logic with backoff for transient network errors without hammering a server or stalling the crawler?
- How do you handle panics inside goroutines so the whole crawler doesn't crash?
- How do you use context cancellation to stop the crawler gracefully, and how do errors propagate without killing the whole process?
“I jumped straight to the happy path, which was a mistake.” The rest of the author's notes on Software Engineer interview at CoreWeave, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post