Developer Success Engineer AgentMail · San Francisco, CA Full-time · Remote — 59 minutes ago

Emploive; San Francisco (CA); Hybrid; USD 120,000 - 180,000; Full time

Job summary

AgentMail is hiring a Developer Success Engineer in San Francisco with remote flexibility. You will own developer support, debug API requests and integrations, reproduce issues, and determine if problems stem from bugs, docs gaps, or usage errors.

You’ll work to resolve most issues independently, isolate problems with precise repros, and surface patterns to improve the product. You should enjoy diagnosing technical problems, reading API docs, and communicating clearly with developers to help

Qualifications

• 2–6 years of experience in technical support or developer-facing roles.
• Ability to read API docs, inspect requests/responses, and reproduce issues.
• Capacity to distinguish bugs, expected behavior, and incorrect API usage.
• Ability to write code to investigate issues and ship small fixes.
• Clear, concise communication with developers.

Responsibilities

• Own technical support for developers building with AgentMail.
• Debug API requests, webhooks, product issues, and integrations.
• Reproduce issues and classify as bug, expected behavior, or doc gap.
• Resolve most issues independently without extra engineering.
• Provide high-quality reproduction or fix issues via PR.
• Surface recurring questions and friction to the team.
• Identify inconsistencies across API, docs, and DX.
• Join calls with developers for async debugging.
• Write precise responses that show understanding of the problem.

Skills

Technical support

Developer experience

API-first product

Clear communication

Debugging code

Investigative mindset

Job description

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.

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.