Content Engineer

Job Description

About Vercel: Vercel gives developers the tools and cloud infrastructure to build, scale, and secure a faster, more personalized web. As the team behind v0, Next.js, and AI SDK, Vercel helps customers like Ramp, Supreme, PayPal, and Under Armour build for the AI-native web. Our mission is to enable the world to ship the best products. That starts with creating a place where everyone can do their best work. Whether you're building on our platform, supporting our customers, or shaping our story: You can just ship things. About the Role: This role has two jobs and you’ll own both. 1) Ship great content. High-quality technical narratives are the baseline. You’ll create work that stands up to scrutiny from senior engineers and executives (including the CTO) as well as seasoned professional writers. The expectation is clarity, accuracy, and grounding in real implementation details, wrapped in tight storytelling. 2) Build the system, agents, and tools that make great content repeatable . We are building the content engine that will define how content is generated in the age of AI. Come build the agents, tooling, workflows, and structure that help our small team ship faster without sacrificing technical credibility or authentic human writing. We’ve got the tokens, and you can help us burn ‘em. You will join a small, high-agency team at the intersection of product, engineering, and go-to-market. We publish for a world where people and AI agents discover, evaluate, and cite information differently than they did in the SEO era. How we work We treat content like an engineering discipline: quality bars, reusable components, and systems that let us iterate quickly. Just like software engineering, the best people have mastered the craft and can do it by hand, but use AI to dramatically increase their throughput. You’ll work in a stack that may include: Claude Code (and other code-first LLM tools) for technical exploration, refactors, example generation, and literally building the agents to coordinate our processes. Shared skills / reusable prompt libraries for consistent drafting patterns and review checklists Context window management : curating inputs, trimming noise, and keeping high-signal working sets Memory + retrieval workflows : building a knowledge layer so we don’t rewrite the same background every time Structured outlines and schemas to make content easier for both humans and agents to navigate and cite If you’ve built systems like this before or you’re excited to, you’ll have a lot of room to shape the approach. Wh

Required Skills