Vercel

Vercel sits at an interesting intersection: infrastructure company, developer tools company, and design-forward product company all at once. They build the platform that a huge portion of the modern web runs on, and they care deeply about how it feels to build on it. That combination — technical depth plus genuine obsession with developer experience — shapes who they hire.

The team has grown significantly as they've scaled into enterprise, but the culture has stayed close to its roots: fast, opinionated, and genuinely in love with the web platform.

Who they're hiring

Vercel is investing heavily in enterprise go-to-market, which means sales, customer success, and solutions engineering roles are active alongside the engineering and product roles. They're also building out their AI product portfolio — v0, AI SDK, and the infrastructure to support AI-heavy workloads at the edge.

On the engineering side, the work spans a wide range: Next.js core, edge runtime, build infrastructure, observability, storage. For product and design roles, the focus is on developer-facing experiences — the kind of work where the customer is someone who will immediately know if something is slightly off.

The process

The shape varies by function, but expect:

1. Recruiter screen — background and interest, straightforward
2. Hiring manager or team lead conversation — role fit, technical direction
3. Technical or work exercise — role-dependent, more below
4. Cross-functional interviews — 2-4 rounds with team members
5. Final / leadership round for senior roles

Vercel moves at a reasonable pace for a company their size. The process isn't unusually long, and they're direct about where you stand.

What they actually care about

Developer empathy. This is the core filter at Vercel. They're building tools for developers, and the people who build those tools need to understand what it feels like to use them. Not in an abstract sense — in the "I have spent a meaningful part of my career writing code that other people's tools made easier or harder" sense. If you've thought seriously about DX, API design, or developer workflows, that's more relevant here than at most companies.

Care about the web platform. Vercel is a company that has strong opinions about how the web should work — performance, edge computing, React server components, the future of rendering. You don't need to agree with all of it, but you should have genuine views. In interviews, people who've thought about these tradeoffs — even critically — tend to resonate more than people who are neutral.

Ability to work at the intersection of infra and product. A lot of Vercel's hardest problems live at the boundary between deep infrastructure work and visible user-facing experience. Engineers who can hold both concerns at once — who care about cold start times AND whether the dashboard that surfaces those metrics is intuitive — are the people who thrive here.

Speed and ownership. Vercel ships fast. The product surface area is large and the team is lean relative to the scope of the work. People who wait for complete specs, who need extensive process to feel comfortable, or who aren't comfortable owning a problem end-to-end will struggle. People who treat ambiguity as space to move tend to do well.

The technical bar

For core engineering roles — Next.js, edge runtime, build systems — it's high. The work is legitimately hard. Build infrastructure at scale, runtime environments, caching strategies, real-time systems. Strong fundamentals are assumed; experience with the specific domain matters.

For product and solutions engineering roles, the bar is more about depth of understanding of the developer ecosystem. You should be comfortable in code, understand how frontend frameworks work under the hood, and be able to talk credibly with engineering teams at sophisticated companies.

For GTM roles (enterprise sales, customer success), Vercel is increasingly hiring people with experience selling to or supporting developers specifically. Generic SaaS sales experience is less valuable than experience navigating a developer-led buying process.

Things worth knowing

Guillermo Rauch is deeply involved in product direction. The CEO's fingerprints are on the product in a visible way. Strong opinions about the web, about design, about performance. In interviews, knowing what Vercel's current bets are — and having views on them — matters more than at a company where the CEO is more distant from the product.

The enterprise motion is newer than the developer motion. Vercel built its reputation with individual developers and small teams. Enterprise sales is a more recent chapter. If you're joining for a GTM role, you're building something, not joining something fully built.

Remote-friendly but not fully distributed. Some concentration in San Francisco, but the team is spread out. Strong async communication skills matter.

Should you apply?

If you care about the web, believe performance and developer experience are worth optimizing seriously, and want to work on infrastructure that touches a meaningful chunk of the internet — Vercel is worth pursuing. The work is technically interesting, the product sensibility is strong, and the company is at an inflection point between developer tool and enterprise platform.