Senior Software Engineer, Advancement Services

GiveCampus

13h•Remote

About The Position

GiveCampus is hiring two Senior Software Engineers for its Advancement Services team. The team builds and operates the data flows connecting GiveCampus to the customer relationship management (CRM) systems used by educational institutions, including Blackbaud Raiser's Edge NXT and Salesforce-based systems such as Ascend and Affinaquest. Its work also includes a partner API, a guided data importer, and a new queue-driven AWS pipeline designed to process tens of millions of records. The engineers will build the pipeline and bidirectional integrations, designing for message redelivery without duplicate records and for CRM rate limits. They will help establish how the team uses AI agents, including maintaining agent context, creating reusable skills and checks, and protecting sensitive donor data. Engineers will own substantial areas of the system early on, with work that affects whether school gifts are correctly reflected in CRMs the same day. The role collaborates with the Advancement Services Product Manager, Partner Success, Partner Operations, Data Science, CRM vendors, and connector partners. The team works in one-week sprints and deploys to production multiple times a day. At IC4, the engineer owns major pipeline and integration components with design input from the team. At IC5, the engineer owns end-to-end system architecture, guides agentic engineering practices, and mentors others. GiveCampus is a mission-driven education fundraising company with a distributed team of more than 130 people in over 30 U.S. states. This is a U.S.-based remote-first role. Team members are expected to attend multiple company-wide and team-specific onsite events during the year; the company's Washington, DC office is available for optional use.

Requirements

At least 6 years of experience building and operating production backend systems.
Experience with a distributed ETL or synchronization pipeline that moved tens of millions of records.
Ability to explain how pipeline consumers handled message redelivery, backpressure, and replay.
Experience integrating with third-party APIs, including handling authentication, token expiration during long pagination, rate limits, retries, and upsert semantics.
Careful data modeling skills, including working with external IDs, timezone-safe bulk writes, and safe schema changes to busy core tables.
Clear written communication, including design documents and pull request descriptions for distributed teams.
Ability to explain synchronization failures to a school's IT staff.

Nice To Haves

Experience improving coding-agent reliability for a team through context files, reusable skills, checks, or evaluations.
Experience shipping on AWS or an equivalent cloud using infrastructure as code, and owning deployment, monitoring, and on-call operations.
Experience integrating with fundraising or nonprofit CRMs, including Blackbaud Raiser's Edge NXT or its SKY API, Salesforce, Ascend, Affinaquest, Ellucian, Veracross, or Slate.
Experience with Ruby on Rails and RSpec.
Experience building a public or partner-facing API product with OpenAPI documentation.
Experience in higher education advancement, nonprofit fundraising, or a related domain.

Responsibilities

Design and ship AWS-based pipelines with idempotent consumers, bounded memory and database usage, throttled writes, managed connection budgets, and pipeline storage separate from the application database.
Build correct incremental syncs using row hashing that remains reliable when batches run in parallel.
Reconcile records from file uploads, the partner API, Raiser's Edge NXT, and the GiveCampus application, including deletions.
Handle CRM rate limits so individual jobs do not exhaust a system's request budget.
Migrate schools to new infrastructure by verifying parity with existing systems before cutover and retaining a fallback path.
Deliver infrastructure as code with deployment, recovery, replay, and monitoring capabilities.
Ensure syncs report to Sentry and New Relic so failures are visible to the team.
Design versioned, documented partner API endpoints and manage beta periods before general availability.
Maintain agent context and create reviewed reusable skills for work such as stacked pull requests and support-ticket triage.
Measure the effectiveness of AI tooling changes and share useful practices with the team.
Collaborate with product, partner-facing teams, data science, CRM vendors, and connector partners.
At the IC5 level, own end-to-end system architecture, guide the team's agentic engineering practices, and mentor colleagues.