Developer Success Engineer
At AgentMail · San Francisco; San Francisco, California, United States
- Engineering
- Full-time
See how well you match Match me reads your CV and picks the jobs that suit you best.
Get jobs like this within hours Radar emails you new jobs open to you within hours of us finding them, before most people see them.
Where you can work from
Open to the United States
“San Francisco”
From the location.
“San Francisco, California, United States”
From the job board field.
“Location: San Francisco / Remote Okay”
From the job description.
Report a mistake
- Posted
- 12 October 2026
- First seen by us
- 4 November 2026
- Last checked
- 23 hours ago
Job description
From AgentMail’s job post, as they wrote it.
Location: San Francisco / Remote Okay
AgentMail gives AI agents their own email inboxes. We’re looking for a Developer Success Engineer to own the front line between developers using AgentMail and the team building it.
This isn’t a role where success means closing as many tickets as possible. We want someone who can solve technical problems independently, understand what a developer is actually trying to do, and recognize when the same problem keeps showing up.
Read the full description
Your job is to answer the question, figure out why it had to be asked, and make sure we learn from it.
What you’ll do
* Own technical support for developers building with AgentMail.
* Debug API requests, webhooks, product issues, and integrations.
* Reproduce issues and determine whether something is expected behavior, developer error, a documentation gap, or a product bug.
* Resolve the large majority of issues independently without needing to pull in another engineer.
* When something is broken, isolate the problem and give engineering a high-quality reproduction - or open a PR and fix it yourself.
* Notice recurring questions and friction across support conversations and surface those patterns to the team.
* Identify inconsistencies and confusing behavior across our API, documentation, and developer experience.
* Jump on calls with developers when async debugging isn’t enough.
* Write concise, technically precise responses that make developers feel like they’re talking to someone who actually understands their problem.
You will be a fit if
* You have 2-6 years of experience in technical support, developer experience, solutions engineering, or engineering, ideally working with a developer-facing or API-first product.
* You’re comfortable reading API documentation, inspecting requests and responses, working with logs, and reproducing technical issues.
* You can distinguish between a bug, expected behavior, and incorrect API usage without immediately escalating to engineering.
* You can write code to investigate issues and ship small fixes.
* You’re an unusually clear and concise communicator.
* You’re resourceful. When you don’t know the answer, your instinct is to investigate rather than hand the problem to someone else.
* You have strong interpersonal instincts and genuinely care about understanding why a customer is frustrated or confused.
* You notice patterns. Answering the same question for the fifth time makes you want to fix the underlying problem.
What this role isn’t
This isn’t traditional customer success or account management. You won’t spend your day running check-in calls or forwarding technical questions to engineers.
You’ll be expected to understand the product deeply enough to investigate most problems yourself - and to turn what you learn from customers into signal for the people building AgentMail.
Developer Success EngineerAgentMail
Apply on AgentMail (opens in a new tab)Get jobs like this by email
Once a week, we email the new remote jobs open where you live, each with the line that proves it. Every email has a one-click unsubscribe.