# Careers

**Hiring now.** We are building email infrastructure that developers trust with their password resets. That means the work is unusually unforgiving — a bug here is a customer who never received their receipt — and unusually satisfying when it is right.

## How we work

### Boring where it carries mail

We spend novelty on the guardrails and the onboarding experience. Everywhere a dropped email would cost a customer, we pick the dullest proven option.

### Honest about what we are not

Our comparison table admits where competitors beat us. Our security page says plainly that we are not SOC 2 certified. That posture is a hiring filter as much as a marketing one.

### Small on purpose, for now

Everyone here talks to customers and carries a pager. If you want deep specialisation inside a large org, this is the wrong stage.

## Open roles

### Founding Engineer, Email Infrastructure

Full-time · Remote

Own the send path end to end: the queue, the provider abstraction, the event pipeline, and eventually our own MTA. You will spend real time on deliverability — IP warm-up, feedback loops, blocklist delisting — which is the part most engineers have never had to learn and the part that decides whether the company works.

What we are looking for:
- Have run something in production where losing a message mattered
- Comfortable in TypeScript, and unbothered by reading an RFC
- Bonus: you have argued with a postmaster and won

Apply: 

### Founding Engineer, Developer Experience

Full-time · Remote

The SDKs, the MCP server, the docs, and the ten lines that take someone from signup to a delivered email. This role owns the first twenty minutes of every customer relationship, which is where most email APIs lose the evaluation.

What we are looking for:
- You have strong opinions about API design and can defend them
- You write documentation because you want to, not because it was assigned
- You have built with MCP, or are impatient to

Apply: 

### Founding Designer

Full-time · Remote

Product and brand together. The dashboard is where people debug a failed send at midnight, so this is information design under pressure rather than decoration — but you would also own how the whole company looks.

What we are looking for:
- A portfolio with at least one dense, data-heavy interface in it
- You can build what you design, or work closely enough with engineers that the gap does not show
- Comfortable being the only designer for a while

Apply: 

No cover letter. Send whatever shows us how you think — a repository, a shipped product, a write-up of something you debugged. Applications will formally open upon public launch. Write to .