How I’d prep for SpaceX’s Sr. Software Engineer, CDN (Starlink) role in 30 days
Updated Nov 15, 2026
The job
Sr. Software Engineer, CDN (Starlink), SpaceX
Palo Alto, CA (also posted in Redmond, WA and Hawthorne, CA) · $200,000 – $280,000 base, plus equity · Posted Nov 12, 2026
View the posting →What this team actually does
Starlink is building its own CDN. A CDN is a network of servers that keep copies of videos and websites close to users, so they load fast. The posting says the team will design, build and scale a new Content Delivery Network for Starlink (10M+ users), build the systems that shape traffic across multiple CDNs, build the tooling, visibility and alerting around it, and write algorithms that make the best use of hardware and keep costs down.
Why Starlink needs one: a 2-year study of Starlink traffic (Bose et al., arXiv 2510.13710) found that a user’s traffic often leaves the Starlink network at a ground station far from where they live. Their DNS lookups get answered from far away too, so CDNs send them to a server in the wrong region. That pushed some latencies beyond 200 ms. When Starlink added ground stations closer to users in early 2025, median page loads got 60% faster. A CDN that Starlink controls is the next step.
There’s also a Principal version of this role at $255,000 – $340,000 base.
| Area | What to know |
|---|---|
| Language | Rust (the posting says C, C++ or Rust; the team says Rust) |
| Networking | DNS, caching, load balancing, SSL/TLS, edge networking, layers 0–7 |
| Traffic | Traffic steering between CDNs, DDoS protection, traffic control |
| Operations | Monitoring, alerting, visibility |
| Nice to have | Network topology, graph theory, numerical and convex optimization |
How I found the stack (do this for any job)
- Read the posting closely. It lists C, C++ or Rust, plus DNS, caching, load balancing, TLS and DDoS protection. It never says which language or which part matters most.
- Check the team’s older postings. The same team has been hiring “Software Engineer, CDN (Starlink)” since July with the exact same description. So this is one team, and it’s growing.
- Find the team on LinkedIn. I searched Google for
site:linkedin.com/in SpaceX Starlink "CDN"and read what the team posts. One senior engineer posted that they’re building a brand-new CDN in Rust. A principal engineer posted that they’re mostly hiring for DNS / Steering and DDoS / Traffic control.
So: Rust, DNS, traffic steering and DDoS. That’s where I’d spend the 30 days.
See a CDN in action first
Before any studying, spend 30 minutes watching a real CDN work from your own laptop:
- Run
dig netflix.comanddig youtube.com. Note the IP addresses you get back, then run the same commands from a friend’s network or a phone hotspot. Different answers mean DNS is steering you to a different server. - Run
curl -sI https://www.cloudflare.comand look at thecf-rayheader. The three letters at the end are the airport code of the Cloudflare data center that served you. - Run
curl -o /dev/null -s -w "dns %{time_namelookup} connect %{time_connect} tls %{time_appconnect} first byte %{time_starttransfer}\n" https://www.youtube.com. That splits one page load into DNS, TCP, TLS and the server’s response time. Each one is a part of the posting. - If you know someone with Starlink, run the same commands on their connection and compare.
You’ll understand everything below much better once you’ve seen these numbers yourself.
System design questions
- Design a CDN for a satellite internet provider. Where do the caches go: ground stations, the satellites, or partner CDNs?
- Design a DNS-based traffic steering system across two CDNs. How fast can it react, and how do you make it react faster?
- A user’s DNS resolver is 2,000 km away from them. How do you still send them to the right edge?
- A new episode of a hit show drops and everyone requests it at once. How do you stop all the edges from hitting the origin at the same time?
- Design DDoS protection for the edge: what happens at layers 3/4 vs layer 7?
- How do you decide what to cache when edge disk is small and expensive?
Concepts they’ll probe
- What happens when you type a URL: DNS, TCP, TLS, HTTP, and how many round trips each one costs.
- DNS: recursive vs authoritative servers, TTLs, anycast, EDNS Client Subnet.
- Caching: Cache-Control, TTLs, invalidation, LRU vs LFU, cache hit ratio.
- Consistent hashing, and request coalescing (one origin fetch for many identical misses).
- Load balancing at layer 4 vs layer 7.
- TLS handshakes and session resumption, and why they hurt more on high-latency links.
- DDoS: SYN floods, SYN cookies, token buckets, and why anycast helps absorb attacks.
- Rust: ownership and borrowing,
ArcandMutex, async with Tokio, and why Cloudflare picked Rust over C for Pingora.
Unlock the rest
- The week-by-week 30-day plan, with daily practice on Devmaxx
- The exact book chapters and docs for each week
- The project: a mini CDN in Rust with Pingora edges, a DNS server, traffic steering and a rate limiter
- The senior bar: the stories to prepare
- The resource list with every link
Get the full guide, free
Enter your email and the guide opens right here. You’ll also get the occasional Devmaxx email. Unsubscribe anytime.