Senior Technical Account Manager

What You Will Do

• Own the post-sales technical relationship for a portfolio of up to three strategic enterprise accounts. Act as the named technical owner, co-owning each account with the Account Executive (technical vs. commercial domains).
• Run a defined cadence: weekly check-ins, monthly business reviews, quarterly QBRs, and annual roadmap workshops.
• Lead post-incident pattern ownership and technical triage. Drive post-mortems, identify architectural root causes, own remediation roadmaps. Respond within 4 business hours to P1/P2 escalations.
• Drive proactive technical strategy, cost optimization, and architectural guidance including architectural reviews, technical risk mapping, usage optimization, and pre-launch assessments.
• Scope and orchestrate broader Vercel engagements (hand off to Forward Deployed Engineers or Professional Services). Coordinate, track outcomes, and integrate into customer roadmaps. Perform throwaway demos and illustrative POCs.
• Operate as the customer's voice inside Vercel, translating needs into signals for Product, Engineering, and Support. Hold teams accountable via influence and future SLAs.
• Carry primary accountability for annual renewal of the TAM engagement, targeting 90%+ renewal rate, 4.5/5+ CSAT, and 95%+ SLA compliance.

About You

• 5+ years in customer-facing technical roles at a platform, infrastructure, or developer tools company (Technical Account Management, Solutions Architecture, Developer Success Engineering, Customer Support Engineering, Field Engineering, or technical consulting). Experience owning $1M+ ACV customer relationships, running QBRs, workshops, procurement, and renewals.
• Deep production experience with Next.js and the Vercel platform. Must have architected, debugged, and optimized production systems on Vercel, with fluency in App Router internals, ISR and caching strategies, Fluid Compute, AI SDK, and cost-optimization patterns.
• Demonstrated track record of driving complex technical outcomes across organizations without formal authority. Comfortable holding senior stakeholders accountable and escalating when blocked.
• Strong written communication for executive and incident contexts. Able to compress complex technical situations into clear one-page summaries for CTOs.