Skip to content
Socket

Technical Enablement Manager

United StatesRemote · United States
Manager · FullTime · Go-to-Market
POSTED 16 OCTVERIFIED 3H AGO
Apply Ask
Pay · posted
$160k–220k
Open for
18d
since 16 Oct
Hiring · 30d
27
−1 net · open roles
Figma

About Us

Socket helps devs and security teams ship faster by cutting out security busywork. Thousands of orgs use Socket to safely find, audit, and manage open source code. Our customers - from Anthropic to xAI, and Figma to Vercel - love Socket (just check out their tweets to see for yourself!)

Founded by Feross Aboukhadijeh, a long-time open source maintainer with software downloaded over a billion times a month, Socket has raised $125M in funding from top angels, operators, and security leaders.

About the Role

Socket is looking for a Technical Enablement Lead to own technical readiness across Customer Engineering: Sales Engineers, Technical Account Managers, Customer Success Managers and Support. You'll start with Sales Engineering, where the need is biggest right now.

You'll be the technical voice of enablement. SEs trust you to know the product well and to find the answer fast when you don't. You'll report to our Head of Enablement, who owns learning design and delivery, and together you'll build the engine that gets new hires ready and keeps everyone current. You'll work closely every day with the Head of Sales Engineering, the SE managers and the other Customer Engineering leaders.

We're hiring fast and shipping product fast. Your job is to turn field gaps into training that scales, starting with getting SEs demo and POC ready, and to keep the team current as new features ship. You'll need to learn the product fast, build fast, and use AI tools to scale yourself so one person can support a team that keeps growing. You'll spend real time in demos, POC reviews and call recordings, and that's where most of your roadmap comes from. You won't start from zero. There's an existing SE onboarding program, an LMS, hands-on labs and a weekly SE training series to build on.

What You'll Do

Onboarding & Certification

Own technical onboarding for new Sales Engineers so they're ready to demo and run POCs as quickly as possible, then build the same for TAMs, CSMs and Support

Build hands-on labs and certification paths, and certify people before they're in front of customers on their own

Work with SE leadership on the demo standard every SE is held to, and train and certify against it

Agree with Customer Engineering leaders what "ready" means for each role, and track ramp against it

Knowledge & Content

Own the Customer Engineering technical knowledge base: audit what exists, retire what's outdated, and keep what stays accurate and self-serve

Build deployment and troubleshooting guides for the hardest setups, starting with Socket Firewall in enterprise networks (proxies, ZTNA, private registries like Artifactory and Nexus)

Own technical competitive material for the tools SEs run into most

Stay Close to the Field

Listen to calls and sit in on POC reviews and escalations to find where people get stuck, and fix it with training

Bring patterns back to Engineering: missing docs, confusing UX, and the questions that keep pulling engineers into deals

Launch Readiness

Work with the engineers shipping each feature so the field is trained before customers see it

Turn each release into field-ready material: a short lab or demo, a talk track, deployment steps and known limitations

Run a regular technical session for SEs and Customer Engineering

What You'll Bring

Required

6+ years in a technical customer-facing or technical enablement role (Sales Engineer, Solutions Engineer, Solutions Architect, TAM, Support Engineer, Technical Enablement, or similar)

You've run demos, POCs, deployments or escalations yourself, not just trained people on them, and you can explain the product to an SE, an AE and an engineer at the right level for each

You've built training other people use without you (labs, demos, certifications, videos, playbooks) and can tell us how you knew it worked

You use AI tools (Claude, Claude Code, or similar) to build and maintain content, and can show how that lets you support a much bigger team than you could alone

Working knowledge of how developers build and ship software: package managers like npm or PyPI, CI/CD, and source control (Git, GitHub, GitLab)

Source · SocketFirst seen 2 NovOriginal ↗