Staff Engineer

Company Description

Givebutter is the most-loved nonprofit fundraising and CRM platform, empowering millions of changemakers to raise more, pay less, and give better. Nonprofits use Givebutter to replace multiple tools so they can launch fundraisers and events, use donation forms and donor management (CRM), send emails and text blasts—all in one place. Use of the Givebutter platform is completely free with a 100% transparent tip-or-fee model.

Givebutter has been certified as a Great Place to Work® every year since 2021, and is the #1 rated nonprofit software company on G2 across multiple categories.

Our mission is to empower the changemaker in all of us. We believe giving should be fun, so you’ll want to do it again, and we also believe that work should be fun, so that you’ll have the greatest impact. We are excited to hear from talented people who want to work with other talented people in making the world a butter place—and have fun along the way. 

Role Description

We're hiring a Staff Software Engineer to help build and evolve the systems that keep Givebutter safe, fraud detection, risk decisioning, abuse prevention, and the internal tooling our operations team needs to investigate and act at scale. This is a hands-on individual contributor role. You'll write code, design systems, debug production issues, and release new features. You'll also have the opportunity to work closely with stakeholders across the company to help set the technical direction for Trust & Safety, and partner teams throughout Givebutter to prioritize and execute on it.

You’ll work day-to-day on our Payments and Trust & Safety team and collaborate closely with our engineering, operations, product and leadership team to solve ambiguous risk challenges into concrete solution.

This role spans the full breadth of how we fight fraud, from building decision systems and investigation tools to hardening our payment infrastructure and working with operations on process. It's as much about understanding the business as it is about writing great code.

Why join the Givebutter Engineering team?

• Democracy of code – We value equal contributions from all engineers and foster an environment of open discussion on architecture and ideas.

• Autonomy in work – We keep meetings to a minimum. Engineers have the freedom to manage their own calendars and block out uninterrupted time for focused work.

• Automated CI/CD – Our build and deployment processes are fully automated and hands-off, allowing engineers to focus on problem-solving through code.

• Mission-driven, full stop – You’ll be working with inspiring nonprofits, charities, and organizations that are making a positive impact around the world.

What You’ll Do

• Build the fraud platform. Design and implement fraud detection and risk decisioning systems, rule engines, scoring pipelines, event-driven risk signals, and backtesting infrastructure.

• Build for operators. Create investigation and review tooling that helps our Trust & Safety operations team triage, investigate, and resolve cases efficiently. You care as much about internal UX as external.

• Help shape what we build next. You'll work closely with your manager, product, operations and leadership stakeholders to identify where we're exposed, propose solutions, and help prioritize the roadmap. Your domain expertise matters here — we want your perspective on what we should be doing.

• Think like an adversary. Develop a deep understanding of fraud vectors in the fundraising and payments space: stolen cards, synthetic identities, friendly fraud, campaign abuse, and help us build systems that adapt as threats evolve.

• Strengthen payment integrity. Work across our payment systems to harden the transaction lifecycle against abuse. You don't need to be a payments expert on day one.

• Mentor and grow the team. Help engineers on your team develop Trust & Safety domain expertise. Share what you know, pair on hard problems, and help raise the bar for how the team approaches adversarial challenges.

Requirements

• 8+ years of software engineering experience, with meaningful time spent in adversarial domains — fraud, trust & safety, risk, abuse prevention, or similar.

• Experience building fraud detection or risk decisioning systems — rule engines, scoring systems, policy frameworks, or investigation platforms. You've built the thing, not just consumed the output