AgentMail Verified
Real Estate Tech (PropTech), Email Marketing, SaaS
Developer Support Engineer
RemoteRemoteFull Time$100,000–$140,000 /yrPosted 1 month agoHidden Gem · YC Startup
Required skills
- API requests
- webhooks
- integrations
- logs
- reproducing technical issues
- writing code
- shipping fixes
- concise responses
- documentation gaps
- investigate issues
Nice to have
- developer experience
- API-first product
- solutions engineering
Role summary
AgentMail is seeking a Developer Support Engineer to be the primary technical contact for developers using their AI agent email platform. This role focuses on solving technical problems independently, understanding developer needs, and identifying recurring issues. Responsibilities include debugging API requests, webhooks, and product issues, reproducing bugs, writing clear technical responses, and surfacing patterns to the engineering team. The ideal candidate has 2-6 years of experience in technical support, developer experience, or engineering, with strong debugging, coding, and communication skills.
AgentMail gives AI agents their own email inboxes. We’re looking for a Developer Support 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.
\
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.
