Rain is hiring a Backend Engineer in Engineering — New York, NY. The overview below is synthesized from the employer posting on jobs.ashbyhq.com: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
About the Company
Company context from the listing:
Rain is the global stablecoin payments platform for enterprises, neobanks, platforms, developers, and AI agents. Our technology allows partners to move, store, and use stablecoins instantly and compliantly through global payment cards, rewards, on/offramps, wallets, and cross-border rails.
You will have the opportunity to deliver massive impact at a hypergrowth company backed by some of the top investors in fintech, crypto, and SaaS. In January 2026, we closed a $250M Series C led by ICONIQ, valuing Rain at $1.95B, with Sapphire Ventures, Dragonfly, Bessemer Venture Partners, Galaxy Ventures, FirstMark, Lightspeed, Norwest, and Endeavor Catalyst also participating.
Our Ethos
We believe in an open and flat structure. You will be able to grow into the role that most aligns with your goals.
What you'll do
Day-to-day scope for the Backend Engineer as described in the posting:
- Be a critical part of the technical and product roadmap
- Contribute to our backend and integrate a variety of third-party services
- Scale our infrastructure to millions of end users globally
- Rapidly ship new capabilities to our customers
- Help drive the architectural decisions of a rapidly evolving product
- Interact with smart contracts across multiple chains
What we're looking for
- Experience with NodeJS and other backend technologies
- A builder mentality, someone who experiments with side projects
- This position is for folks with 2-10+ years of experience, compensation will be based on experience
Nice to have, but not mandatory
Additional experience noted as a plus:
- Fintech experience (neobank or card issuing experience gets extra brownie points)
- Experience with smart contracts and blockchains
Things that enable a fulfilling, healthy, and happy experience at Rain
Unlimited time off 🌴 Unlimited vacation can be daunting, so we require Rainmakers to take 10 days minimum for themselves.
Flexible working ☕ We support a flexible workplace – work from home, come into an office, or both. We want everyone to work in an environment where they're their most confident and productive selves.
Easy to access benefits 🧠 For US Rainmakers, we cover 95% of your health, dental, and vision plan costs and 90% for your dependents, plus a 100% company-subsidized life insurance plan.
Retirement goals💡 Plan for the future with confidence. We offer a 401(k) with a 4% company match.
Equity plan 📦 Every Rainmaker gets an equity option plan so we all benefit from our success.
Health and Wellness 📚 High performance begins from within. Rainmakers receive a monthly stipend to be used for eligible health and wellness spending like gym memberships/fitness classes, massages, acupuncture - whatever recharges you!
In-office meals 🍜 Rainmakers working from the office enjoy lunch and dinner on us, covered with a DoorDash credit.
Team summits ✨ Summits play an important role at Rain. Time together helps us build relationships and a common destiny.
Build a standout application
For the Backend Engineer at Rain, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.
Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.
In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.