OneStream Financial Systems Administrator

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Position Summary (could be About the role). Key Responsibilities (Responsibilities). Qualifications (Education & Experience, Technical Skills, Core Competencies, Preferred Qualifications). There's also a Benefits section (Why Join Us and Why work at Safariland? includes benefits). No explicit Pay or Schedule mentioned. So we should not include Pay or Schedule sections. Also we should not repeat job title as heading. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement at end; we should remove that. Also remove "TOGETHER, WE SAVE LIVES" maybe not needed but it's not boilerplate? It's a tagline; could be considered not substantive? Might keep as part of intro? Probably we can drop it as it's not part of job description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The tagline is not those; but we can keep? Might be considered not needed. Safer to keep only substantive content: Position Summary, Key Responsibilities, Qualifications (Education & Experience, Technical Skills, Core Competencies, Preferred Qualifications), Benefits (Why Join Us, Why work at Safariland?). We need to format as HTML fragment. Let's extract content. Position Summary paragraph: "The OneStream Financial Systems Administrator is responsible for the administration, maintenance, and continuous improvement of the OneStream platform, supporting the Company’s financial close, consolidation, reporting, and planning processes. This role serves as the primary functional and technical owner of OneStream, partnering closely with Finance, Accounting, and IT to ensure data integrity, system reliability, and efficient financial reporting. The ideal candidate will bring a strong combination of accounting knowledge and financial systems expertise to optimize business processes and enable scalable growth." That's prose ->

  . Key Responsibilities: bullet list under headings: System Administration & Governance, Financial Close & Consolidation Support, Data Integration & Data Integrity, Reporting & Platform Development, User Support & Training, Controls, Compliance & Audit Support, Continuous Improvement & Projects. Each has sub-bullets. We need to output as

  • for any list of duties/requirements/benefits. So we can have a top-level
    with each responsibility as
    • . Inside each
    • we can have maybe a heading? Not required but we can keep prose. The instruction: use
      • for any list of duties/requirements/benefits. So we should wrap each duty in
      • . For sub-items, we could also use nested
        • . That's fine. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all sub-bullets. Let's list them: System Administration & Governance - Administer and maintain the OneStream platform, including: - User access, roles, and security configurations - Dimensions, hierarchies, and metadata management - Manage system upgrades, patches, and version releases - Maintain development, training, and production environments - Ensure compliance with internal controls, including SOX and segregation of duties Financial Close & Consolidation Support - Support monthly, quarterly, and annual financial close processes, including: - Consolidations and eliminations - Financial reporting and data validation - Monitor workflows and task manager processes to ensure timely completion - Support account reconciliation processes within OneStream and validate outputs Data Integration & Data Integrity - Oversee integration of financial data from ERP systems into OneStream - Perform data validation and reconciliation (e.g., ERP-to-OneStream tie-outs) - Troubleshoot data load and transformation issues - Maintain mappings, transformations, and data quality controls Reporting & Platform Development - Develop and maintain: - Cube views and financial reports - Dashboards and reporting solutions for management and external reporting - Configure workflows, forms, business rules, and calculation logic - Support system enhancements, new entity setups, and acquisitions User Support & Training - Serve as the primary point of contact for OneStream support issues - Troubleshoot system, reporting, and access issues - Train new users and provide ongoing education to Finance teams - Develop and maintain documentation and training materials Controls, Compliance & Audit Support - Maintain strong system controls and documentation to support audit requirements - Coordinate with internal and external auditors on system-related requests - Ensure compliance with SOX/internal control frameworks and access governance Continuous Improvement & Projects - Identify opportunities to improve automation, reporting, and workflows - Lead or support system enhancements and strategic finance initiatives - Act as a subject matter expert on OneStream functionality and best practices - Stay current on platform updates and emerging capabilities Now Qualifications: includes Education & Experience, Technical Skills, Core Competencies, Preferred Qualifications. Education & Experience: - Bachelor’s degree in Accounting, Finance, Information Systems, or related field - 3–7+ years of experience in financial systems or EPM platforms - Hands-on experience with OneStream strongly preferred - Strong understanding of: - Financial close and consolidation - Financial reporting and account reconciliations Technical Skills: - Experience with OneStream XF or similar EPM tools (Hyperion, Oracle, SAP BPC) - Familiarity with: - ERP integrations and financial data flows - Financial reporting tools and Excel-based reporting - Experience with data structures, mappings, and system configuration - Strong analytical and troubleshooting capability Core Competencies: - Strong problem-solving and analytical skills - Ability to translate business requirements into technical solutions - Effective communication and cross-functional collaboration - High attention to detail and strong organizational skills - Ability to manage multiple priorities in a fast-paced environment Preferred Qualifications: - CPA or relevant professional certification - Experience supporting SOX compliance and audit processes - Experience implementing or enhancing OneStream or similar platforms We need to decide how to structure Qualifications section. Could have a heading

          Qualifications

          and then sub-sections? The instruction: use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have a

          Qualifications

          . Inside we can have paragraphs or lists. Since there are multiple subcategories, we could either make separate headings for each (like Education & Experience) but those are not in the allowed list; but we could still use

          ? Not allowed? The instruction only says use

          for section headings (list). It doesn't forbid other headings, but to keep simple we can just use

          for prose and

          • for lists. So under Qualifications we can have a

            summarizing? But we need to preserve all detail; we can break into multiple

            • lists with headings as maybe. That's acceptable. Similarly Skills: The posting has Technical Skills and Core Competencies; we could combine under Skills section? The instruction includes Skills as a possible heading. So we could have

              Skills

              and include both Technical Skills and Core Competencies as lists. But we also have Qualifications heading; we need to include Education & Experience and Preferred Qualifications under Qualifications. Thus:

              About the role

              (Position Summary)

              Responsibilities

              (list)

              Qualifications

              (Education & Experience + Preferred Qualifications)

              Skills

              (Technical Skills + Core Competencies)

              Benefits

              (Benefits list) We must not include Pay or Schedule. Now Benefits: from "Why Join Us" and "Why work at Safariland?" includes list of benefits. Let's extract: Why Join Us: - High-impact role supporting enterprise-wide financial reporting - Opportunity to shape and optimize a growing OneStream environment - Close collaboration with senior finance leadership and accounting teams - Exposure to complex consolidations, integrations, and reporting processes Why work at Safariland? (benefits): - Medical, dental & vision insurance - 401(k) with company match - Employer paid life insurance and AD&D - Employer paid disability - Wellness program - Adoption assistance - Tuition assistance - Employee assistance program - Work life balance - Paid time off (PTO), sick leave and paid holidays throughout the calendar year (consistent with relevant state law and company policies) Also earlier: "At Safariland our colleagues are some of the best and brightest..." that's fluff; we can keep maybe as prose? It's not a benefit but could be considered part of Why work at Safariland? Might be considered boilerplate? It's describing culture; maybe we keep as prose under Benefits? But instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The culture description is not filler but it's not a benefit; but we could include it as part of Benefits section as prose before list. However the Benefits section should contain benefits; we could keep the culture description as a

              before the list. But we need to avoid EEO boilerplate at end; we will remove that. Now construct HTML. We'll need to ensure proper nesting. Let's draft:

              About the role

              The OneStream Financial Systems Administrator is responsible for the administration, maintenance, and continuous improvement of the OneStream platform, supporting the Company’s financial close, consolidation, reporting, and planning processes. This role serves as the primary functional and technical owner of OneStream, partnering closely with Finance, Accounting, and IT to ensure data integrity, system reliability, and efficient financial reporting. The ideal candidate will bring a strong combination of accounting knowledge and financial systems expertise to optimize business processes and enable scalable growth.

              Responsibilities

              • System Administration & Governance
                • Administer and maintain the OneStream platform, including:
                • User access, roles, and security configurations
                • Dimensions, hierarchies, and metadata management
                • Manage system upgrades, patches, and version releases
                • Maintain development, training, and production environments
                • Ensure compliance with internal controls, including SOX and segregation of duties
                • Financial Close & Consolidation Support
                  • Support monthly, quarterly, and annual financial close processes, including:
                  • Consolidations and eliminations
                  • Financial reporting and data validation
                  • Monitor workflows and task manager processes to ensure timely completion
                  • Support account reconciliation processes within OneStream and validate outputs
                • Data Integration & Data Integrity
                  • Oversee integration of financial data from ERP systems into OneStream
                  • Perform data validation and reconciliation (e.g., ERP-to-OneStream tie-outs)
                  • Troubleshoot data load and transformation issues
                  • Maintain mappings, transformations, and data quality controls
                • Reporting & Platform Development
                  • Develop and maintain:
                  • Cube views and financial reports
                  • Dashboards and reporting solutions for management and external reporting