Developer Success Engineer

OpenKrill; United States; Hybrid; USD 120,000 - 180,000; Full time

Job summary

OpenKrill is seeking a Developer Success Engineer to bridge developers using AgentMail with our engineering team. You’ll own frontline support, debug APIs and webhooks, and reproduce issues to help us learn from every question.

We value engineers who can read API docs, inspect requests, and distinguish bugs from expected behavior. You’ll often work independently, sometimes on calls, and craft concise, technically precise responses.

Qualifications

• 2–6 years in technical support or developer-focused roles.
• Experience reading API docs and debugging API requests.
• Ability to distinguish bug vs. expected behavior.

Responsibilities

• Own technical support for developers using AgentMail.
• Debug API requests, webhooks, product issues, and integrations.
• Reproduce issues and classify them as bug, doc gap, or user error.
• Resolve most issues independently without another engineer.
• Provide high-quality reproductions or fixes when needed.
• Identify recurring questions and surface patterns to the team.
• Highlight inconsistencies in API, docs, and DX.
• Join calls with developers for async debugging.
• Write clear, concise responses showing deep understanding.

Skills

API experience

Technical support

Developer experience

Solutions engineering

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.