Software Engineer, CDN Content

Vercel · Hybrid - San Francisco · Engineering · listed July 7, 2026

The shape of it

Seniority
Mid level
Experience asked
2+ years
Where
Hybrid
Stated pay
$172,000 – $258,000
Requirements listed
6
Length
838 words

In the posting’s own words

As a Software Engineer on the team, you'll take on well-scoped projects with real production impact and grow into owning larger pieces of the system. The work spans the serving path end to end, and everything ships through careful, progressive rollouts validated with production data. You'll learn how a planet-scale CDN works from engineers who built it.

What it asks for · 6

  • 2+ years of experience building and operating backend services in production.
  • Proficiency in at least one of Go, TypeScript/Node.js, or a comparable systems language, and enthusiasm for working across a polyglot stack.
  • Solid understanding of HTTP and web fundamentals — caching headers, request/response lifecycle, what a proxy does.
  • You write code you're willing to operate: tested, instrumented, and documented.
  • Curious about how large-scale systems work, and motivated to dig into unfamiliar code and production data to figure things out.
  • A collaborative teammate who communicates clearly, asks good questions, and follows through reliably.

Also a plus

  • Have experience with caching systems (CDNs, Redis/Memcached, application-level caches) at any scale.
  • Have AWS experience, particularly S3 or ElastiCache.
  • Have used Next.js or another modern web framework and understand rendering modes like SSR/SSG/ISR.
  • Have experience with observability tooling (Datadog, Honeycomb, or similar).
  • Have experience with Terraform or Kubernetes.

What the job covers

  • Build and improve the services behind ISR, PPR, and image optimization — working in Go, Lua, and TypeScript across the serving path.
  • Execute well-defined projects independently, from implementation through safe rollout (feature flags, shadow modes, progressive deployment) and post-ship validation.
  • Monitor and maintain your work in production: build dashboards, add metrics and alerts, and develop ownership of what you ship.
  • Contribute to the team's observability and testing surface — the dashboards, logs views, and e2e test suites that keep a high-change system trustworthy.
  • Participate in the on-call rotation with support from senior engineers, and contribute to incident follow-ups that make the system more resilient.
  • Collaborate with teammates and partner teams (Next.js, CI/CD) through design discussions, code review, and pairing.

Tools and skills named

Cloud & infra
  • Observability2×
  • AWS
  • CI/CD
  • Datadog
  • Distributed systems
  • Kubernetes
  • Redis
  • Terraform
Languages
  • JavaScript4×
  • Go2×
  • TypeScript2×
Frameworks
  • Next.js3×
  • Node.js2×
Ways of working
  • Code review
  • On-call
  • Testing
Operations & finance
  • Recruiting

Words the posting leans on

  • systems7×
  • production6×
  • caching5×
  • cdn5×
  • experience5×
  • serving4×
  • caches3×
  • code3×
  • content3×
  • engineers3×
  • next.js3×
  • rollouts3×
  • services3×
  • ship3×
  • build2×
  • careful2×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Vercel

every open role at Vercel

How this page was made

An automated read of a public job posting, fetched August 24, 2026 and last changed by Vercel on August 18, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.