Developer Success Engineer

• 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.

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., * 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., 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.