Careers

What you'll do

• ·Design and harden the order pipeline: address verification, pricing, sandbox mode, print/mail handoff, and the webhook contract that tells a caller what actually happened.
• ·Own the confirmation-token and capability-token safety layer that separates quoting from spending money — this is the thing that lets an AI agent hold a payment method without also holding the authority to use it unsupervised.
• ·Work directly with USPS and print-vendor integrations; be the person who understands the real failure modes (undeliverable addresses, print rejects, refused/returned mail) and designs for them.
• ·Set the technical bar for the rest of the backend as the team grows past you being the only one.

What we're looking for

• ·5+ years building and operating production backend systems, ideally with real money or real physical fulfillment on the line.
• ·Comfortable owning a system end to end — schema, API contract, background jobs, the on-call pager.
• ·Have shipped something where "it silently failed and nobody noticed for a week" was a real risk you designed against, not a hypothetical.

Nice to have

• ·Next.js/TypeScript experience.
• ·Experience with idempotency, webhooks, or payment-adjacent systems (Stripe, similar).
• ·Curiosity about AI agents as a first-class API consumer, not just a human behind a browser.

What you'll do

• ·Design and maintain the postal design system (the paper/ink token set, the letter-as-interface visual language) that every surface on this site draws from.
• ·Own the send flow from a blank page to a mailed letter — the highest-stakes, highest-traffic screen in the product.
• ·Design for two audiences on the same surfaces: a person sending one letter, and an AI agent calling the same paths programmatically — without either one degrading the other.
• ·Be the first design hire; set conventions the next several hires will inherit.

What we're looking for

• ·4+ years of product design, with real shipped work you can walk through decision by decision, not just a polished shot.
• ·Comfortable in code enough to hand off (or make) a real Tailwind/React component, not just a Figma file.
• ·A track record of shipping something plain and honest that still felt considered — this brand is deliberately not flashy.

Nice to have

• ·Experience designing for a dual consumer/developer audience.
• ·Illustration or type-systems background.
• ·Has personally been frustrated by a bad checkout flow enough to redesign one out of spite.

What you'll do

• ·Own and improve the developer docs (`/developers`, the direct-mail and mail-merge API pages, the MCP tool reference) — including the live sandbox try-it panels.
• ·Write and maintain integration guides for the platforms people actually build on: n8n, Pipedream, Claude, ChatGPT, and whatever shows up next.
• ·Be a real engineer, not just a writer — ship fixes to the SDKs, the sandbox, and the docs tooling yourself rather than filing tickets for someone else.
• ·Represent developer feedback back into the roadmap; you are the loudest advocate for the API being pleasant to use.

What we're looking for

• ·3+ years as a software engineer, with genuine enjoyment of writing docs and example code, not just tolerance for it.
• ·Comfortable being the public face of the API — GitHub issues, integration debugging, the occasional live demo.
• ·Real, hands-on experience building something on top of an LLM tool-use or MCP-style interface, not just reading about it.

Nice to have

• ·Has published an open-source integration, SDK, or community node for another product.
• ·Experience with n8n, Pipedream, Zapier, or similar workflow platforms.

What you'll do

• ·Own organic growth: the use-case pages, the comparison pages, the guide library, and the programmatic-SEO playbook already documented in this codebase.
• ·Decide what the next 50 pages should be, backed by real keyword and competitive research, not guesswork.
• ·Keep every public claim honest and verifiable — this brand's whole differentiator is a price that means what it says and refusing to fabricate proof, and marketing has to hold that line as hard as engineering does.
• ·Run the first paid-acquisition experiments once organic has a real baseline.

What we're looking for

• ·3+ years in growth or SEO-led marketing at a company selling to both consumers and developers, or a strong track record on one side plus real curiosity about the other.
• ·Comfortable writing copy yourself, not just briefing someone else to.
• ·Has shipped programmatic SEO before and can talk about what broke.

Nice to have

• ·Experience marketing an API or developer product alongside a consumer product on the same site.
• ·Direct-mail, legal-services, or local-services marketing background (the core use cases here: certified mail, demand letters, notices).

What you'll do

• ·Manage the relationship with print/mail fulfillment partners — SLAs, print-run cutoffs, quality issues, cost.
• ·Own the fraud/content screening process (automated with human review on flags) that keeps this a mail service and not an abuse vector.
• ·Track and report the real operational numbers — delivery times, refund rates, screening false-positive rate — the same numbers this site's own honesty rules require being accurate about publicly.
• ·Be the escalation point when a real letter goes wrong: lost mail, a bounced address, a support case that needs a human.

What we're looking for

• ·3+ years in operations, logistics, or trust & safety, ideally with a physical-fulfillment or regulated component.
• ·Comfortable being the person who says no to a print run that doesn't look right.
• ·Detail-oriented enough to catch the edge case everyone else missed.

Nice to have

• ·Direct experience with USPS commercial mailing programs (Certified Mail, First-Class presort, or similar).
• ·Background in trust & safety or content moderation.