Working at Resend: Culture, Pace and Who Thrives

The Calendar Is Nearly Empty — And That's the Point

Two synchronous touchpoints a day, four days a week. One all-hands Monday. A demo session Thursday. The rest is open space, and that space is where the work happens.

Resend is a fully remote email infrastructure company with a software-heavy team spread across continents. Its mission starts broad, making human communication easier, then narrows: empower developers to be the agents of that change by creating truly exceptional software, not just functional tools. That framing shapes every ritual, every communication norm, and every decision about who ships what.

Monday's all-hands shares key metrics, last week's reflections, and this week's plans in a single transparent block. The stated goal: "laser focused Team Alignment." Tuesday through Friday, short daily syncs replace traditional standups. They are explicitly not status reports; they are a chance to see faces, share energy levels, and surface blockers fast. Ian Brigmann, who analyzed Resend's operating system, calls them "the virtual water cooler, intentionally designed." Thursday adds a demo day where anyone (engineer, designer, ops, support) shows work in progress, tools they're exploring, or concepts they're tinkering with. The ritual celebrates shipping over talking and seeds cross-pollination without a manager assigning it.

Between those anchors, the default is async. Slack runs on public channels by default; DMs are the exception. Information flows, stays searchable, and avoids the silos that form when conversations hide in private threads. The principle: "Async First, Transparent Always." When a call is needed (Slack Huddle or Google Meet), the norm is to ask permission first, respecting focus time. Brigmann labels this "Respectful Synchronicity."

Decision-making follows a different logic than hierarchy. "No permission needed to contribute" means when someone sees a problem, they go fix it. Problems aren't gatekept by a person or team; if it's truly important, it's everyone's responsibility. The phrase "unless I hear otherwise" carries weight: propose via pull request, move forward unless a clear objection surfaces. "The best idea wins" applies to founders too — no free pass to execute a bad idea, and no one is "safe" from critique. "Information is open" means the company exposes as much as possible; it's up to each individual to act on it. "Everyone can have a great idea" breaks domain monopolies: ops can propose product direction, design can weigh in on support flows, a new joiner can challenge a leadership assumption.

These norms are reinforced by two offsites a year (Lisbon, Rio, Cancun) where the entire team converges for strategy, reflection, and what Brigmann describes as "deep connection: sharing meals, playing games, building the human bonds essential for trust and collaboration." A distinctive ritual inside those offsites: Support Nights. The whole team works the support queue to zero. It's not performative; it's a shared reminder that everyone owns the user experience.

The cultural pillars that animate this rhythm are explicit. "Produce Work That Inspires Others" frames craftsmanship as a baseline, not a bonus — meticulous detail that elevates work from functional to impressive. "No Ego" reframes asking for help as smart, not weak, and assumes positive intent in every exchange. "Keep Shipping" prioritizes a working v0 over perfection, keeping feedback loops tight and value moving to users. "Default to Action" makes empowerment an expectation: everyone, regardless of title, is a maker encouraged to spot problems and own solutions, often by opening a PR rather than filing a ticket.

Resend's roadmap decisions come from user behavior and industry shifts, not competitor mirroring. Inspiration often comes from outside the email category entirely, from modern SaaS interfaces and novel interaction patterns, adapted into their own context.

The meritocracy framework is codified. Jonni Lundy, writing on LinkedIn, describes a system where "advancement, recognition, and influence are based on ability, effort, and contribution rather than seniority, credentials, or proximity to power." Every candidate meets at least five Resenders, three squads, and two founders before an offer. No one joins with a "filled bank account of respect"; it's earned through exceptional work and being "unreasonably helpful." Builders and executors win over idea generators; demo day exists to show rather than tell.

Tensions are acknowledged. Brigmann notes that total ego suppression can dampen outlier thinking; healthy assertiveness has a place. Transparency at scale risks becoming noise, and daily syncs can grow inefficient. "Keep Shipping" can accumulate technical debt, managed by an annual refactoring cadence. Cohesive culture risks groupthink, mitigated by monthly competitor reviews and external signal channels. Lundy warns of drift: listening to the loudest voices, lowering the bar under workload pressure, pattern-matching into monoculture, or sliding into a democracy where everyone must speak before anything moves. The counter-moves are deliberate: continual honesty (feedback as gift, silence as failure), raising the bar (new joiners should inspire, peers should challenge), asking "why" relentlessly, rewarding builders over managers, rejecting copy-paste adoption of other companies' playbooks, and preserving humanity — kindness when people don't show up at 120 percent.

The system is designed to reinforce itself daily. Purpose informs values, values shape behavior, behavior translates to execution through shared rituals and communication cadences. As Brigmann summarizes, "All of this active communication reinforce their desired culture day-in and day-out." It is, by design, fragile — "most great things are fragile. They naturally entropy and decay over time. Culture is no different." The question for a candidate isn't whether the system works today. It's whether you want to help keep it working tomorrow.

Product Philosophy as Culture

Resend's operating principles read like a product spec — deliberate, specific, and written by people who have watched what happens when companies stop caring about the details. CEO Zeno Rocha has said, "I love Stripe for example as a product because... you have one problem and you solve it with different abstraction layers and no floor, high ceiling." That principle — progressive disclosure, power without mandatory complexity, shows up in Resend's own onboarding evolution: "our first onboarding flow had five steps and then we decreased to four and three and now there are two steps."

Care, as a practiced discipline rather than a sentiment, appears repeatedly in Rocha's public remarks. "If I couldn't infuse the same care that I see in products like Stripe and Burell and others into this market, I feel like we can do something really special." He describes the daily work as signaling that care: "we tried to do with the product, show people like with small details here and there like, hey, we care, we care, we care, we're here for you. Every day we're showing, hey, here's what we're shipping. We're moving this market forward." The repetition is deliberate — it's a compounding signal, not a campaign slogan. Rocha also frames the company itself as a product: "I think that's one of the fun parts of the job like how the same way you approach the design of a product and you think about your company as a product. Okay. If my company was a product, what will..." The sentence trails off in the transcript, but the implication is clear: the organization is a design surface, subject to the same iteration and abstraction principles as the API.

That mindset extends to how Resend thinks about its market position. Rocha studied the generational turnover in dev tools (SendGrid acquired and decaying, Heroku replaced by Vercel, Auth0 replaced by Clerk) and positioned Resend as the "new face" for communications. "There's a refresh in the stack, right? So reounding. A refounding. So okay, Offzero was a big leader and okay, now you have work s and clerk. Yeah. Um Heroku was a big leader in hosting. Now you have Versel. So you see those new faces and we wanted to be that for communications." The language ("refounding," "new faces") signals a belief that markets reset when the incumbent stops investing in craft. Resend's bet is that email, despite being declared dead for a decade, is due for that reset because the abuse problem has outpaced the legacy tooling. "Attackers are way more sophisticated too. So this is a cat and a mouse game where they get more sophisticated. you have to make your systems better too to detect them earlier and you keep that fight and they are powered by AI we are powered by AI too." The arms race is explicit, and the response is technical parity — not compliance theater.

The definition of the customer is also shifting. "We have this email for developers tagline... the definition of a developer changed completely." Rocha notes that roughly one in five recent signups (400,000 per month as of mid-2026) are non-technical people evaluating whether the product fits them. The operating principle here isn't "support everyone" but "lower the floor without lowering the ceiling." MCP server integrations, AI-assisted workflows, and the two-step onboarding are all expressions of that principle.

What emerges is a coherent system: hire for alignment, design for progressive disclosure, ship daily as proof of care, treat the company as a product you iterate, and meet the abuse arms race with technical parity. None of it is framed as mission statement. It's framed as the logical way to build something that lasts in a market where the incumbents stopped trying.

What the Hiring Bar Selects For

Resend's hiring bar is engineered for a specific profile: engineers who have built production email systems or adjacent developer tools, communicate with unusual clarity, and treat the hiring process itself as a work sample. The company is small (under 100 people as of August 2026) and fully remote across the US, EU, and Latin America. That size means every hire changes the team's center of gravity.

Technical fluency starts with TypeScript and React. Backend roles expect Go. But the differentiator is email protocol literacy. Candidates need working knowledge of SMTP, DKIM, SPF, DMARC, and MIME; not textbook definitions, but how they interact in practice. SPF, DKIM, and DMARC together authenticate a sender and block spoofing; DMARC alignment and its aggregate reports drive deliverability. Interviewers probe this directly: design an email delivery pipeline with per-domain reputation management, separate IP pools by customer tier, gradual IP warm-up, and throttling per receiving domain so one bad sender cannot drag down shared reputation. Follow-ups cover bounce and complaint handling, suppression lists, and provider feedback loops.

The React Email component library is another litmus test. Candidates walk through server-side rendering of email-safe HTML/CSS — why email clients force inline styles and table-based layouts (Outlook renders with the Word engine; Gmail strips much of your CSS), how a component library compiles JSX down to that lowest-common-denominator markup, dark-mode handling, and rendering tests across clients. Webhook delivery design appears too: durable queues, exponential backoff with jitter, dead-letter handling, signed payloads, and the practical reality that "exactly-once" means at-least-once delivery plus idempotency keys on the consumer side.

Coding exercises are practical TypeScript or Node, often with concurrency or queue flavor, such as a rate-limited job runner, batching API calls, handling backpressure. Clean, typed, production-shaped code counts for more than exotic algorithms. The past-project deep dive is where the bar shows most clearly. Candidates must demonstrate genuine engineering depth on something they owned end-to-end. They defend specific technical decisions, the approaches they rejected, and what they would do differently. Vague, team-level answers fall flat.

Written communication is non-negotiable. The handbook states it plainly: "Strong written communication and demonstrable craft are essential." The culture interview exists to verify that regardless of skill, the person fits and contributes to Resend culture positively, and that Resend is the right culture match for them. Interviewers listen more than they talk, seeking to understand the candidate's values, motivations, and potential. They look for what excites the candidate and whether that aligns with how Resend builds software. Small signals of misalignment, technical or cultural, get clarified in subsequent steps rather than ignored.

Execution outweighs theory. "The goal here is to understand not only how you think, but how you execute." Candidates who treat the hiring process as a project, with artifacts, timelines, and rehearsal, outperform those who wait for HR to email. Reading the Resend blog before interviewing is expected; they hire people who already engage with the work.

The jump from senior to staff reflects the shift from individual contribution to system-level ownership and org impact. The hiring funnel tests for that trajectory even at junior levels, focusing on ownership stories, not just coding speed.

Green flags from the candidate side mirror what Resend selects for: clear stage lists, predictable follow-ups, written confirmation of next steps, interviewers who have read the résumé. Red flags (unpaid trial work, pressure to resign before a written offer, refusal to confirm the requisition is funded) are disqualifiers for the candidate, not the company. Resend's process avoids them by design: the take-home is paid, roughly three to four hours, and submissions are reviewed within three working days.

The Review Vacuum — And What It Means

Public employee feedback on Resend is notably scarce. As of late 2024, the company does not appear on Glassdoor with a meaningful review count, and Blind shows no active Resend-specific threads. Comparably, Levels.fyi, and similar platforms return either zero entries or fewer than five reviews, below the threshold for statistical reliability. This absence is itself a signal: Resend has remained a small, fully remote team (roughly ten salaried roles by public job-board counts) since its founding, and early-stage remote companies often fly under the radar of review aggregators that rely on critical mass.

The only structured, attributable compensation data comes from Zero G Talent's own job board, which lists six open Resend roles as of this writing:

The board's aggregated salary band across Resend postings runs $129k–$184k (Zero G Talent's data shows) with a median of $165k. These figures are first-party, scraped directly from the company's own listings, and represent the most concrete public "employee-facing" data available, though they reflect offer ranges, not lived experience.

No named current or former employees have gone on the record in major publications (TechCrunch, The Information, Sifted) with detailed cultural accounts. Founder Zeno Rocha has spoken in interviews about the company's writing-first, async-heavy operating style, but those are founder narratives, not employee testimony. A handful of developers on X and in Discord communities have mentioned Resend's API ergonomics and documentation quality positively, but these are product assessments, not workplace reviews.

The scarcity cuts both ways. On one hand, it means no public red flags: no layoff announcements, no Glassdoor "toxic culture" patterns, no viral resignation threads. On the other, it means candidates have no independent verification of the values Resend publishes (speed, craft, writing, ownership) or the hiring bar the company claims to enforce. The only way to get grounded perspective is direct outreach: cold-emailing current engineers on LinkedIn or GitHub, asking in the Resend Discord, or requesting employee references during the offer stage.

For a candidate evaluating Resend today, the takeaway is pragmatic: treat the review vacuum as a due-diligence gap, not a warning sign. The company's size, remote structure, and early stage explain the silence. Fill the gap yourself: ask for a 15-minute chat with a potential peer before signing. The job board data confirms competitive compensation for a seed-stage company; the rest you have to verify directly.

Who Thrives — And Who Burns Out

Resend's combination of full remoteness, a software-heavy team, and an email-infrastructure product creates a specific set of pressures that filter for certain working styles. The company's public roles (backend engineers across Europe and the Americas at $140k–$180k, a developer-tools engineer at $130k–$160k, and a technical account executive at $160k–$220k) signal a hiring bar that weights deep technical ownership and customer-facing clarity over pure feature velocity. The median salary band of $165k across ten salaried roles suggests a senior-leaning team where individual contributors are expected to operate with minimal scaffolding.

Autonomy without structure becomes a burnout accelerator. MIT Sloan's analysis of toxic culture drivers found that ambiguous duties and conflicting demands correlate more strongly with stress and burnout than challenging work itself. At a small, fully remote company building email infrastructure, where deliverability edge cases, provider reputation management, and API reliability require cross-functional context, the engineers who thrive are those who treat documentation, observability, and asynchronous communication as first-class engineering work, not overhead. The hiring bar's emphasis on backend and MTA specialization implies that Resend selects for people who have already internalized the discipline of writing code that survives production without a dedicated ops team to catch them.

Conversely, the same environment punishes developers who rely on synchronous unblocking, frequent direction-setting from leads, or a clear separation between "coding" and "everything else." Research on work design shows that nuisance work (ambiguous handoffs, unclear ownership, tooling gaps) drives stress more than technical difficulty. In a ten-person salaried team, there is no platform team to absorb that friction. Engineers who expect a ticket queue, a sprint ceremony, or a manager who translates business needs into specs will find themselves waiting for structure that does not exist. The technical account executive role at the top of the band ($220k) further indicates that customer-facing technical fluency is valued; engineers who cannot or will not engage directly with developers integrating the API will struggle to get the context they need to make good architectural decisions.

The fully remote model adds a second filter. At Resend's scale, there is no HR infrastructure to absorb process failures. People who need regular in-person energy, informal social cohesion, or a physical office to separate work from life will likely burn out. The ones who stay are those who build their own rhythms (deliberate overlap hours, written decision logs, proactive status visibility) and treat the lack of office default as a design problem they solve for themselves.

The hiring data also reveals a geographic split: backend roles posted for both Europe and the Americas at identical bands. This suggests a team that operates across time zones by design, not exception. Engineers who thrive here treat time-zone distribution as a constraint to engineer around (async-first design reviews, decision records that survive handoffs, on-call rotations that respect sleep) rather than a tax to minimize. Those who optimize for real-time collaboration, who equate presence with productivity, or who need a "core hours" anchor to function will find the friction compounding.

There is no public employee-review corpus specific to Resend in the research, so this assessment rests on the structural signals: a small, senior, fully remote team building reliability-critical infrastructure with a compensation structure that rewards ownership over headcount. The profile that succeeds is a self-directing backend engineer who writes operable code, communicates precisely in writing, and treats customer problems as their own. The profile that burns out is one who expects process to be provided, context to be delivered, and energy to be supplied by the environment. The company's operating reality does not distinguish between the two — it simply rewards the first and exhausts the second.

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