About Donorbox
Donorbox is a leading fundraising platform and donor management system for nonprofit organizations. Our mission is to accelerate positive impact worldwide by helping nonprofits become highly effective at raising funds and managing their supporter base. Since 2014, we have powered more than 100,000 global organizations to raise over $4 billion in donations. 🚀
Our fast-growing company is profitable and bootstrapped with a healthy run rate. We have a fully distributed and diverse 150-person team based in 16+ states and 23+ countries. In 2026, Donorbox was named by Built In as one of the Best Places to Work in Washington, DC.
🏅 Donorbox is rated the #1 software for fundraising, donor management, and nonprofit payment on G2 based on hundreds of verified customer reviews — a reflection of the care our team puts into building products that nonprofits trust.
The Team
You will be joining the Fundraising Team, one of the most highly visible and client-facing parts of our application. We are responsible for the Omnigive donation form—the absolute bread and butter of our company. Because this form is highly interactive and critical to our non-profits' success, we rely heavily on vanilla JavaScript on the frontend, powered by a robust Ruby on Rails backend. We operate with a flat hierarchy, a fully remote team, and a deliberate choice to keep our tech stack simple, reliable, and powerful.
The Role: Engineer II — The "Task Finder"
At Donorbox, our engineers in this role are what we call "Task Finders." At the Engineer II level, you own a feature end-to-end under review, surfacing the work the ticket didn't spell out — as we put it internally: "Given I was asked to do this, I'll also need to do that." We don't just hand you a ticket and expect you to act as a pure order-taker — you directly contribute to our team's goals for the year.
What You Will Do
-
Drive the Omnigive Form: Build and maintain complex, highly interactive UI components using vanilla JavaScript, while seamlessly connecting them to our Rails backend.
-
Apply the "Omakase" Mindset: Solve problems with the framework rather than around it. You will write idiomatic Ruby on Rails code using ActiveRecord, controllers, and ViewComponents.
-
Champion Product Sense: Analyze requirements through a "Jobs-to-be-Done" lens. Before writing new code, you will ask, "Can the user already do this?" and actively consider edge cases and error states.
-
Collaborate and Ship: Balance the desire to ship quickly with the need to ship quality. You will review peers' pull requests with care, communicate blockers proactively in async channels, and default to safely shipping value to users.
