About the role
You'll own the deliverability surface of Saleshandy's product. That's the layer that decides whether a customer's cold email actually lands in the inbox or not. It sits between our sending infrastructure (the engineers operating MTAs, which are the server systems that actually send the email, plus IP pools and warmup systems) and our customers (sales teams who don't want to think about SPF records but care a lot about reply rates). Your job is to translate one to the other and ship the product surface that makes deliverability legible and actionable for them.
This is a product role, not an engineering role. You'll partner with the deliverability engineering pod, but you won't be writing the code that sends the email. You will be the person who can read a raw SMTP transaction, diagnose why a campaign tanked, and turn that diagnosis into a feature.
The hardest part of this role is the depth gap. Deliverability is one of the most technical product domains in SaaS, and customers will ask questions that 80% of PMs can't answer. You need to be the 20%.
Typical candidates have 2-4 years of experience in a technical product, infrastructure, or deliverability-adjacent role. We hire on demonstrated technical fluency, not tenure or degree.
What you'll do
- Own the deliverability product roadmap: inbox-placement testing, domain warmup, blacklist monitoring, SPF/DKIM/DMARC setup wizards, sender-reputation dashboards, and the diagnostic tools customers use when something goes wrong.
- Read the data yourself. Pull Google Postmaster Tools and Microsoft SNDS feeds, read DMARC aggregate reports, debug a failing SMTP handshake from log lines.
- Run a weekly user-research loop with heavy senders and the customer-success deliverability specialists. Turn the patterns you hear into shipped product changes.
- Sit in the room when there's a deliverability incident (an IP pool gets a complaint spike, a domain ends up on a major DNSBL, a mailbox provider tightens a filter). Co-