Careers

Do the most delivered work of your career.

Small platform team, unreasonable standards, 1.8 million emails a month from week one.

Why MailOps

Four reasons people stay

1

Ownership from day one

You ship a routing change in your first week and present it by your fourth.

2

Incidents in the room

Every engineer joins the postmortems. No telephone game.

3

Craft over ceremony

Few meetings, short documents, long stretches of deep work.

4

Volume that teaches

At 1.8M emails a month, every theory gets tested by Friday.

Open roles

Four seats, warm

Senior Platform Engineer, Email Infrastructure

Engineering On Site / Hybrid Full-time

Own the SMTP edge, the routing engine and the vendor mesh that carries every message we send.

  • Design and operate the acceptance layer and routing rules
  • Keep failover under sixty seconds, measured
  • Pair with SRE on breaker thresholds and capacity
Apply

Applied AI Engineer, Diagnosis Models

Engineering Hybrid Full-time

Own the models that read bounce clusters, explain root causes and propose routing fixes.

  • Design failure-mode taxonomies with deliverability leads
  • Run offline evals and shadow diagnoses
  • Keep latency and cost inside budget
Apply

SRE, Deliverability

Engineering Remote Full-time

Make 99.2% the floor, not the ceiling — and make every incident cheaper than the last.

  • Own delivery SLOs across all vendors
  • Tune circuit breakers from incident evidence
  • Automate the toil out of the on-call rotation
Apply

Internal Developer Advocate

Platform Remote Full-time

Make MailOps the obvious way to send mail — docs, examples and office hours for every product team.

  • Write the integration guides product teams actually read
  • Run onboarding for new sending teams end to end
  • Feed platform gaps back with evidence
Apply

Nothing here with your name on it?

We hire for slope, not intercept. Tell us what you would own here.

Get in Touch

Not the role? Still curious?

Read what the platform actually does before you write to us.