Deepgram

Partner Success Engineer

Remote Customer Success role with clear candidate location fit.

PostedApr 24, 2026

Eligible countries1 accepted country

Seniority signalOpen level

Work settingRemote

Accepted candidate locations

USA

Python TypeScript

Role overview

Partner Success Engineer

Requirements and responsibilities

Readable role content extracted into sections for faster review.

What You’ll Do

Serve as the technical advisor and strategic owner for a portfolio of strategic partners, engaging everyone from developers to CIOs and CTOs.
Own the full partner lifecycle: onboarding, adoption, technical enablement, expansion, and advocacy.
Drive joint adoption through live demos, workshops, architecture guidance, troubleshooting, and best-practice recommendations — making Deepgram successful inside the partner’s environment.
Run discovery continuously: surface partner problems, understand their business impact, and translate them into actionable requirements for product and engineering.
Identify and scope expansion (cross-sell, upsell, multi-product, co-sell) in partnership with Sales, and lead executive business reviews and joint planning sessions.
Act as the voice of the partner internally — influencing roadmap, GTM strategy, and the tools we build to support partners.
Track adoption, usage, health, and expansion to drive outcomes; travel to partner sites as needed.
Operate AI-first by default, and build tools, agents, and workflows that eliminate recurring work for you and the broader team. Your impact is measured by the leverage you create, not just the partners you serve.

What We’re Looking For

Significant experience in technical, customer-facing roles — TAM, sales/solutions engineering, partner or enterprise CS with a strong technical focus, implementation, or support — at API-driven, developer-first, or AI companies. For most people that’s roughly 7+ years, but we care more about the shape of your experience than the exact number.
A track record that blends partner or customer ownership with technical depth: solution design, hands-on troubleshooting, and commercial growth.
Hands-on experience running demos, POCs, or technical workshops with enterprise partners or customers — leading them, not just attending.
Demonstrated success identifying and landing expansion in complex enterprise or partner accounts.
Fluency discussing APIs, integrations, and developer workflows, and troubleshooting L1-style issues (no coding required, but genuinely conversant — not hand-waving).
A strong understanding of partner ecosystems and channel business models — resale, referral, integrations, co-marketing, co-selling — and multi-party commercial dynamics.
Experience engaging both technical stakeholders (developers, architects) and executive buyers (CIO, CTO, VP Engineering).
Exceptional communication, influence, and relationship-building — concise and structured, across technical and business audiences.
Something you’ve built — a tool, agent, script, or workflow — that permanently eliminated recurring work. In your application, tell us what it was, what it replaced, and what it’s still doing today.
An AI-native operating model: specific workflows that structurally depend on AI, and a clear account of how you’d rebuild them if those tools disappeared tomorrow.

Nice to haves

Experience in machine learning, voice AI, cloud infrastructure, or developer-first technologies.
Telephony / CCaaS / CPaaS background (e.g., Twilio, Genesys) — maps directly to our partner ecosystem.
A background spanning solutions engineering, TAM, or L1 support alongside CS or partner responsibilities.
Familiarity with channel/partner marketing, enablement programs, or technical enablement asset creation.
Working fluency with automation, scripting, or agent-building (Python, TypeScript, workflow tools, agent frameworks, or equivalent). You don’t need to be a software engineer — just dangerous enough to ship working systems.

Similar roles