Senior Software Engineer, Integrations
14 hours ago
New York, NY, United States
Givebutter
Full-time
Free with email or Google
Save this job and keep your search organized
Create a free account to save jobs, create alerts and return to this listing from your dashboard.
Free with email or Google
By continuing, you agree to our Terms & Privacy Policy.
Senior Software Engineer, Integrations
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." We want to hear from people who… 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 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 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 have 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 More About Givebutter
Benefits Remote Work:
Work remotely from one of our 10 hubs (Austin, Denver, Indianapolis, Los Angeles, San Francisco, New York, Salt Lake City, Minneapolis, Seattle, and Nashville). Health Insurance:
We offer Medical, Dental, and Vision insurance covered 100% for employees as well as HSA and FSA accounts. Dependent Care Coverage:
We offer coverage for dependents, with 50% of Medical, Dental, and Vision premiums covered for all eligible dependents. Mental Health:
Givebutter health insurance plans come with access to a TalkSpace membership. 401k:
We offer a 3% 401k match for all eligible employee's. Vacation and Holidays:
Givebutter offers a Flexible PTO policy with uncapped vacation days and company-recognized holidays. Wellness Week:
Givebutter closes for one week each summer to prioritize rest and recharge for the entire team. Parental Leave:
We offer 12 weeks of paid leave for all parents and comprehensive leave planning management through Aidora. Family Care Support:
Access a company-paid UrbanSitter membership plus care credits to bo
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." We want to hear from people who… 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 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 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 have 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 More About Givebutter
Benefits Remote Work:
Work remotely from one of our 10 hubs (Austin, Denver, Indianapolis, Los Angeles, San Francisco, New York, Salt Lake City, Minneapolis, Seattle, and Nashville). Health Insurance:
We offer Medical, Dental, and Vision insurance covered 100% for employees as well as HSA and FSA accounts. Dependent Care Coverage:
We offer coverage for dependents, with 50% of Medical, Dental, and Vision premiums covered for all eligible dependents. Mental Health:
Givebutter health insurance plans come with access to a TalkSpace membership. 401k:
We offer a 3% 401k match for all eligible employee's. Vacation and Holidays:
Givebutter offers a Flexible PTO policy with uncapped vacation days and company-recognized holidays. Wellness Week:
Givebutter closes for one week each summer to prioritize rest and recharge for the entire team. Parental Leave:
We offer 12 weeks of paid leave for all parents and comprehensive leave planning management through Aidora. Family Care Support:
Access a company-paid UrbanSitter membership plus care credits to bo