Product Manager Workflow Automation and Treasury Solutions
for each heading. Only include sections where there is real specific content. We must not repeat job title as heading. Must preserve all substantive info. Remove boilerplate like EEO, etc. Also remove application instructions, navigation, cookie, etc. The posting includes: Benefits list: Simple IRA with Matching, Bonus based on performance, Competitive salary, Dental insurance, Health insurance, Opportunity for advancement, Paid time off, Training & development, Vision insurance, Wellness resources.
Also there is a "Compensation: $111, 411 to $144,000 annually". Also "FINBOA offers medical, dental, and vision coverage; a 401(k) plan with company match; paid time off; and additional voluntary benefits." That's overlapping with benefits. We need to preserve all substantive info; we can combine but not lose details.
We need sections: Benefits (list), Pay (compensation), Schedule (Typical business hours, Monday through Friday), maybe About the role (the description of role), Responsibilities (the "What You’ll Do" bullet list), Requirements/Qualifications/Skills (the "What You’ll Bring" list). Also maybe "Position Details" includes Employment Type, Work Location, Approved States, Travel, Incentive Eligibility. Could be part of About the role or separate. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some.
We need to decide which sections to include based on content.
- About the role: we have a paragraph describing role: "FINBOA is seeking an experienced Product Manager to lead the strategy, roadmap, and market success of our workflow automation, treasury onboarding, intelligent intake, and AI-enabled solutions. In this role, you will help shape FINBOA’s next generation of products, enabling financial institutions to streamline operations, reduce manual effort, and accelerate digital transformation. You will work closely with Engineering, Product Marketing, Sales, Solutions Consulting, and customers to turn complex operational needs into valuable, scalable solutions." That's substantive.
- Responsibilities: the "What You’ll Do" list (multiple bullet points). Use - .
- Requirements: maybe combine "What You’ll Bring" list (experience, skills). Could be Requirements or Qualifications. We need to decide: The list includes experience, knowledge, skills, tools, preferred experience. Could be Requirements (mandatory) and Qualifications (preferred). But we can just have one Requirements section with all. However we have headings for Requirements, Qualifications, Skills. We could split: Requirements = mandatory experience (5+ years product management, owning strategic roadmaps, etc). Qualifications = preferred (Treasury management, AI-enabled products, supporting banks). Skills = tools (Jira, Azure DevOps, Confluence) and analytical etc. But we need to avoid filler headings. We must only include sections if there is real specific content. We have content for each.
Let's parse "What You’ll Bring":
- Five or more years of product management experience in SaaS, fintech, banking technology, or a related field.
- Experience owning strategic roadmaps for technically complex products.
- Strong knowledge of workflow automation, process improvement, and operational efficiency.
- Experience creating product requirements, user stories, and acceptance criteria.
- A solid understanding of Agile methodologies and the software development lifecycle.
- Strong analytical, problem-solving, communication, and stakeholder-management skills.
- Experience using tools such as Jira, Azure DevOps, or Confluence.
- Treasury management or banking operations experience is strongly preferred.
- Experience with AI-enabled products is preferred.
- Experience supporting banks, credit unions, or other community financial institutions is a plus.
We could categorize:
Requirements (mandatory): first six bullet points (experience, roadmap, knowledge, requirements, Agile, analytical skills). Qualifications (preferred): Treasury management, AI-enabled, supporting banks. Skills: Experience using tools such as Jira, Azure DevOps, or Confluence (maybe also analytical etc but we already used). Could also include strong analytical etc as Skills. But we need to avoid duplication.
Simplify: Use Requirements for the list of experience/knowledge/skills (including analytical etc). Use Qualifications for preferred experience (Treasury, AI, supporting banks). Use Skills for tools (Jira, Azure DevOps, Confluence). That seems reasonable.
Now Benefits: we have list. Also note "FINBOA offers medical, dental, and vision coverage; a 401(k) plan with company match; paid time off; and additional voluntary benefits." This overlaps with benefits list. We'll combine into Benefits section: list items: Simple IRA with Matching, Bonus based on performance, Competitive salary, Dental insurance, Health insurance, Opportunity for advancement, Paid time off, Training & development, Vision insurance, Wellness resources, Medical insurance, 401(k) plan with company match, Additional voluntary benefits. Ensure we don't duplicate: we already have dental, health, vision, paid time off. Add medical, 401(k), additional voluntary benefits.
Pay: we have compensation range: $111,411 to $144,000 annually. Also mention "Incentive Eligibility: Eligible for an annual bonus". Could be part of Pay or Benefits. Since we have Benefits already includes Bonus based on performance. But we can still include Pay section with salary range and note annual bonus eligibility.
Schedule: "Typical business hours, Monday through Friday". Also "Work Location: Remote within a FINBOA-approved state". Also "Approved States: ...". Also "Travel: Occasional travel may be required". Also "Employment Type: Full-time, exempt". Could be part of About the role or separate. But we have Schedule heading; we can put typical business hours. Also we could include Work Location etc under About the role? But we need to preserve all substantive info. We could add a short paragraph under About the role covering employment type, location, approved states, travel. Or we could create another heading like "Position Details" but not in allowed list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we could also add other headings if needed, but better to stick to those. We can incorporate location, employment type, travel into About the role or Responsibilities? Probably About the role is appropriate to include context.
Thus About the role paragraph will include: FINBOA is seeking..., you will help shape..., you will work closely..., plus employment type full-time exempt, remote within approved states list, occasional travel may be required.
We must not repeat job title as heading. The job title is "Product Manager-Workflow Automation & Treasury Solutions". We must not put that as heading.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
FINBOA is seeking an experienced Product Manager to lead the strategy, roadmap, and market success of our workflow automation, treasury onboarding, intelligent intake, and AI-enabled solutions. In this role, you will help shape FINBOA’s next generation of products, enabling financial institutions to streamline operations, reduce manual effort, and accelerate digital transformation. You will work closely with Engineering, Product Marketing, Sales, Solutions Consulting, and customers to turn complex operational needs into valuable, scalable solutions. This is a full-time, exempt position. The role is remote within FINBOA‑approved states (Alabama, Arkansas, Arizona, Florida, Georgia, Illinois, Massachusetts, North Carolina, New York, Pennsylvania, South Carolina, Texas). Occasional travel may be required.
Responsibilities
- Own the strategy and roadmap for FINBOA’s workflow automation, treasury onboarding, intelligent intake, and AI‑enabled solutions.
- Translate customer and market needs into business requirements, user stories, and acceptance criteria.
- Manage and prioritize the product backlog in partnership with Engineering.
- Identify opportunities to apply AI, intelligent intake, and decisioning technology across the product portfolio.
- Conduct customer and prospect discovery to understand operational challenges and market needs.
- Lead customer feedback programs, including advisory groups, beta programs, and product validation sessions.
- Develop data‑supported business cases for new products and automation investments.
- Define and monitor product adoption, utilization, and customer satisfaction metrics.
- Partner with Product Marketing on positioning, pricing input, and go‑to‑market planning.
- Support Sales and Solutions Consulting with strategic opportunities, demonstrations, and RFP responses.
- Validate delivered functionality and support product‑launch readiness.
- Represent the portfolio during product planning and prioritization discussions.
Requirements
- Five or more years of product management experience in SaaS, fintech, banking technology, or a related field.
- Experience owning strategic roadmaps for technically complex products.
- Strong knowledge of workflow automation, process improvement, and operational efficiency.
- Experience creating product requirements, user stories, and acceptance criteria.
- A solid understanding of Agile methodologies and the software development lifecycle.
- Strong analytical, problem‑solving, communication, and stakeholder‑management skills.
Qualifications
- Treasury management or banking operations experience is strongly preferred.
- Experience with AI‑enabled products is preferred.
- Experience supporting banks, credit unions, or other community financial institutions is a plus.
Skills
- Experience using tools such as Jira, Azure DevOps, or Confluence.
Benefits
- Simple IRA with matching
- Bonus based on performance
- Competitive salary
- Dental insurance
- Health insurance
- Vision insurance
- Opportunity for advancement
- Paid time off
- Training & development
- Wellness resources
- Medical insurance
- 401(k) plan with company match
- Additional voluntary benefits
Pay
Compensation: $111,411 to $144,000 annually. Eligible for an annual bonus.
Schedule
Typical business hours, Monday through Friday.
We need to ensure we didn't include any boilerplate like EEO, etc. We removed that.
Check for duplication: We listed "Competitive salary" in Benefits and also Pay section includes salary range. That's okay; we keep both as they are distinct: Benefits list includes "Competitive salary" as a benefit; Pay section gives actual range. Not duplicate exactly.
We included "Medical insurance" separate from Health insurance? Actually health insurance often includes medical. But we keep both as they were mentioned: "FINBOA offers medical, dental, and vision coverage". So we have medical insurance separate.
We added "Additional voluntary benefits". Good.
Check that we didn't include any filler like "commensurate with experience". Not present.
Check that we didn't include any headings with empty content. All have content.
Now output only HTML fragment.
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we could also add other headings if needed, but better to stick to those. We can incorporate location, employment type, travel into About the role or Responsibilities? Probably About the role is appropriate to include context.
Thus About the role paragraph will include: FINBOA is seeking..., you will help shape..., you will work closely..., plus employment type full-time exempt, remote within approved states list, occasional travel may be required.
We must not repeat job title as heading. The job title is "Product Manager-Workflow Automation & Treasury Solutions". We must not put that as heading.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
FINBOA is seeking an experienced Product Manager to lead the strategy, roadmap, and market success of our workflow automation, treasury onboarding, intelligent intake, and AI-enabled solutions. In this role, you will help shape FINBOA’s next generation of products, enabling financial institutions to streamline operations, reduce manual effort, and accelerate digital transformation. You will work closely with Engineering, Product Marketing, Sales, Solutions Consulting, and customers to turn complex operational needs into valuable, scalable solutions. This is a full-time, exempt position. The role is remote within FINBOA‑approved states (Alabama, Arkansas, Arizona, Florida, Georgia, Illinois, Massachusetts, North Carolina, New York, Pennsylvania, South Carolina, Texas). Occasional travel may be required.
Responsibilities
- Own the strategy and roadmap for FINBOA’s workflow automation, treasury onboarding, intelligent intake, and AI‑enabled solutions.
- Translate customer and market needs into business requirements, user stories, and acceptance criteria.
- Manage and prioritize the product backlog in partnership with Engineering.
- Identify opportunities to apply AI, intelligent intake, and decisioning technology across the product portfolio.
- Conduct customer and prospect discovery to understand operational challenges and market needs.
- Lead customer feedback programs, including advisory groups, beta programs, and product validation sessions.
- Develop data‑supported business cases for new products and automation investments.
- Define and monitor product adoption, utilization, and customer satisfaction metrics.
- Partner with Product Marketing on positioning, pricing input, and go‑to‑market planning.
- Support Sales and Solutions Consulting with strategic opportunities, demonstrations, and RFP responses.
- Validate delivered functionality and support product‑launch readiness.
- Represent the portfolio during product planning and prioritization discussions.
Requirements
- Five or more years of product management experience in SaaS, fintech, banking technology, or a related field.
- Experience owning strategic roadmaps for technically complex products.
- Strong knowledge of workflow automation, process improvement, and operational efficiency.
- Experience creating product requirements, user stories, and acceptance criteria.
- A solid understanding of Agile methodologies and the software development lifecycle.
- Strong analytical, problem‑solving, communication, and stakeholder‑management skills.
Qualifications
- Treasury management or banking operations experience is strongly preferred.
- Experience with AI‑enabled products is preferred.
- Experience supporting banks, credit unions, or other community financial institutions is a plus.
Skills
- Experience using tools such as Jira, Azure DevOps, or Confluence.
Benefits
- Simple IRA with matching
- Bonus based on performance
- Competitive salary
- Dental insurance
- Health insurance
- Vision insurance
- Opportunity for advancement
- Paid time off
- Training & development
- Wellness resources
- Medical insurance
- 401(k) plan with company match
- Additional voluntary benefits
Pay
Compensation: $111,411 to $144,000 annually. Eligible for an annual bonus.
Schedule
Typical business hours, Monday through Friday.
We need to ensure we didn't include any boilerplate like EEO, etc. We removed that. Check for duplication: We listed "Competitive salary" in Benefits and also Pay section includes salary range. That's okay; we keep both as they are distinct: Benefits list includes "Competitive salary" as a benefit; Pay section gives actual range. Not duplicate exactly. We included "Medical insurance" separate from Health insurance? Actually health insurance often includes medical. But we keep both as they were mentioned: "FINBOA offers medical, dental, and vision coverage". So we have medical insurance separate. We added "Additional voluntary benefits". Good. Check that we didn't include any filler like "commensurate with experience". Not present. Check that we didn't include any headings with empty content. All have content. Now output only HTML fragment.