Senior Software Engineer, Online Giving (General Interest)

Location: United States

Department: 500 Eng

A note on this posting

This is a general-interest posting for the Online Giving team. We hire for this team on a rolling basis, so we may not have a seat open the day you apply. We review every application, and when a role opens that matches your experience, well reach out. If youre a strong fit for an open role now, well move quickly.

About the team

Every donation that moves through the GiveCampus platform passes through Online Givings code. The team owns the giving experience itself—mobile-first Giving Forms and Giving Pages, recurring giving, Memberships, and the campaign tools schools use to run giving days and year-round fundraising—and the payments layer underneath it: card, ACH, and Digital Wallets across Stripe, Spreedly, and PayPal.

Its full-stack work where correctness genuinely matters. Donations have to balance to the penny, a schools finance office reconciles every deposit, and a conversion improvement on a giving form turns directly into dollars for scholarships, programs, and facilities.

As our Partner base and giving volume grow, payments is becoming a bigger share of this teams work. We expect to hire engineers who can go deep on payment infrastructure—processing, recurring billing, payouts and deposits, reconciliation, and risk—alongside engineers who focus on the donor and admin experience. This posting covers both.

Online Giving is one of our cross-functional product teams in Engineering. We run one-week sprints and ship to production multiple times a day.

What you might work on

Depending on the teams priorities and your strengths, youll take on work like:

Payments and money movement

• Moving payment flows onto modern processor APIs, including our ACH migration to current Stripe APIs.
• Building and hardening one-time, recurring, and membership payments with idempotency, retries, and webhook handling that hold up under giving-day traffic.
• Making payouts, deposits, and reconciliation reliable and explainable, so a schools finance team can trace every dollar from donor to bank account.
• Reducing failed and declined payments, handling disputes and refunds cleanly, and helping us spot fraud and card testing early.
• Keeping our payments footprint secure and compliant as we add processors and payment methods.

Giving experience and campaign tools

• Building donor-facing Giving Forms and Giving Pages with a focus on conversion, accessibility, and mobile-first design.
• Shipping our new block-based, API-driven campaign builder and growing Memberships.
• Bringing personalization like Smart Ask Amounts into the giving flow, so schools can ask each donor for the right amount.

Across the team

• Owning projects end to end: architecture, code, automated tests, deployment, and support in production.
• Partnering with your pods Product Manager, Designer, and fellow engineers to turn Partner needs into technical plans you can ship incrementally.
• Joining a team-based support rotation and a paired 24/7 on-call rotation, including payment and deposit reconciliation, recurring-gift issues, and Partner configuration requests.
• Mentoring engineers earlier in their careers and helping us keep improving how we build and how we hire.

Successful outcomes

• Payments you can trust on the busiest day of the year. Giving days spike traffic for hours at a time, and your flows process every gift once, recover from processor hiccups, and alert the team before a Partner notices.
• Money that reconciles. Every gift, fee, refund, and payout lines up from the donors receipt to the schools deposit, and support tickets about missing or mismatched funds go down.
• Forms that convert. Changes you ship to giving forms and checkout move completion rates in the right direction, and you can show the numbers.
• Systems the team can grow on. You leave payment and giving code better documented, better tested, and easier for the next engineer to change.

What were looking for

Required

• 6+ years of hands-on, production software development.
• Full-stack proficiency: a modern front-end framework (React or Vue.js) plus a backend language and framework (Ruby on Rails, Node.js, Python, or similar).
• Strong SQL and data modeling skills, with a real concern for data integrity.
• System design experience, with a focus on solutions you can ship incrementally while keeping an eye on scale and resilience.
• RESTful API design and experience integrating with third-party services you dont control.
• A test-driven mindset and sharp debugging instincts, including in production.
• Startup-ready ownership: youre comfortable with ambiguity, set your own direction, and carry work from idea through maintenance.
• Clear written communication for a distributed team.

Strongly preferred

• Payments experience: Stripe or a comparable processor, ACH, card networks, digital wallets, webhooks, idempotency and retries, disputes and refunds, and reconciliation. This is the single strongest signal for this team.
• Experience with Ruby on Rails and RSpec.

Bonus points

• Payouts, ledgers, or double-entry accounting systems.
• Fraud prevention, risk scoring, or PCI scope reduction.
• Running more than one payment processor, or migrating between processor APIs.
• High-conversion consumer checkout or donation flows.
• Experience on a fundraising, crowdfunding, fintech, or e-commerce product.
• Postgres performance tuning, caching, or triaging stability issues at scale.
• Experience making coding agents a reliable part of a teams workflow.

Levels

We hire for this team at IC4 and IC5. At IC4, youll own major features and payment flows with design input from the team. At IC5, youll own the architecture of a system end to end, set technical direction for the pods roadmap, and mentor others—and theres room to step into a Tech Lead role. If youre not sure which fits, apply and well figure it out together.

Our stack

• Ruby on Rails and React
• Postgres and Redis
• Stripe, Spreedly, and PayPal for payment processing
• AWS with ArgoCD and Kubernetes for hosting and application management

How the team works

• You sweat the details where money is involved, and youd rather prove a fix with a test than hope it works.
• You think about how every decision lands for donors, school administrators, and the finance staff reconciling the books.
• 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.

GiveCampus is not able to sponsor employment visas for this role.