Lead Product Manager

Data is the foundation of everything GiveCampus is becoming. Our fastest-growing products—GC Intelligence, GC GO, personalized Outreach, Smart Ask—only deliver their value when a school's complete data is flowing into GiveCampus and back out to the systems they run their work in. Today, that flow is the single biggest thing standing between our 1,500+ Partner schools and the value we've promised them: integration friction is the number one blocker to going live, it shows up across every CRM and deal stage, and only a fraction of schools are sending us the full data our products are built to use. Closing that gap is one of the biggest growth and retention levers in front of the company.

We're hiring a Lead Product Manager to own data and integrations end-to-end—not just the roadmap, but the outcome: schools actually sending us their complete data, reliably, at scale. You'll be accountable for whether that number moves, and you'll drive everything required to move it on the product side: strategy, discovery, execution, shipping quality and velocity, reliability, activation and onboarding, and the third-party vendors and integrations that sit in the flow. You'll do it across a wide range of CRMs (Blackbaud RE NXT and BB CRM, Salesforce / Ascend, Ellucian, Veracross, Slate) and a wide range of schools—from a 2-person K-12 advancement shop to a 500-person university team. Engineering is one big input, and a critical one—but it isn't the whole job. The whole job is making the movement of data between GiveCampus and our Partners so seamless and trustworthy that adoption stops being gated on it.

You won't do that alone. Engineering is your closest build partner; Partner Success and Partner Operations live the integration pain with schools every day and are your eyes and ears in the field; Data Science helps you turn raw data into product value. And because no team could ever build every integration itself, you'll personally own a roster of external partners—CRM vendors, connector partners, and consultancies—whose roadmaps, sandboxes, and release cycles you'll learn to shape. Coverage is a team sport, and you're the captain of the technical side.

This is a PM role for someone who wants to operate like the GM of data and integrations, ship like a builder, and go deeper with users and their systems than anyone else at the company—on the phone with an Advancement Services director one hour, in a CRM's API docs the next. It's also a PM role for the AI-native era. You reach for AI across your entire workflow—research synthesis, data analysis, drafting, prototyping, experimentation, shipping—and you have a sharp point of view on where AI-enabled data transformation can move faster than waiting for a CRM's API to open up.

You'll report to the Head of Product, Platform and work in close partnership with Infrastructure Engineering, Product, Product Engineering, Partner Success, Partner Operations, Data Science, Marketing, Business Development, and Business Operations—plus the external CRM and connector partners whose roadmaps you'll help shape.

Successful Outcomes

• Complete data, flowing—the outcome that matters: The number you own is the share of schools sending us their complete data—not just the gifts we generate, but the full data set their CRM holds—on a regular cadence (the bar: ~90% of schools, at least once a month). Not a backlog. Not a velocity number. Not a feature list. If we ship a slick connector but schools don't trust it enough to turn it on, the number doesn't move and it doesn't count. You own the product half of that equation—and whatever else it takes across functions, vendors, and external partners to actually move it: activation, field mapping, migration, validation, the unglamorous reliability work that makes a connector trustworthy.
• Alliances for leverage and coverage: You can't build every integration yourself, and you shouldn't try. You build and own the partnerships—CRM vendors, connector partners, and consultancies (think Blackbaud / SKY API, Omatic, Kindsight, Huron, and the firms helping us build a Salesforce package)—that extend coverage far faster than building alone. You're comfortable that the other side's API, roadmap, and uptime are out of your hands, and you manage joint roadmaps, sandbox access, versioning, deprecation, and onboarding lead times like the leverage they are. Every alliance is a multiplier on how many schools we can reach and how fast.
• Insanely close to users and their CRMs: You know our Advancement Services and IT users—the people who actually move and manage the data—better than anyone else at the company, and you know their CRMs the same way. You're on a text-message basis with the operators running data at our schools, swapping notes on a Tuesday morning, showing up to watch them wrestle a giving-day import, taking them to lunch to hear what's broken. And you know the systems cold: the data models, where constituent records split in half, why a sync fails silently, what "low lift" actually means to an API-averse team. That depth is where you earn the authority to decide what we build—and the credibility to hold the line when the room gets loud.
• Builder mindset: You don't just write PRDs—you make things, and you do it with AI in your hands all day. AI runs across your full workflow: synthesizing user interviews, interrogating data, drafting specs, prototyping flows, generating experiments you can test in hours instead of sprints. You use AI-powered tools (Claude Code, Cursor, Lovable, Figma Make, v0, and whatever's best this month) to ship small fixes, internal utilities, and—increasingly—the AI-enabled data-mapping and transformation tooling that lets a school get its data flowing without waiting on a CRM's API. If you see a broken flow and can fix it, you open a PR; you don't file a ticket and wait. This doesn't require a CS degree. It requires initiative, taste, and a refusal to let solvable problems sit.
• Set the pace: Speed and urgency aren't a style choice; they're the job. You make decisions fast—80% right today beats 100% right next week. Nobody hands you a neat prioritized list; you see the full landscape, judge what matters most right now, and move between things—15 minutes here, a full day there, a late night when something can't slip. You set the tone for everyone around you, and that tone is fast.

Experience

• A track record of moving the number, not just shipping. Significant PM experience (typically 6+ years) owning complex data and integration products from 0-to-1 and through real scale in high-growth environments, with a tight execution loop behind you. You can name the outcomes you owned, not just the launches you led.
• Integrations and CRM scar tissue. You've built API and flat-file pipelines and bi-directional syncs—and you've been burned enough by what breaks (matching and dedup, gift semantics, ID mismatches, silent failures) to design around it. B2B SaaS required; hands-on with a major CRM (Blackbaud, Salesforce, or similar) strongly preferred.
• You've owned partners, not just used them. 2+ years managing technical partnerships—joint roadmaps, sandboxes, versioning, deprecation—and the discipline of depending on systems whose roadmap and uptime aren't yours to control.
• AI-native, with receipts. You've gone from idea to working prototype with AI-powered tooling, and ideally shipped a fix or app that solved a real problem—with the judgment to know when your hands on the keyboard multiply the team and when they distract.
• Discovery and data instincts. You've validated ideas with real users, you can tell a customer ask from a customer need, and you run your own analyses instead of waiting on someone to pull the query.
• Technical fluency with engineers. You hold your own on architecture, security, data modeling, and integration trade-offs because you understand them—and you can reason about a canonical data model and how it maps across incompatible CRMs.

Cultural Characteristics

• Dynamic, emerging leader who is better at listening than speaking
• Thrives in ambiguity, creates order in chaos, and consistently thinks two steps ahead
• Hands-on builder excited to go deep into technical requirements, user flows, and data—and to reach for AI or open a PR when that's the fastest path
• Operates AI-first by default—AI is in the flow across research, drafting, analysis, prototyping, and shipping; not bolted on as an afterthought
• Strong collaborator who will naturally work cross-functionally but is also comfortable operating independently
• Intensely curious, always pushing to understand why things are the way they are and how they got that way
• Operates with a sense of urgency, maintains a fast pace, always pushing for faster
• Holds themself and others to high standards; always pursues excellence
• Deep sense of ownership and accountability; low maintenance, low drama
• Comfortable with strong opinions, loosely held—advocates passionately, then commits fully once a decision is made
• Runs towards big, ambitious goals rather than away from them
• Passionate about advancing the quality, the affordability, and the accessibility of education
• Radical empathy for our Partner schools, the fundraisers doing the hard work, and the donors who want to make a difference