Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Agentmail

Developer Success Engineer

  • Seen live on Agentmail's site today
  • Mid level
  • Remote
Pay
Not stated
Location
San Francisco
Open for
12+ days
First seen
Oct 23, 2026
Apply on Agentmail's site (opens in a new tab)

Posting record

No flags

Open 12+ days

The posting's record, oldest first
  1. Agentmail's site dates the posting
  2. Ghostless first sees this listing
  3. Last checked: still up
How we know

It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.

Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Agentmail, so its true age is longer.

Last checked Nov 4, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What it asks of you

2–6 years of experience
“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 pro” (quoted from the posting)

What the posting discloses

Not stated: Pay, real vacancy, AI screening.

Why these three

Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the role

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.

Something wrong with this posting?