Software Engineer, CDN Content

The role

The CDN Content group handles delivery of every asset flowing through the company's worldwide edge network, from static files to incrementally regenerated pages. The role sits where infrastructure meets product, with frequent collaboration alongside frameworks like Next.js to run framework-defined infrastructure on the platform. Performance and cost experienced by developers depend heavily on caching decisions made here, using a multi-tier cache stack spanning process memory, regional services, and object storage in more than twenty regions.

What you would do

• Construct and refine the services powering incremental static regeneration, partial prerendering, and image transformation, using Go, Lua and TypeScript.
• Own well-scoped projects end to end, releasing changes gradually behind flags, shadow traffic, and staged deployments, then verifying results afterward.
• Build dashboards, metrics, and alerting for your changes in production and take responsibility for their health.
• Improve observability and test coverage, including dashboards, log tooling, and end-to-end suites, for a system that changes constantly.
• Take a turn in the on-call schedule with senior engineer backup and help drive follow-up work after incidents.
• Work with teammates and partner groups such as Next.js and CI/CD through design reviews, code reviews, and pair programming.

What they asked for

• Two or more years running backend services that serve real production traffic.
• Working fluency in Go, TypeScript/Node.js, or another systems-oriented language, and willingness to work across several languages.
• Grounded knowledge of HTTP, including caching headers, request lifecycles, and how proxies behave.
• Writes code that is maintainable in production: tested, instrumented, and documented.
• Strong curiosity about large systems, comfortable digging through unfamiliar code and telemetry to find answers.
• Communicates clearly, asks sharp questions, and reliably closes out commitments.

Nice to have

• Hands-on time with caching layers such as CDNs, Redis, Memcached, or in-app caches, at any scale.
• AWS familiarity, especially S3 or ElastiCache.
• Experience building with a contemporary frontend framework and an understanding of how SSR, SSG, and ISR differ.
• Used observability platforms such as Datadog or Honeycomb.
• Infrastructure-as-code experience with Terraform or container orchestration with Kubernetes.