Vercel Innovation & Technology Culture

Vercel gives engineers the autonomy and infrastructure to move quickly from idea to production. With a culture built around shipping, fast feedback and low-friction execution, employees can see their work reach users without waiting on unnecessary layers of process.

“The ‘you can just ship things’ slogan is real. New commits can be deployed in a matter of minutes.”

Vercel is building an AI-forward go-to-market organization that applies emerging technology across the customer journey. By bringing together functional expertise, data science and GTM engineering, teams are exploring new ways to create smarter, faster and more effective customer experiences.

“Vercel is like a 99th percentile AI company, and one of the things I’m passionate about is bringing AI to bear on everything that we’re doing in go-to-market to really build a unique AI-forward experience.”
 

What new technologies or frameworks are helping your teams move faster and build smarter?

One of the ironies I’ve found in the current moment of agentic programming is I can get away with using so much less and accomplishing a lot more. Selecting the right tools, languages and infrastructure used to be a heavy, upfront cognitive tax. Every new project meant hand-rolling boilerplate: test environments, CI/CD, deployment pipelines, infra config which are all necessary, but none of it is the actual idea.

At Vercel, that tax is mostly gone. Our engineers give agents authenticated access to Vercel and GitHub and the agents start spinning up environments, deploying on demand, provisioning temporary infrastructure, writing their own integration tests to prove the work is correct, often without being asked. That autonomy is bounded by the same security model we use for human teams, so agents can move quickly while staying inside the guardrails. The result is I can focus on the core research behind my ideas and guide the agents on implementation, knowing that the agent will create the necessary feedback loops to prove its success.

How do you balance experimentation with reliability in your development process?

The honest answer is now 90 percent of my development process is experimentation, not a phase before the “real” work starts. There used to be a nagging pull to ship something just because I’d already spent the time building it. That pull is gone. I don’t hesitate to try an implementation or an API design because it’s so easy, in terms of time, to try it again in a different way.

That loop, build, evaluate, discard if it’s not right, is what lets me judge the result honestly instead of feeling obligated to defend a path just because time went into it. Reliability isn’t something I bolt on after experimentation; it’s the output of running that loop enough times that only the strongest version survives.

That’s the standard we hold ourselves to — fast iteration isn’t in tension with reliability, it’s how we get there.

What role does collaboration play in turning innovative ideas into products? 

As implementation gets cheaper, expertise stops being the bottleneck for who gets to contribute. We no longer need to lean as heavily on the one person who happens to have deep technical knowledge in a given area. Instead, we can collaborate at a broader layer, with people who may not know how to build something technically complex but know exactly how it should work for a customer, a workflow, or a team. So we let the best idea win, regardless of where it comes from.

For example, Eve, our new open-source agent framework, is designed so building an agent is about defining what it does, not standing up the infrastructure around it. We’re seeing people outside of traditional engineering roles come together to build and ship internal agents.

Overall, fewer gates and more surface area for good ideas to reach production, no matter who they come from.