Just finished the Vercel onsite and the behavioral portion was more substantive than I expected from a company their size. Writing this up because most Vercel interview threads focus on the technical rounds and skip the behavioral entirely.
I had two behavioral-focused conversations across my loop. One with an EM and one with a cross-functional partner (design/product side). Both lasted about 45 minutes.
Themes they kept coming back to.
Autonomy and ownership. Almost every question had some version of "how did you decide" or "who did you involve" underneath it. They wanted to see that I could push something forward without waiting for permission but also that I knew when to bring others in. Classic senior-level stuff but they pushed deeper than most companies.
Writing and async communication. They asked how I document decisions and how I write for different audiences. This makes sense for a remote-first company. I gave examples of architecture decision records I'd written and they were genuinely interested in the format.
How I handle constraint. One question was basically: tell me about a time you had strong technical conviction but had to ship something simpler. They wanted to see whether I could make peace with pragmatic tradeoffs or whether I'd be the person who blocks a launch to get perfect.
Feedback culture. Not "tell me about a time you gave hard feedback" in the abstract but specifically: how do you calibrate when to give feedback vs. let something go? That nuance felt real.
Values signals. Vercel talks publicly about being product-obsessed and shipping fast. In the behavioral rounds that showed up as skepticism toward any answer where my instinct was to run a long process or build internal consensus. They seemed to like moves that were quick, customer-visible, and reversible.
I came from a large enterprise company and had to consciously reframe some of my stories to not sound like I needed 6 months to do anything. Worth thinking about if you're coming from a similar background.