SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Givebutter is a nonprofit fundraising and CRM platform used by millions of changemakers. The company is certified as a Great Place to Work and is the #1 rated nonprofit software on G2 across multiple categories.
You will join the Growth pod as a Senior Software Engineer focused on Integrations. In this role, you'll own the space between Givebutter and the dozens of tools nonprofits already use—CRMs, accounting systems, volunteer platforms, AI assistants, and more. Your work will shape Givebutter's public API to be something builders and AI agents actually want to use, and you'll hold key partner surfaces as they grow.
Most of your work happens at the intersection of two systems: reading partner documentation, spiking to understand what breaks, sitting on calls with external engineers, and closing ambiguity to turn "maybe we could" into "here's how."
Key aspects of the role:
- Own one or more partner integration surfaces end-to-end, maintaining coherence as sales, success, and product evolve them
- Shape the public API as its audience grows to include AI agents building on behalf of nonprofits
- Spike, prototype, and de-risk new partnerships, including ones that require creative problem-solving
- Design and defend API contracts, webhook shapes, and data flows that will be built against for years
- Partner with an existing integrations lead and grow into shared ownership
- Act as a translator between Product, Growth, Marketing, and external partner engineers
The engineering culture emphasizes democracy of code (equal contributions valued), autonomy (minimal meetings, self-managed calendars), fully automated CI/CD, mission-driven work with inspiring nonprofits, peer ownership of production surfaces, and AI-native workflows using terminal-based agents like Claude Code daily.
Requirements:
- 4+ years shipping production backend services on a modern web framework
- Strong proficiency in PHP/Laravel, or adjacent framework fluency (Rails, Django, Spring experience transfers well)
- Deep familiarity with REST API design, HTTP semantics, and patterns that make APIs worth building against
- Solid SQL knowledge, specifically MySQL or comfortable with relational database trade-offs
- Experience building against real-world third-party APIs (not just pristine documentation)
- Comfortable designing async job workflows, queued work, and observable failure paths
- Strong instincts around OAuth, webhooks, and trust-boundary decisions for public API safety
- Active use of terminal-based AI development tools (Claude Code, Cursor, or similar) with clear review discipline
- Experience contributing to on-call rotation for production services
- Comfortable navigating an existing monorepo (PHP/Laravel backend)
Nice to have:
- Contributions to a public API you helped design (especially if it survived a v2)
- Built custom AI tooling, skills, or agent workflows beyond defaults
- Familiarity with AI agents consuming APIs on behalf of end users and opinions on legible API design for non-human callers
- Opinions on specification vs. implementation differences (OAuth variants, JSON:API vs REST, GraphQL, etc.)
- Nonprofit or mission-driven experience
