Senior Product Owner / Senior Product Manager

Position: Senior Product Owner / Senior Product Manager

Location: Remote – Work from anywhere in the United States

Employment Type: Full-Time

Base Salary Range: $110k-$166k

Reports to: VP of Product

About Give Interactive

Give Interactive is a fintech software company providing technology solutions to community foundations and philanthropic organizations across North America. Our platform supports donor-advised funds, complex asset donations, investment operations, and grantmaking through modern automation, intuitive user experience, and robust analytics.

Our Mission

We exist to inspire and facilitate world-changing generosity.

Our Culture: The 3 C’s at Give Interactive

Our culture is built on three pillars that guide how we work and lead.

Character

Humility, integrity, ownership, respect, and assuming positive intent.

Commitment

Grit, growth mindset, ownership of outcomes, and a bias toward action.

Competence

Excellence, continuous learning, sound judgment, innovation, and mastery of craft.

Together, Character, Commitment, and Competence enable us to lead through innovation and win through execution.

Job Summary

We are hiring a Senior Product Owner / Senior Product Manager who can run a product lane with minimal oversight. This is not an entry point into product management. You'll take ownership of scope, prioritize and sequence work, and make sound decisions independently without needing frequent escalation. You should already be comfortable operating in Scrum/Kanban-style agile environments and in fixed-scope/waterfall, contract-driven delivery, and know how to shift between the two depending on what the work requires. Our platform sits in a regulated, high-stakes financial domain, so precision and accountability matter as much as speed.

Core Responsibilities 

• Requirements Analysis: Analyze client requirements, understand actual client workflow (not just what's asked for), and compare against similar client requests and existing system features. Know when a request is a one-off versus a pattern worth building into the platform.
• Product Planning & Architecture: Make product architecture decisions with real tradeoff awareness (build vs. defer, one-off vs. platform feature, technical debt vs. shipping now) while building a scalable platform for all clients.
• Documentation: Write user stories, feature specifications, system diagrams, wireframes, API documentation, and acceptance criteria clear enough for a developer to pick up without repeated follow-up meetings.
• Testing & Sign-off: Participate in product testing and sign off on user story completion. This requires understanding the underlying data and business logic well enough to catch a wrong result, not just checking a box.
• Underlying Needs Knowledgebase: Maintain and evolve the knowledge base for your lane, keeping user stories grounded in the real problems clients are trying to solve, not surface-level feature requests.
• Roadmap Ownership: Maintain the roadmap for your lane based on client feedback and market trends, balancing short-term needs against long-term strategy.
• Stakeholder Coordination: Work closely with clients and internal stakeholders to manage expectations and drive alignment and buy-in on prioritization decisions.
• Risk Mitigation: Proactively identify and address risks and roadblocks before they affect delivery timelines.
• Performance Tracking: Monitor relevant KPIs and metrics to evaluate the success of product initiatives.
• Represent the product: You're the go-to person for your lane. When stakeholders have questions about it, you have answers, or you know exactly who does and chase them down.
• Proactive problem-finding: Don't wait to be handed a ticket or told something's wrong. Actively look for gaps, risks, and opportunities in your product area before they become someone else's fire drill.
• Follow-through to done: Taking the ball means carrying it all the way to done, through ambiguity, blockers, and other teams' slow responses, rather than stopping at the first handoff point.
• Applied AI: Comfortable leveraging AI tools, agents, plugins, and automations to work faster and more effectively, treating them as accelerants, not replacements for your own judgment. You own the output: you understand it, can defend it, and are accountable for its quality, whether AI touched it or not. No deep AI background required, just curiosity, a willingness to learn, and a habit of continually finding new ways to apply it.

Domain Expertise We Need

• Strong working knowledge of accounting principles: general ledger, journal entries, reconciliation, and fund accounting concepts. You don't need to be a CPA, but you need to be able to read a trial balance and explain why a debit landed where it did.
• Hands-on experience with accounting or financial software/systems (ERP, GL systems, fund accounting platforms) is highly preferred.
• Fund management or donor-advised fund (DAF) experience is a strong plus.
• An analytical mindset: comfortable with math, data models, logic trees, and workflow mapping. You should be able to trace a calculation through a system and explain it clearly to both an engineer and a client.

Working With Engineering

• Genuinely technical: comfortable reading SQL, an API spec, or a system diagram, and able to trace how data flows through the platform without needing an engineer to translate it for you. You don't need to write production code, but you need to hold your own in a technical conversation.
• Years of experience building genuine, trust-based working relationships with developers and engineers, not just handing over requirements.
• Enough technical fluency to understand tradeoffs (data model changes, technical debt, test coverage) and negotiate scope credibly.
• Comfortable being told "no" by engineering and working through the actual constraint together rather than escalating immediately.

The Soft Skills We Can't Teach

• Empathy for other teams: a real understanding of how engineering, QA, support, sales and implementations do their jobs, and the constraints they carry that you don't.
• Self-direction: you find the ambiguity, ask the right question of the right person, and move without waiting for a fully-formed task.
• Self-directed learning: you grok the platform on your own, digging into documentation, poking around in the system, and asking the right questions, rather than waiting to be walked through it.
• Judgment under incomplete information: most client requests don't arrive with clean requirements. You know what to ask, what to assume, and when to flag risk.
• Directness paired with tact: comfortable pushing back on a client, stakeholder, or engineer when something doesn't add up, without burning the relationship.
• Follow-through: decisions get written down and closed out, not lost.

Key Qualifications

• Minimum 7-8 years of experience as a Product Owner/Product Manager, with at least 3 years in fintech, accounting tech, or another complex, regulated domain.
• Proven track record of writing product requirements and user stories that hold up once engineering starts building.
• Familiarity with the user story development framework.
• Deep comfort with Agile methodologies, plus the flexibility to operate in fixed-scope/waterfall, contract-driven delivery when that's what a client engagement requires.
• Startup or scale-up experience is a strong plus: comfortable with ambiguity, thin process, and building the plane while flying it.
• Bachelor's degree in Business, Accounting, Computer Science, Engineering, or a related field preferred, not required.

Compensation & Hours

• Flexible schedule with remote work
• 100% Medical Insurance Premiums paid for Employee-Only Coverage (High-deductible health care plan)
• Paid Time Off (Unlimited PTO policy for full-time employees, with manager approval)
• Short-Term & Long-Term Disability Insurance
• Employer Match 401(k) Contributions
• All equipment needed for the job is provided by the company

Application Process

1. Resume Review 

• Our team will review your resume to assess qualifications. 

2. Screening Interview 

• An introductory interview to discuss your background, experience, and interest in the role.

3. Hiring Manager - Part One

• A brief conversation to discuss your background and answer initial questions.

4. Hiring Manager - Part Two

• A deeper dive into your experience, skills, and role alignment. 

5. Assessment (Potential)

• You may be asked to complete a short, role-relevant assignment or exercise. This step will be included only if the hiring team determines it is needed.

6. Team Interview 

• Meet with at least two team members to get a sense of collaboration and culture. 

7. Final Offer Call 

• If selected, we’ll extend an offer and discuss next steps. 

Applicants must be legally authorized to work in the United States. This position is not eligible for employer‑sponsored work authorization. Candidates must not require current or future sponsorship to work in the United States.  We hire anyone who is permanently authorized to work in the U.S. without sponsorship.