Senior Software Engineer, Integrations

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. 

Givebutter is hiring a Senior Software Engineer, Integrations, to join our Growth pod. Nonprofits live inside dozens of tools they already love: CRMs, accounting, volunteer platforms, AI assistants. This role decides how well Givebutter meets them there. You'll shape our public API into something builders and their AI agents actually want to reach for, and hold the partner surfaces we care about most as they grow with us.

Most of this work happens in the space between two systems: reading partner docs, spiking to see what breaks, sitting on calls with external engineers, closing the ambiguity that turns "maybe we could" into "here's how."

• Read someone else's API docs carefully, and know why the choices in them matter

• Care as much about the person calling the API as the person writing it

• Know that a good integration keeps a nonprofit inside the tools they already love, instead of dragging them into ours

• Spike, learn what breaks, and turn that into an engineering conversation without needing a project manager to translate

• Get on a call with a partner engineer and come out with less ambiguity than you started

• Take your development setup seriously (terminal, editor, agent) and have probably built one or two custom skills to make them work harder

• →

  Own one or more of our partner integration surfaces end-to-end, and hold them coherent as sales, success, and product shape them further

• →

  Shape our public API as its audience grows to include AI agents building on behalf of nonprofits who don't code themselves

• →

  Spike, prototype, and de-risk new partnerships, including the ones we don't yet know how to build, and the ones that only ship because someone had an aha moment

• →

  Design and defend API contracts, webhook shapes, and data flows that other engineers (and other agents) will build against for years

• →

  Partner with an existing integrations lead on the surfaces they hold today, and grow into shared ownership over time

• →

  Partner with Product, Growth, Marketing, and occasionally an external partner engineer, as a natural translator between what each group needs

Below is a high-level outline of our standard interview process

1. →

   Recruiter Screen: A 30-minute conversation to learn more about your background, walk through the role, and ensure mutual alignment on expectations, values, and logistics.

2. →

   Hiring Manager Interview: A deeper dive into your relevant experience, skillset, and working style. This is your first opportunity to connect directly with the person who may be your future manager.

3. →

   Assessment (technical or non-technical): This stage will vary based on the role. It could involve a live coding session, case study, or take-home project. Some roles may include two parts to this stage to evaluate both practical skills and problem-solving approaches

4. →

   Values Interview: A conversation with team members focused on how you align with our core values and leadership principles.

5. →

   References: We connect with a few folks you’ve worked closely with to get a better picture of your working style and impact.

6. →

   Offer: If all goes well, we’ll move to the offer stage!

Please note, we will have an AI note-taking tool join most of our interviews.

Hi potential new butterslice! A recent study from LinkedIn showed that most women apply to jobs only when they meet 100% of the requirements, whereas men will hit the apply button if they hit 60%. Givebutter is committed to building a diverse and inclusive team. So to the women and nonbinary folks out there feeling unsure if you're a perfect fit, we strongly encourage you to apply!

• 4+ years shipping production backend services, ideally on a modern web framework

• Strong proficiency in PHP / Laravel, or the kind of adjacent framework fluency that ramps quickly (we won't rule you out for having lived in Rails, Django, or Spring)

• Deep familiarity with REST API design, HTTP semantics, and the patterns that make an API worth building against

• Solid SQL, MySQL specifically or comfortable enough with another relational database to speak to the trade-offs you've made

• Experience building against real-world third-party APIs, not just the pristine documented examples

• Comfortable designing async job workflows, queued work, and observable failure paths

• Strong instincts around OAuth, webhooks, and the trust-boundary decisions that keep a public API safe and honest

• Active use of terminal-based AI development tools (Claude Code, Cursor, or similar) with a clear review discipline for what the agent produces

• Experience contributing to on-call rotation for production services

• Comfortable navigating an existing monorepo (ours is real, and PHP / Laravel is most of the backend)

• Contributions to a public API you helped design (bonus if it survived a v2)

• You've built your own AI tooling, custom skills, or agent workflows, not just used the defaults

• Familiarity with the emerging surface where AI agents consume APIs on behalf of end users, and opinions about what a legible API looks like to a non-human caller

• You have opinions about the difference between a specification and an implementation (OAuth 1 vs 2, JSON:API vs REST, GraphQL and what came after: any of it, all of it)

• Nonprofit or mission-driven experience

Benefits