# Delivered — Gustavo Stein, Technical Account Executive candidate at Resend

> A job application built as a small product. It's a browser-only email posture checker for any domain (MX, SPF, DKIM, DMARC, BIMI, MTA-STS over DNS-over-HTTPS), a résumé written as a DNS zone file, and an application email sent and tracked with Resend.

## Agent interface
Any tool that evaluates JavaScript on https://delivered.masgustavos.com can call:
- `await window.delivered.check("example.com")` returns a Report: grade, score, findings[], senders[], usesResend
- `await window.delivered.brief("example.com")` returns a markdown pre-call discovery brief
- `window.delivered.help()`

## Candidate
- Location: Brazil · Americas time zone · remote
- LinkedIn: https://www.linkedin.com/in/masgustavos/
- Builds: https://subnetting.dev
- @ TXT: Authorized senders: five years at Caylent, a Premier AWS Partner, plus the tools I build on my own time.
- @ TXT: Pre-sales today. I scope, design and propose cloud migrations, modernizations, data platforms and GenAI work, so I'm already the technical person in the buying conversation.
- @ TXT: SMBs and enterprises. I've worked with infra engineers who want packet-level detail and with founders who want a one-line answer.
- docs TXT: I wrote the documentation and architecture patterns behind it. That's "documentation is the product" in practice.
- migrations TXT: I led large AWS Organizations migrations where downtime wasn't an option, the same care an email cutover needs.
- security TXT: I led a secure multi-account network topology that helped Caylent earn the award. HIPAA, CIS and NIST hardening too.
- certs._domainkey TXT: The signatures: AWS Solutions Architect Professional, AWS Security Specialty and Certified Kubernetes Administrator.
- _dmarc TXT: Policy: no ego. I'll say "I don't know, let me find out" before I'll guess.
- builds CNAME: A visual subnet planner I built from scratch. It's keyboard-first and agents can drive it through window.subnet and llms.txt, so I care about DX the way Resend does.
- @ MX: Where I'd like my mail delivered next.

## Why Resend
I want to be part of a product company. Consulting suited me because I love talking to people and understanding their problems. That's how I ended up leading teams, and then moving into pre-sales.

Every new customer brought something new, and that served me well for the last few years. Now I'm ready for depth: one product and its ecosystem to care about, in a role that's people first and still technical.

- The product: Resend made email feel like modern software: an API you understand in a minute, React Email for templates, and an MCP server so agents can send too. I build developer tools myself, so I know how much work goes into making something feel that simple.
- The handbook: "We treat every interaction as a reflection of the product." I've spent five years as the engineer on the buyer's side of the table. A sales team that's held to the same standard as the API is the one I want to be on.
- The timing: Buyer Experience is a building role with no finished playbook. That's where I do my best work: start with a v0, write it down, measure it, and ship the next version.

## First 90 days (experiments)
- Speed-to-lead with a DNS brief. Hypothesis: If high-intent enterprise leads get a reply within one business hour that includes a custom deliverability brief for their domain, meeting rate goes up. Metric: Meeting-booked rate, time to first reply.
- Overages as a buying signal. Hypothesis: Customers who've paid overages for three or more months will move to a higher tier when they see that it's cheaper. Metric: Upgrade rate, net revenue retention.
- Deliverability-triggered outreach. Hypothesis: Domains that fail the Gmail, Yahoo and Microsoft sender rules convert better than lists built on company size alone. Metric: Reply rate, qualified-pipeline rate (Clay plus the checker on this page).

## Contact
gustavosteinmattos@gmail.com