Sr. Director, Finance Technology Product Management

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about mission etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience". Pay and Schedule: we have Pay info: salary range $200K - $225K, no bonus, location-based. So we can include Pay section. Schedule: they mention work location virtual, 100% remote, preference eastern/central time zones. That's schedule? It's location and remote. Could be considered Schedule? The instruction says use Schedule heading if posting actually states them. It does state work location virtual, 100% remote, preference time zones. That's more about location/work arrangement, not schedule hours. Might still be considered Schedule? Probably we can include Schedule section with remote work details. Benefits: they list benefits. So include Benefits. Responsibilities: there is a big block under "WHERE YOUR CAREER IS A FORCE FOR GOOD (Key Responsibilities):" and then bullet-like sentences. Also earlier "What You Need To Know About The Job" includes description of role. We need to capture responsibilities as list items. Requirements: maybe "WHAT YOU NEED TO SUCCEED (required/minimum Qualifications)" includes education, experience, management, travel, skills & abilities. That's qualifications and skills. We need separate sections: Requirements (maybe education/experience), Qualifications, Skills. But we can combine? The instruction: Use headings for those specific names if content exists. We have content for Requirements (education, experience, management, travel). Qualifications maybe same? Actually "WHAT YOU NEED TO SUCCEED (required/minimum Qualifications)" includes Education, Experience, Management, Travel. That's qualifications. Then "Skills & Abilities" list. Then "WHAT WILL GIVE YOU THE COMPETITIVE EDGE (Preferred Qualifications)" includes preferred qualifications. Could be under Qualifications as well? But we need to avoid thin sections. Perhaps we combine Required Qualifications and Preferred Qualifications under Qualifications heading, with subpoints? But we must use

• for any list. We can have multiple lists under same heading. We need to preserve all substantive info, not invent or summarize away detail. So we must include all details: education bachelor's degree required, 10+ years related experience, experience in business applications, shared services, enterprise platforms, working across business and IT functions in complex environments, management 7+ years people leadership, travel 10-15% domestic required. Then skills & abilities list (multiple bullet points). Then preferred qualifications: prior experience in nonprofit/humanitarian/mission-driven orgs, familiarity with Lean Agile/SAFe framework, combination of education and general experience satisfies requirements so long as total years equate to description's minimum education and general experience years combined (certification cannot be substituted). Physical requirements are those present in normal office environment conditions. Operational flexibility required to meet sudden and unpredictable needs. Ability to use a personal computer, applicable software, office equipment for sustained periods. May include sitting for long periods, driving a vehicle, working under challenging conditions. We also have earlier "What You Need To Know About The Job" describing role: provides leadership for Finance technology strategy, modernization, Finance-owned business systems, vendor management, data and reporting capabilities, ERP transformation initiatives, enterprise program delivery. Serves as strategic bridge between Finance and IT, ensuring Finance technology solutions support current operational needs while evolving to meet future objectives. Provides leadership of product management practices across shared service domains (HR, Finance, Marketing, Core IT) to improve how work is shaped, prioritized, delivered. Partner with business and technology leaders to bring structure and transparency to demand, ensuring requests are clearly defined, aligned to priorities, positioned for effective execution. Translate diverse stakeholder needs into cohesive product and service direction, applying industry practices and organizational standards to guide prioritization and sequencing of work across both project-based and operational efforts. Operate within a flexible delivery environment, helping shared services coordinate effectively with agile delivery teams and traditional project models as appropriate. Provide leadership, coaching, direction to teams while fostering a culture of clarity, accountability, continuous improvement. Work location virtual, 100% remote, preference eastern/central time zones. Then responsibilities list under "WHERE YOUR CAREER IS A FORCE FOR GOOD (Key Responsibilities):" includes many bullet-like sentences. We need to capture those as list items. Benefits: list includes Medical, Dental Vision plans; Health Spending Accounts & Flexible Spending Accounts; PTO: Starting at 19 days a year; based on type of job and tenure; Holidays: 11 paid holidays comprised of six core holidays and five floating holidays; 401K with up to 6% match; Paid Family Leave; Employee Assistance; Disability and Insurance: Short + Long Term; Service Awards and recognition. Pay: annual salary range $200K - $225K; no annual bonus; note about location-based salary; factors; review at phone screening; job posted min five business days etc. The latter about posting duration maybe not needed? It's still substantive but maybe not needed for Pay section? It's about job posting duration; could be omitted? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include that note as part of Pay section? It's not pay but maybe still part of posting. However we have no section for "Posting Duration". Could we include it under Pay? Might be odd. Better to include a short paragraph under Pay about posting duration? But the instruction says include a section ONLY when posting has real, specific content for it. The posting duration is not Pay, Benefits, etc. There's no heading for that. We could drop it as it's not required to be kept? The instruction says preserve ALL substantive information; do not invent or summarize away detail. That suggests we should keep it somewhere. But we have limited allowed headings. Could we put it in a

  without heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It 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. It doesn't say we cannot have other headings, but to follow the pattern. Probably we should stick to those headings and embed other info within those sections as paragraphs. So we can put the posting duration note inside Pay section as a paragraph. Schedule: we have remote work location and time zone preference. That's more about work arrangement; we can put under Schedule heading. About the role: we have introductory paragraphs about mission etc. Also "What You Need To Know About The Job" could be considered About the role. We'll put that under About the role. Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:

  About the role

  ... mission paragraphs ...

  ... What You Need To Know About The Job description ...

  Responsibilities

  • Monitor technology trends and emerging capabilities to identify opportunities to improve Finance processes, systems, reporting, and user experience.
  • Drive technology-enabled modernization initiatives (EPM, ERP, etc.) that improve efficiency, controls, reporting, and maximize business value realization.
  • Oversee system administration, configuration management, user access management, release coordination, testing support, and operational governance activities.
  • Collaborate with IT to manage relationships with Finance technology vendors and partners to ensure platform performance, service quality, and alignment with business needs.
  • Partner with Finance stakeholders, IT, and data teams to support Finance data, reporting, analytics, and data governance initiatives.
  • Partner with Finance process owners and IT to define and maintain roadmaps for products, platforms, and service capabilities, aligning to enterprise priorities while accounting for operational needs, compliance requirements, and dependencies.
  • Build strong relationships with business leaders, IT partners, and vendors, acting as a trusted advisor and providing leadership, coaching, and guidance to team members and matrixed teams on day-to-day work as well as large cross-functional initiatives.
  • Lead practices to shape, assess, and prepare demand prior to formal intake, ensuring requests are clearly defined, aligned to business priorities, and ready for submission through established organizational processes.
  • Facilitate prioritization across stakeholders by understanding and reconciling diverse perspectives, needs, and constraints, synthesizing inputs into clear priorities and sequencing of work.
  • Create and maintain a transparent view of demand, priorities, and work in progress, improving flow and reducing fragmentation across project-based and operational work.
  • Scope: Establish operating policies and procedures that affect departments and subordinate sections and work units.
  • Interpret company-wide policies and procedures.
  • Develop budgets, schedules, and performance standards.
  Note: The "Scope:" etc were under a separate "+++++++++++++++++++++++++++++ Scope:" block. We'll include as list items.

  Requirements

  Education: Bachelor’s degree in Business, Information Technology, or related field required.

  Experience: Minimum 10+ years of related experience.

  Experience in business applications, shared services, or enterprise platforms and working across business and IT functions in complex environments.

  Management: Minimum 7+ years of people leadership experience.

  Travel: 10-15% domestic travel required.

  But we might want to combine into a list? The instruction says use
  • for any list of duties/requirements/benefits. So for requirements we should use a list. So:

    Requirements

    • Education: Bachelor’s degree in Business, Information Technology, or related field required.
    • Experience: Minimum 10+ years of related experience.
    • Experience in business applications, shared services, or enterprise platforms and working across business and IT functions in complex environments.
    • Management: Minimum 7+ years of people leadership experience.
    • Travel: 10-15% domestic travel required.

    Qualifications

    We have both required/minimum qualifications (already covered in Requirements?) Actually the "WHAT YOU NEED TO SUCCEED (required/minimum Qualifications)" includes education, experience, management, travel, plus skills & abilities. But we already put education/experience/management/travel under Requirements. The skills & abilities we can put under Skills. The preferred qualifications we can put under Qualifications as well. But we need to avoid duplication. Perhaps we treat Requirements as the mandatory education/experience/management/travel. Qualifications as the skills & abilities plus preferred qualifications? But the instruction lists Qualifications as a separate heading. We'll put the skills & abilities under Skills heading, and Qualifications under Qualifications heading for preferred qualifications and any other qualification statements (like physical requirements, operational flexibility, ability to use PC, etc). However the instruction says use
    • for any list of duties/requirements/benefits. So for Qualifications we can list preferred qualifications and other qualification statements as list items. Thus:

      Qualifications

      • Prior experience in nonprofit, humanitarian, or mission‑driven organizations.
      • Familiarity with Lean Agile/SAFe framework.
      • Combination