SlipstreamJobsFresh Startup & VC-Backed Jobs

Developer Success Engineer

AgentMail - San Francisco, CA, USA - Hybrid - posted 2026-10-12

Apply on the company site

SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.

AgentMail is building infrastructure that gives AI agents their own email inboxes. We're seeking a Developer Success Engineer to serve as the primary technical support contact for developers integrating with our platform. This role bridges developers and the engineering team. Success is not measured by ticket volume, but by solving problems independently, understanding developer intent, and identifying systemic issues that recur across support conversations. Key Responsibilities: - Own technical support for developers building with AgentMail's API and platform - Debug API requests, webhooks, product issues, and integrations - Reproduce issues and classify them as expected behavior, developer error, documentation gaps, or product bugs - Resolve the majority of issues independently without escalation - When bugs are found, provide high-quality reproductions to engineering or submit PRs to fix them directly - Identify recurring questions and friction patterns across support interactions and surface them to the team - Spot inconsistencies and confusing behavior in the API, documentation, and developer experience - Conduct calls with developers when asynchronous debugging is insufficient - Write clear, technically precise responses that demonstrate genuine understanding of developer problems This is not a traditional customer success or account management role. You will not spend your day on check-in calls or forwarding technical questions to engineers. Instead, you'll develop deep product knowledge, investigate most problems yourself, and translate customer learnings into actionable signals for the product team. Requirements: - 2–6 years of experience in technical support, developer experience, solutions engineering, or engineering, ideally with a developer-facing or API-first product - Comfortable reading API documentation, inspecting requests/responses, working with logs, and reproducing technical issues - Ability to distinguish between bugs, expected behavior, and incorrect API usage without immediate escalation - Capable of writing code to investigate issues and shipping small fixes - Unusually clear and concise communicator - Resourceful problem-solver who investigates rather than immediately escalates - Strong interpersonal instincts and genuine empathy for frustrated or confused customers - Pattern recognition: motivated to fix underlying problems when the same question recurs

Similar roles