Vercel provides AI-native cloud infrastructure and developer tools—including v0, Next.js, and the AI Cloud—that let developers and enterprises build, secure, and scale intelligent web applications.
<div class="content-intro"><h2>About Vercel:</h2> <p><span data-sheets-root="1">Vercel is the agentic infrastructure company. We free people and agents to ship what’s next.</span></p> <p><span data-sheets-root="1">For more than a decade, Vercel has shaped how the web is built. As the team behind Next.js, v0, and AI SDK, we create products that help builders move from idea to production with speed, security, and exceptional developer experience.</span></p> <p><span data-sheets-root="1">Now, software is entering a new era, and the next generation of products will not just be used by people. They will be built, extended, and operated by agents.</span></p> <p><span data-sheets-root="1">We are building the platform for that future, trusted by companies like <strong>OpenAI, PayPal, Ramp, Supreme, and millions of developers worldwide</strong>. Whether you’re building our products, supporting our customers, growing our community, or shaping our story, you’ll help define what comes next.</span></p></div><h2>About the role</h2> <p>Vercel builds and maintains a broad portfolio of open source projects that power the modern web, running in millions of applications. Your primary focus will be <strong>Turborepo, Nuxt, Svelte/SvelteKit, SWR, Workflow, and Nitro</strong>. A single structural fix at the framework level protects every one of those applications at once, which makes this one of the highest-leverage security roles at the company.</p> <p>We're looking for a security engineer who loves finding a whole class of vulnerability and eliminating it in one move, not someone who's satisfied filing one bug at a time. You'll run deep security assessments of framework internals (routing, middleware, caching, server actions, the build pipeline), find the systemic patterns that produce entire families of bugs, and drive the framework-level fixes and design changes that remove them permanently. You'll also own how these projects handle externally reported vulnerabilities, coordinated disclosure, and CVEs, working directly with maintainers and the open source security community. This includes hands-on ownership of Vercel's open source bug bounty program for these projects: triaging incoming reports, validating and reproducing findings, and driving fixes with the right maintainers.</p> <h2>What you will do</h2> <ul> <li><strong>Hunt for vulnerability classes, not individual bugs:</strong> Run deep security assessments of framework internals (routing, middleware, caching, data fetching, server actions/RSC boundaries, build tooling) to find the systemic design patterns that produce whole families of issues.</li> <li><strong>Drive root-cause framework fixes:</strong> Push design changes upstream that eliminate a category of vulnerability across every application built on the framework, rather than patching individual instances as they're reported.</li> <li><strong>Own vulnerability disclosure and CVEs:</strong> Triage security reports from the community and researchers across Turborepo, Nuxt, Svelte/SvelteKit, SWR, Workflow, Nitro, and other maintained OSS projects. Coordinate embargoed fixes, write and publish advisories, and manage the CVE/CNA process end to end.</li> <li><strong>Run the OSS bug bounty program for these projects:</strong> Own triage and validation of incoming reports to Vercel's open source bug bounty program for Turborepo, Nuxt, Svelte/SvelteKit, SWR, Workflow, and Nitro. Reproduce findings, assess severity, and coordinate fixes with the right maintainers and researchers.</li> <li><strong>Get security into design early:</strong> Partner with framework maintainers and core teams during RFCs and design review, so new features ship with security considered from the first draft, not bolted on after a report comes in.</li> <li><strong>Build preventive tooling:</strong> Contribute linters, codemods, and CI checks that catch regressions of previously-fixed vulnerability classes before they land again.</li> <li><strong>Own supply chain security for these projects:</strong> Harden how dependencies, releases, and published packages for Turborepo, Nuxt, Svelte/SvelteKit, SWR, Workflow, and Nitro are built, signed, and distributed. As more contributions and dependency updates are generated or assisted by AI agents, build the review and provenance practices that keep that increased volume safe.</li> <li><strong>Work with the community, not around it:</strong> Engage directly with maintainers, contributors, and external researchers as peers. Bring pragmatic security recommendations to project discussions in a way that respects how these projects actually get built, and represent Vercel in coordinated disclosure norms and working groups when an issue spans multiple ecosystems.</li> </ul> <h2>About you</h2> <ul> <li><strong>You've actually used or broken these frameworks:</strong> You've built real things with Turborepo, Nuxt, Svelte/SvelteKit, SWR, Workflow, or Nitro (or closely comparable projects), or you've found and reported security issues in them. This is a hard requirement, not a nice-to-have: we need someone who understands what these projects actually do and how they're actually used, not a generalist parachuting in.</li> <li><strong>You have a deep appreciation and respect for open source work:</strong> You understand that these are community projects with maintainers, contributors, and users who care deeply about them, and you treat that with the seriousness it deserves. You're not here to slow the project down with process for its own sake.</li> <li><strong>4+ years in security engineering,</strong> ideally with real hands-on open source contribution experience. You've actually sent PRs to projects like these, not just filed issues against them.</li> <li><strong>You're energized by root cause, not remediation count:</strong> Finding the one design flaw that kills fifty potential bugs is more satisfying to you than closing fifty tickets one at a time.</li> <li><strong>You can read framework i