Senior Software Engineer, Integrations

Givebutter

2d•$170,000 - $185,000•Remote

About The Position

Givebutter is hiring a Senior Software Engineer, Integrations, to join their Growth pod. This role is responsible for determining how well Givebutter integrates with other tools that nonprofits use, such as CRMs, accounting software, and volunteer platforms. The engineer will shape the public API and partner surfaces to ensure they are user-friendly for builders and AI agents. The work involves reading documentation, testing integrations, and collaborating with external engineers to resolve ambiguities and build effective connections between systems.

Requirements

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)

Nice To Haves

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

Responsibilities

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