Careers at Resend: Teams, Pay and How to Get Hired

Hiring Where the Product Is Stretching

Resend lists nine salaried roles on its job board, and every one carries a published salary band. For a company of roughly 45 people, that combination — a lean roster and radical pay transparency — is the most reliable signal a candidate has for deciding whether to apply and how to prepare.

Resend's active requisitions cluster in three zones: backend and product engineering, a nascent sales motion, and a customer success function that treats documentation as part of the product. Five are engineering roles split between continents: Software Engineer, Backend in Europe and the Americas; Product Engineer in both regions; and a Backend Engineer focused on MTA (mail transfer agent) infrastructure in the Americas. The sixth is a Technical Account Executive for the Americas, the first dedicated sales hire the board shows. The remaining three salaried roles aren't itemized publicly, but the company's February 2025 announcement welcoming Pauline Chin as a Customer Success Engineer confirms that function is growing. Contractors supplement design and brand work, a pattern the design team acknowledges openly.

The engineering mix tells you what the product needs next. Backend roles outnumber product roles two to one, and the MTA specialist posting signals that email delivery infrastructure — not just the API layer — is a current investment area. Product Engineers work across the full stack using React, TypeScript, Tailwind, and Radix, and the design handbook notes that code serves as the source of truth, with Figma serving collaboration rather than specification. That means a Product Engineer candidate should expect to ship production code from day one, not hand off mockups.

Design operates as a horizontal layer across product, marketing, and brand. For each, the team runs two processes: Balsamiq for early exploration, then Figma for collaboration. The handbook explicitly discourages Loom videos or GitHub issues for design feedback, preferring open channels in Linear and Slack. Contractors have done brilliant work on major projects, the design lead said, so the design hiring bar is calibrated for both full-time and project-based contributors.

Sales sits earlier than the engineering org. A single Technical Account Executive role suggests Resend is testing a direct motion for larger accounts after relying on self-serve and developer adoption. The title "Technical" is deliberate: the role sits beside engineers, not in a separate sales org, and the philosophy page's emphasis on "credible, consistent, and predictable" output extends to how the product is sold.

Customer Success Engineering doubles as a technical discipline. Chin's introduction highlights "leverage existing knowledge, whether through documentation, colleagues, or open-source communities," a signal that this role writes code, debugs integrations, and feeds the docs the philosophy page calls "the product".

The distribution is lopsided by design. A lean team spanning nine time zones with no-meeting Wednesdays and a Monday planning cadence cannot onboard generalists. Every open role maps to a surface the product is actively expanding: MTA reliability, multiplayer editing, bulk sending (in beta), and newsletter broadcasting (in exploration). If your background doesn't align with one of those surfaces, the current hiring plan doesn't have a slot for you, and that clarity is the signal.

What Resend Pays

Resend posts salary bands on its own job listings, a practice that still puts it ahead of most corporate postings, where pay details appear in fewer than one in seven ads. Zero G Talent's board data shows a combined band running roughly $136,000 to $188,000 and a median midpoint around $170,000. That range reflects base salary only; equity and benefits sit on top. Candidates comparing offers should treat the posted band as the cash anchor, not the total package ceiling.

The board data breaks cleanly by function and geography. Software and product engineering roles between $140,000 and $180,000 depending on specialization and region. Backend engineers in the Americas and Europe share the same $140,000–$180,000 window. Product engineers — a hybrid profile that ships customer-facing features end to end — sit tighter at $150,000–$170,000 in both regions. The Backend Engineer, MTA role, a deeper infrastructure slot, mirrors the product engineer band at $150,000–$170,000 for Americas-based hires. On the revenue side, Zero G Talent reported the Technical Account Executive role carries the widest spread: $160,000–$220,000 for Americas candidates, reflecting variable commission structure baked into the band.

Third-party aggregator levels.fyi reports a wider total-compensation spread, a median of $119,400 across all reported roles as of September 2026, with individual figures spanning from $99,500 for Customer Service in the United States to $139,300 for a Software Engineer in Brazil. The gap between that median and Resend's posted base median stems from methodology: levels.fyi blends base, bonus, and equity into total compensation across all levels and tenures, while the board bands reflect current open requisitions for experienced individual contributors. Both signals matter. The aggregator shows where the market has settled for people already in seat; the board shows what Resend is willing to pay for the next hire.

Pay transparency laws now cover more than a third of US states, with Delaware joining in September 2027. Resend's remote-first posture means its postings routinely trigger the strictest regimes: Colorado, Illinois, and New York each require external and internal posting disclosures plus benefits descriptions. The company's bands are specific enough to satisfy those rules without resorting to the overly broad ranges that invite regulator scrutiny. A candidate in New York or California sees the same numbers as a candidate in Lisbon or São Paulo; the band does not shift by locale. That consistency simplifies benchmarking but also means a hire in a lower-cost market captures the full band value.

For negotiation, the band's width is the lever. The Technical Account Executive span of $60,000 signals meaningful performance-based upside; the $30,000 spans on engineering roles suggest tighter leveling. Candidates should ask where inside the band an offer lands and what milestones move it toward the top. The board data does not break out equity grants or refresh cadence. Those conversations happen after the screen. But the cash number on the posting is the floor Resend has already committed to publicly. That commitment is the strongest signal a candidate has before a single interview.

Seven Stages to an Offer

Resend publishes its entire hiring pipeline in the company handbook, and the sequence is specific even for a team under 100 people. It runs seven stages: an introduction call, a paid take-home challenge (roughly three to four hours), a technical interview, a cultural interview, a conversation with the founders, reference calls, and finally an offer. A third-party interview guide describes a similar arc: a recruiter screen, the same paid take-home, then three 60-minute sessions (pair programming, system design, and a past-project deep dive) followed by a behavioral round, spanning three to five weeks. Both accounts agree on the async work sample and the multi-angle technical assessment; the handbook adds the founder meeting and explicit reference step as formal gates.

The introduction call is a clarity check, not a screen. "The goal is not depth but clarity, logistically, whether proceeding makes sense," the handbook said. Resend said it reviews every submission within three working days and that candidates should never feel ghosted. That commitment matters because Resend hires across four functions — software engineering, product and design, customer success, and sales and business development — and the evaluation criteria shift at each technical stage.

For engineering roles, the take-home is the primary filter. Resend expects fluency in TypeScript and React, with Go for backend positions, and designs the challenge to reveal "demonstrable craft" and "strong written communication," phrases the interview guide repeats as non-negotiable. Candidates who advance face pair programming on a real problem, a system-design discussion that often touches on email infrastructure (SMTP, DKIM, SPF, DMARC, MIME), and a deep dive into a past project where they must explain trade-offs, not just outcomes. The cultural interview and founder meeting then test whether the candidate's motivations align with how Resend builds developer tools: "We want to understand what excites you, and what matters to you, and whether that aligns with the way we build software."

Product and design applicants follow a similar arc, but the take-home leans toward product thinking and design systems rather than pure implementation. The handbook notes there is "no exact script by design" for the culture step, questions meant to break standard interview molds so the candidate has to think, not recite. For customer success and business development roles, the technical interview gives way to a role-specific case: a support scenario requiring protocol knowledge (how SPF, DKIM, and DMARC work together to authenticate a sender) or a sales exercise built around Resend's actual pricing and deliverability positioning. Current open roles (Account Executive, Backend Engineer, Business Development, Customer Success) confirm this split.

Reference calls are mandatory and structured: at least two, one from a manager or supervisor and one from a peer. "We will reach out to your references to get a better understanding of your work history and how to best support your success," the handbook says. This step comes after the founder meeting, meaning a strong technical and cultural showing can still be overturned by reference feedback.

What gets candidates through is consistency across the chain. The handbook emphasizes spotting "signals that suggest misalignment, either technically or culturally" and clarifying even small signals in subsequent rounds. Conversely, "positive indicators that someone will thrive here, the way you communicate, the way you work" compound. Reading the Resend blog before applying is explicitly recommended prep; the interview guide notes "they hire people who already engage with the work." In practice, that means a backend engineer who can discuss DMARC alignment and aggregate reports in the system-design round, or a sales candidate who references a recent Resend blog post on deliverability during the founder conversation. Candidates who arrive prepared signal the kind of thinking the process rewards.

A Remote Company, One Address

Resend is a remote company first. The company's own handbook states it plainly: "Resend is a remote company. There are no plans for this, but even if there are some local offices in the future, the core operations of the company will always facilitate remote work because we believe in it as a way of working." That is the operating assumption behind every role Resend posts, and it shapes how a candidate should think about the physical context of the job before applying.

That said, Resend is not office-less by accident. The company maintains a corporate headquarters at 2261 Market Street, Suite 5039, San Francisco, CA 94114. As of the most recent records, San Francisco is listed as the sole global office location. Resend also absorbed Briefer, a subsidiary founded in 2022 and based in Sao Paulo, Brazil, through a merger completed on August 5, 2025, adding a South American node to the company's geographic footprint, though the research does not describe it as a staffed office.

The remote model is not loose or unstructured. Resend's handbook lays out a specific operating rhythm. The company defaults to asynchronous communication: RFCs instead of meetings, Slack channels instead of synchronous stand-ups, and Linear tickets instead of office whiteboards. Working hours stay inside the Americas' time zones, with business hours running from 1 PM to 12 AM UTC, which constrains the window for real-time collaboration across a distributed team. Resend plans two offsites per year for in-person time and switches to synchronous work when the situation demands it, during incidents, at the beginning of complex problems, and in other moments when the async model alone will not move things forward fast enough.

Resend's job listings reveal a striking distribution for a company of its size. Board postings and third-party listings show roles spread across multiple continents: a Technical Account Executive covering the Americas, Software Engineer and Backend roles in Europe and the Americas, a Product Engineer in Europe, and a Backend Engineer, MTA in the Americas. Listings on Remote Rocketship, Wantapply, and Built In Dublin show candidates from Kazakhstan, Cyprus, Serbia, and Ireland being considered for remote roles, with some postings tagged as hybrid or offering relocation. The company is small (PitchBook reports 6 employees and Highperformr lists 50), which means every hire materially shifts the team's geographic mix.

For a candidate weighing whether to apply, the practical question is not whether Resend has an office nearby. It is whether they can work effectively within the Americas-centric time zone window, contribute in an async-first culture that defaults to writing over talking, and show up in person twice a year. The San Francisco address exists, but the handbook is unambiguous: remote work is the core operating model, and Resend expects candidates to build their lives around that reality rather than the other way around.

The Profile That Gets Through

The conditions that determine who succeeds at Resend are not listed in any job posting. They emerge from the company's own record — its published bands, its open handbook, its documented hiring mix — and they select for a specific kind of candidate.

Resend's hiring record shows a specific profile taking shape across a small, remote workforce. The published band runs from roughly that range, with a median near $170,000. That's a lean roster. A roster this size is not a sprawling org chart; each hire touches a disproportionate share of the product, each departure creates a visible gap, and the person who thrives fills gaps on their own.

The postings cluster around three functions: backend software engineering in the Americas and Europe (at $140,000–$180,000), product engineering in both regions (at $150,000–$170,000), and customer-facing roles including a Technical Account Executive in the Americas (at $160,000–$220,000). A Backend Engineer, MTA posting rounds out the engineering roles. Both the Technical Account Executive and the product engineering roles suggest Resend is not building in isolation; the company needs people who can bridge the gap between the codebase and the customer. A candidate who treats customer success as an afterthought, or who sees engineering as a closed system, will find the culture here demanding in a specific way. The hiring mix signals that Resend wants generalists who can go deep and specialists who can reach across the table.

The remote setup adds another filter. With a small workforce spread across continents — roles in both Americas and Europe represented in the postings — synchronous communication is a luxury, not a default. Someone who thrives here is comfortable writing things down, asynchronous by default, and picking up context from a thread rather than a hallway conversation. Resend posts roles in multiple regions, which means the person who succeeds coordinates across time zones without waiting for a meeting to unblock themselves. At Resend, that ability is a working condition, not a soft skill.

Resend's transparent salary band signals who the company expects to attract. By publishing a range that runs from roughly that spread, the company asks candidates to self-select on compensation expectations before they apply. The person who applies to a $140,000 role when the band tops out at $188,000 makes a different calculation than someone who targets the top of the range. That transparency filters for candidates who have done their homework and whose expectations align with what Resend is actually paying. A candidate who walks in expecting a negotiation that starts at the top of the band may find the process frustrating; someone who understands the band is the anchor, not the ceiling, moves through it more smoothly.

The company's small size also means the person who thrives wears multiple hats without waiting for permission. In a small salaried workforce, the line between product engineer and backend engineer is porous. The Technical Account Executive is not just closing deals; they feed customer signal back into the product. Research on workplace feedback reinforces this point: Glassdoor data shows that four in five job seekers say their perception of a company improves after seeing an employer respond to a review, and businesses that respond regularly often receive more reviews because customers notice the company cares. Resend's transparent compensation and documented hiring mix function the same way; they signal that the company has nothing to hide, and that kind of openness attracts people who value directness over corporate ambiguity.

Those conditions, drawn from that record, are specific. Comfort with a small team where each role carries weight. The ability to work asynchronously across distributed geography. Alignment with a transparent compensation model that rewards self-knowledge. A willingness to bridge engineering and customer-facing functions without waiting for organizational charts to define the boundaries. The person who thrives here builds the structure as they go, matching their skills to the teams Resend is actually building, not the ones it imagines it might need someday.

Nine roles on a board that never goes dark. A salary band that asks candidates to do their math before Resend asks a single question. The numbers are on the page. The rest is up to the person reading them.

Working in AI? Zero G Talent tracks the openings: see every open Resend role, browse AI jobs, the companies hiring, and the people building the field.