Product Manager, Financial Systems

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About SoftPro (company description) maybe "About the role"? Actually "About SoftPro" is company description; we could treat as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the Equal Opportunity Employer paragraph and maybe the "Join Us and Live Our Core Values" part? That's not boilerplate but maybe considered values; but we can keep if substantive. However we need to follow headings. We need to parse content: - About SoftPro: description of company, mission, HQ, Why Join SoftPro? Benefits list. - What are we looking for? (role description) - includes role summary. - What will I do as a Product Manager at SoftPro? (Responsibilities) broken into sub-sections: Product Strategy & Vision, Product Discovery, Product Delivery, Banking & Financial Integrations, Compliance & Risk, Analytics & Reporting. - What will I need to be successful as a Product Manager at SoftPro? (Required Qualifications, Preferred Qualifications, Success Metrics (First 12 Months), Desired Leadership Characteristics) - Why You’ll Love Working Here (maybe Skills? Actually it's about culture). Could be "Benefits"? Already have benefits earlier. - Ready to Make an Impact? (call to action) - maybe application instruction, we should remove. - Join Us and Live Our Core Values (list of values) - could be considered "Skills"? Not exactly. Might be considered "Skills" or "Qualifications"? Probably we can treat as "Skills" or maybe omit as it's fluff but still substantive? The instruction: Prefer a few substantive sections over many thin ones. We could combine values into a "Skills" or "Qualifications"? But better to include a section "Skills" if there is specific content: they list core values: Deliver AMAZING Customer Service, Be an AWESOME Teammate, Adopt a Sense of Urgency, Innovate to be Efficient, Produce Quality Work, Take Initiative, Go the Extra Mile. Those are more like behavioral competencies, could be under "Skills". We'll include a Skills section. - Benefits: Already listed under Why Join SoftPro? Comprehensive Benefits, Financial Wellness, Generous Paid Time Off, Flexibility. Also Award-Winning Culture. So we can have Benefits section. - Pay: Not mentioned. So we should NOT include Pay section. - Schedule: Not mentioned explicitly (maybe hybrid/remote). There is mention: "The position can be in our Raleigh, NC office (hybrid), or fully remote. If remote, you must be able to work East coast hours and be willing to travel to our Raleigh NC headquarters up to 5 times per year for defined events." That's schedule/location info. Could be under Schedule section. Since they mention hybrid/remote and travel expectations, we can include Schedule. Thus sections: About the role (maybe company overview + role summary), Responsibilities, Requirements (maybe combine Required Qualifications), Qualifications (maybe Preferred Qualifications?), Skills (core values), Benefits, Schedule. But we need to avoid duplication. Let's map: - About the role: Could include "What are we looking for?" summary: SoftPro is seeking an experienced Product Manager to lead the strategy, design, and delivery of a cloud-native SaaS Bank Reconciliation Platform. Also location/hybrid/remote details? Might be better in Schedule. But we also have "About SoftPro" company description. Could be part of About the role? Might be okay. Better: Use About the role for role summary and maybe company context. Use Responsibilities for the detailed duties (Product Strategy & Vision etc). Use Requirements for Required Qualifications. Use Qualifications for Preferred Qualifications. Use Skills for core values/leadership characteristics? Actually Desired Leadership Characteristics could be under Skills. Or we could have Skills for both core values and leadership characteristics. But we have also Success Metrics (First 12 Months) - maybe that's part of Requirements? Could be under Requirements as expected outcomes. But we could include a separate section "Success Metrics" but not in allowed headings list. The allowed headings are limited to those examples; we should not create other headings. So we need to fit Success Metrics into one of the allowed sections, maybe under Requirements or Qualifications. Probably under Requirements as "Expected outcomes". Or we could incorporate into Responsibilities? Not ideal. We could also treat Success Metrics as part of "Requirements" (what needed to be successful). But the posting already has "What will I need to be successful as a Product Manager at SoftPro?" which includes Required Qualifications, Preferred Qualifications, Success Metrics, Desired Leadership Characteristics. So we could split: Requirements = Required Qualifications + Success Metrics. Qualifications = Preferred Qualifications. Skills = Desired Leadership Characteristics + Core Values (Why You’ll Love Working Here? Actually that's about culture). But we need to preserve all substantive info. Let's extract each piece: Company description (About SoftPro): - SoftPro is nation’s leading provider of real estate closing and title insurance software. - Division of Fidelity National Financial (NYSE: FNF). - Technology solutions trusted by thousands of law firms and title companies. - Essential role in residential and commercial real estate transactions. - Headquarters in Raleigh, North Carolina. Why Join SoftPro? (Benefits): - Comprehensive Benefits: Medical, dental, vision, disability, and more - Financial Wellness: 401(k) with company match and Employee Stock Purchase Plan - Generous Paid Time Off: vacation, holidays, and parental leave - Flexibility: Some positions eligible for 100% remote work, plus hybrid options for those living near Raleigh HQ - Award-Winning Culture: SoftPro has received national recognition for outstanding customer service and innovative products. Named 2026 Best Place to Work by Triangle Business Journal—honor earned 14 times since 2012. What are we looking for? (role summary): - SoftPro seeking experienced Product Manager to lead strategy, design, delivery of cloud-native SaaS Bank Reconciliation Platform. - Responsible for defining/executing product vision for modern reconciliation solution automating matching, validation, exception management, reporting of financial transactions across multiple banking partners, payment networks, accounting systems. - Position can be Raleigh, NC office (hybrid) or fully remote. If remote, must work East coast hours and willing to travel to Raleigh HQ up to 5 times per year for defined events. What will I do as a Product Manager at SoftPro? (Responsibilities) broken down: Product Strategy & Vision: - Define and communicate product vision, strategy, roadmap, success metrics. - Develop multi-year product roadmap aligned with business objectives and market demands. - Identify market opportunities via customer research, industry analysis, competitive intelligence. - Serve as primary voice of customer throughout product lifecycle. Product Discovery: - Conduct customer interviews and workflow analysis with finance, treasury, accounting, operations teams. - Identify pain points in reconciliation processes: bank account reconciliation, ACH transaction reconciliation, wire transfer reconciliation, trust account reconciliation, payment exception management, general ledger balancing. - Translate customer needs into validated product requirements. Product Delivery: - Create and maintain product backlogs, epics, user stories, acceptance criteria. - Prioritize features based on customer value, regulatory requirements, business impact, technical feasibility. - Partner closely with engineering teams using Agile methodologies. - Participate in sprint planning, backlog grooming, release planning activities. Banking & Financial Integrations: - Drive product strategy for: Open Banking integrations, Bank APIs, ACH networks, Wire transfer networks, ERP and accounting platforms, Payment processors. - Define onboarding experiences for new financial institutions and customers. Compliance & Risk: - Partner with Compliance and Security teams to ensure adherence to: NACHA requirements, PCI-DSS standards, SOC 2 controls, Bank security requirements, Audit and reporting requirements. - Establish governance requirements for financial data management. - Analyze? Actually "Analytics & Reporting" separate. Analytics & Reporting: - Define KPI frameworks and dashboards for: Auto-match rates, Exception volumes, Reconciliation completion times, Outstanding variances, Customer adoption, Revenue growth. - Drive reporting and insights features that improve operational efficiency. What will I need to be successful as a Product Manager at SoftPro? (Required Qualifications): - Bachelor's degree in Business, Finance, Accounting, Computer Science, Information Systems, or related field. - 5+ years of Product Management experience. - 3+ years managing SaaS products. - Experience with financial technology (FinTech), banking, payments, treasury, or accounting platforms. - Demonstrated success leading software products from concept through deployment. - Strong understanding of Agile product development practices. - Excellent communication and stakeholder management skills. - Ability to translate complex business processes into scalable software solutions. Preferred Qualifications: - Experience with: Bank reconciliations, Treasury Management Systems, ERP integrations, ACH and Wire processing, General ledger accounting, Financial reporting platforms. - Familiarity with AI-assisted matching and exception management solutions. Success Metrics (First 12 Months): - Deliver MVP reconciliation platform on schedule. - Achieve targeted automated matching percentage. - Reduce manual reconciliation effort by defined customer benchmarks. - Increase customer adoption and retention metrics. - Successfully onboard initial banking integrations. - Deliver audit-ready reporting capabilities. - Maintain high customer satisfaction scores. Desired Leadership Characteristics: - Customer obsessed - Data-driven decision maker - Strong collaborator - Strategic thinker with hands-on execution capability - Comfortable navigating ambiguity in a startup-style SaaS environment - Skilled at influencing without authority - Passion for modernizing financial operations through automation Why You’ll Love Working Here: - Be part of a supportive, fun team that values innovation and collaboration. - Enjoy opportunities for professional growth and continuous learning. - Make a real difference by helping customers succeed with tools that power the real estate industry. Ready to Make an Impact? (call to action) - remove. Join Us and Live Our Core Values: - Deliver AMAZING Customer Service - Be an AWESOME Teammate - Adopt a Sense of Urgency - Innovate to be Efficient - Produce Quality Work - Take Initiative - Go the Extra Mile Equal Opportunity Employer boilerplate - remove. Now we need to map to headings. We have: - About the role: Could combine company description + role summary? Or we could have About the role = role summary (What are we looking for?). And maybe include company description in a separate paragraph before headings? The instruction says output only HTML fragment, no extra text outside headings? It didn't forbid extra paragraphs not under headings, but we should follow structure: use headings for sections. Could have an introductory

before first heading? Not prohibited but better to keep all content under headings. We could treat "About SoftPro" as "About the role" heading. Thus

About the role

then include paragraphs: company description and role summary. But we also have Benefits, which we can put under

Benefits

. Responsibilities under

Responsibilities

. Requirements under

Requirements

(maybe include Required Qualifications + Success Metrics). Or we could split Required Qualifications into Requirements and Success Metrics into something else but we don't have a heading for Success Metrics. So we put them together. Qualifications under

Qualifications

(Preferred Qualifications). Skills under