Open main menu
Features
Company
Resources
Help
Docs
Pricing
Log In
Get Started
The process behind Resend
Hand
book
Search…
⌘
K
company
Why we exist
What we believe
How we got here
What inspires us
How we make money
What are our rituals
How we talk to each other
How to facilitate a project
How we innovate by experimenting
How dogfooding shapes our product
people
How we work
How we think about remote work
How we hire
What are the benefits
How the onboarding works
How to take time off
How to spend money
What is the travel policy
How to give feedback
How we recognize peers
How to lead a brainstorm
How we think about titles
Why we have a "meeting-free day"
engineering
What is our tech stack
Who is "The Fixer"?
How we use RFCs
How we plan our cycles
How we ship new features
How we separate deploy and release
How we handle pull requests
How we approach CI/CD
How we handle incidents
How we handle on-call rotations
How we handle post incident reviews
design
What's the role of design at Resend
What is our design process
How we think about design
How to work with the design team
What are our brand guidelines
success
What is our vision for exceptional support
How we help users
How we scale support
How we evolve our knowledge base
How we receive feedback
What is our philosophy for anti-abuse
marketing
How we approach marketing
How we keep momentum
How we think about social
How we think about YouTube
How we think about our website
How we write customer stories
How we think about swag
What are the most common use cases
What is our brand's voice and tone
sales
How we think about buyer experience
What is our sales philosophy
What's the role of sales at Resend
What is our sales stack
How to expand, upsell and cross-sell
