Technical Product Manager (OTE $70,000/year USD), @Sparkrock Finance

Role overview

Technical Product Manager owning the end-to-end technical direction of Sparkrock’s Finance ERP. You’ll define product vision and technical architecture for mission-driven customers in the Non-Profit and K-12/Education sectors, partnering with engineering, QA, customers, and go-to-market to deliver reliable, compliant financial systems.

Responsibilities

• Finance domain ownership: Own product and technical design for core capabilities such as:
  • General Ledger, AP, AR
  • Budgeting, fund/grant accounting
  • Reporting and integrations
• Requirement discovery & analysis: Translate finance business needs into clear functional and technical requirements with customers and implementation partners.
• Solution & architecture design: Design scalable, secure, and compliant solutions, including workflows, integrations, data models, and APIs.
• Cross-functional collaboration: Work with engineering, QA, implementation, and customer success to ensure solutions are feasible, maintainable, and aligned to product vision.
• Documentation & specifications: Produce detailed specifications, diagrams, and decision records.
• Technical validation & risk management: Evaluate trade-offs to ensure accounting correctness, performance, auditability, and compliance.
• Release readiness: Drive production readiness with rollout plans, documentation, and stakeholder communication.

Requirements

• Bachelor’s degree in Computer Science, Software Engineering, or related field.
• 5+ years in software (e.g., technical consultant, architect, developer, or solution designer).
• 2+ years as a Technical Product Manager (or similar role).
• Proven experience building ERP Finance or large-scale financial systems.
• Strong understanding of ERP finance concepts including:
  • General Ledger, AP/AR
  • Budgeting/forecasting
  • Fund/grant accounting
  • Financial reporting and audits
  • Non-profit financial workflows
• Experience designing scalable, secure backend systems.
• API and integration design (e.g., REST and event-driven systems).

Nice-to-haves

• Not explicitly stated in the provided text.