About GiveCampus

GiveCampus is the world's leading fundraising platform for non-profit educational institutions, trusted by millions of donors and over 1,300 colleges, universities, and K-12 schools. Our mission is to advance the quality, affordability, and accessibility of education. We are on track to facilitate $100 billion in charitable giving over the next decade.

Backed by leading investors including Y Combinator, GiveCampus practices Sustainable Growth, having made the Inc. 5000 list of America's fastest-growing private companies for five consecutive years and been profitable nine of the last ten. In 2025, we celebrated a $140 million growth investment that included a major liquidity event for GiveCampus employees—the second in less than three years.

Our purpose-driven team of 130+ is located in 30+ states across the U.S., with team members working from anywhere they choose. We have a 12,000 sq ft office in Washington, DC available for optional use, and we regularly organize team meet-ups, partner institution visits, and retreats in various locations.

While operating at meaningful scale, we are still growing rapidly to meet commercial and social good opportunities, including a $100 million investment in AI product development. Every employee plays a meaningful role in shaping our future. If you believe in the transformative power of education and want to join a fast-growing, mission-driven company, you'll fit right in.

Location: This is a remote-first role based in the U.S. While we embrace flexible, distributed work, we also value in-person connection. Team members are expected to attend multiple company-wide and team-specific onsites throughout the year.

About the Role

Everything GiveCampus builds relies on school data, and connecting this data is currently the top reason for launch delays. Our AI tools like GC Intelligence (donor prediction, outreach drafting), Smart Ask Amounts (suggested ask amounts), and GC Gift Officer (fundraiser relationship management) all require a school's full donor history.

This data must flow seamlessly between GiveCampus and the school's CRM, where their advancement office (fundraising and alumni relations team) manages donor, gift, and interaction records. Currently, only a fraction of our Partner schools send us complete data, and closing this gap is a significant growth lever for the company.

The Advancement Services team owns this critical data flow. We connect GiveCampus to various school CRMs, primarily Blackbaud Raiser's Edge NXT and Salesforce-based systems such as Ascend and Affinaquest. We also manage the API used by schools and software partners for data exchange, the guided data importer for file uploads, and a new queue-driven pipeline on AWS designed to handle tens of millions of records.

We are hiring two Senior Software Engineers to build this pipeline and the bidirectional integrations that run on it. You will design solutions for challenges such as preventing duplicate gifts from redelivered messages and managing CRM rate limits (e.g., 10 requests per second). You will also help define how the team builds with AI agents, including developing checks, context files, and guardrails to ensure data integrity and security.

Given the team's small size and the broad scope, you will own significant pieces of the system from your first month. The code you ship will directly impact whether gifts made during critical fundraising events land correctly in a school's CRM on the same day.

You will collaborate closely with the Advancement Services Product Manager, Partner Success, Partner Operations, Data Science, and various CRM vendors and connector partners. The team operates on one-week sprints and deploys to production multiple times a day.

We're hiring at two levels:

• IC4: You will own major components of the pipeline and integrations, with design input from the team.
• IC5: You will own the architecture of a system end-to-end, guide the team's agentic engineering practices, and mentor others.

If you're unsure which level fits, please apply, and we'll determine it together.

Successful Outcomes

• A pipeline that holds up at scale: Design and ship AWS-based pipelines with idempotent consumers. Keep memory and database load bounded, throttling writes, budgeting connections, and keeping pipeline storage off the application database.
• Incremental syncs that stay correct: Runs pick up only what changed, using row hashing that holds up when batches run in parallel. Reconcile records arriving from file uploads, the API, Raiser's Edge NXT, and the GiveCampus app, including deletes, and handle rate limiting to prevent exhausting a CRM's request budget.
• Migrations with a fallback: Move schools onto new infrastructure by first proving parity with the old system, then cutting over with the old path ready. Everything ships as infrastructure as code, with deploy, recovery, replay, and monitoring included from the start.
• No silent failures: Every sync reports to Sentry and New Relic, ensuring the team identifies broken syncs before a school's advancement services director does.
• A partner API developers want to build on: Design versioned, documented endpoints that go through a beta period before general availability, enabling consultants and software partners to plan integrations effectively.
• An agentic practice the whole team uses: Write and maintain context agents read and build reviewed skills for repeated work like stacked PRs and support-ticket triage. Measure the impact of tooling changes and teach effective practices to the team.

What We're Looking For

Required

• Pipelines at real volume: 6+ years building and running production backend systems, including a distributed ETL or sync pipeline that moved tens of millions of records. You can explain how your consumers handled redelivery, backpressure, and replay.
• Third-party integration scar tissue: You've built against APIs you didn't control and handled authentication, token expiry during long pagination, rate limits, retries, and upsert semantics. You understand what breaks when the other system changes without warning.
• Careful data modeling: You think in external IDs, timezone-safe bulk writes, and safe schema changes to busy core tables. Data integrity is paramount because someone on the other end reconciles every record.
• Clear, written communication: You write design docs and PR descriptions that a distributed team can act on without a meeting, and you're comfortable explaining a sync failure to a school's IT staff.

Strongly Preferred

• AI-native, with receipts: You've made coding agents more reliable for a team by writing context files, building skills, or adding checks and evaluations. You can share an example of when you didn't trust an agent's output and the check you added afterward.
• Infrastructure you can operate: You ship on AWS (or an equivalent cloud) with infrastructure as code, and you've owned the deploy, monitoring, and on-call responsibilities for what you built.

Bonus Points

• Experience integrating with fundraising or nonprofit CRMs: Blackbaud Raiser's Edge NXT or its SKY API, Salesforce (including Ascend or Affinaquest), or school systems like Ellucian, Veracross, or Slate.
• Experience with Ruby on Rails and RSpec.
• You've built a public or partner-facing API product with OpenAPI documentation.
• You've worked in higher education advancement, nonprofit fundraising, or a nearby domain.

What You'll Learn Here

You don't need to know advancement data on day one. In your first 90 days, you'll learn Raiser's Edge NXT, the Blackbaud SKY API, and the Salesforce products we support. You'll also learn the building blocks of school fundraising data:

• Constituents: Anyone a school tracks, such as alumni, parents, and donors.
• Hard and soft credits: Who gave a gift, and who else gets recognized for it, like a spouse or a company that matched it.
• Recurring gifts and designations: Gifts that repeat on a schedule, and the fund each gift goes to, such as financial aid or athletics.
• Opportunities and assignments: Large gifts a fundraiser is working toward, and which fundraiser owns each donor relationship.
• Events: Reunions, galas, and other gatherings, along with who registered and attended.

You'll get to know our pipeline codebase and our tools (Metabase for reporting, New Relic, and the Rails console). If you come from another backend framework, you'll pick up Rails along the way.

Our Stack

• Ruby on Rails and React
• Postgres and Redis
• AWS, including SQS, Aurora, S3, and EKS
• REST APIs documented with OpenAPI, plus the Blackbaud SKY API, Salesforce, and other CRM APIs
• Sentry and New Relic for observability
• AI coding agents across the workflow, with shared context files, skills, and evaluations

How the Team Works

• You go deep on the other system's quirks. You'd rather read the SKY API changelog than guess at why a sync broke, and you want to know how a system got the way it is.
• You use AI agents by default and verify what they produce. You've built the checks that catch when they're wrong.
• You write it down. Design docs, PR descriptions, and incident notes that let a distributed team act without a meeting.
• Strong opinions, loosely held. You argue hard for your approach, then commit fully once the team decides.
• You care about the people on the other end: the advancement services staff reconciling every record, the fundraisers relying on the data, and the donors behind it all.