1. What the Role Actually Is
A Vercel Solutions Engineer (SE) / Solutions Architect spans pre-sales and post-sales. From the actual job description:
"In pre-sales, you qualify technical fit, design future-state architectures, run evaluations, and demonstrate how Vercel unlocks measurable business outcomes. Post-sales, you act as a technical quarterback, helping customers successfully adopt and standardize on Vercel."
What you actually do day-to-day
| Activity | Description |
|---|---|
| Technical discovery | Talk to a prospect's engineering team, understand their stack, find the pain (slow builds, bad Core Web Vitals, no preview deployments, scaling issues) |
| Architecture design | Design target architectures — which rendering strategy, which compute tier, how headless CMS integrates, where the edge sits |
| Live demos | Deploy something in real time. Show Preview Deployments, show ISR revalidation, show AI streaming with the AI SDK |
| Code audits | Review a customer's Next.js codebase. Find anti-patterns, wrong rendering strategy, cache misses, oversized bundles |
| Migration planning | Help a team move from Create React App → Next.js App Router, or from Gatsby → Next.js + ISR |
| POC/eval support | Run a 30-day evaluation, build a reference implementation, get the engineering team to say yes |
| Post-sales architecture | Guide onboarding, build reference implementations, run workshops, pair program with their engineers |
| Voice of Customer | Feed customer pain and feature requests back to Vercel's Product and Engineering teams |
The key duality
You must be equally comfortable:
- Talking business outcomes with a VP of Engineering or CTO ("This improves your LCP by 40%, which Google's data shows increases conversion 2–3% per 100ms improvement")
- Talking implementation details with a senior developer ("You should use
unstable_cachehere instead of thefetchcache, and here's why the ISR stampede was happening")