Jobs · Finance

Director - Global Shared Services, Finance

Rehlko · Milwaukee, WI · 1 mo ago
Finance$166k–$217k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "Why Work at Rehlko" (purpose), "What We Offer", "Why You Will Love this Job" (includes location and description), "Specific Responsibilities", "Requirements", "About Us", "Our Values". We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - Why Work at Rehlko: purpose, mission. Could be "About the role"? Actually "About the role" is generic. But we could use "About the role" heading for the purpose/mission description. However 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? It says use

    for section headings (e.g. ...). Likely they expect those standard headings. But we can also include other headings if needed? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the allowed headings. Probably we should map content to those headings where appropriate. Thus we need sections: - About the role: could contain the "Why Work at Rehlko" purpose description and maybe the "What We Offer"? Actually "What We Offer" is benefits/compensation. Could go under Benefits. - Responsibilities: list of specific responsibilities. - Requirements: list of requirements (education, experience, etc.) - Qualifications: maybe not separate; we could combine with Requirements. - Skills: maybe not present. - Benefits: "What We Offer" includes competitive compensation and benefits, work-life flexibility, recognition and rewards, development and career opportunities, safe and inclusive workplace. Also mention salary range. - Pay: The posting includes salary range: $166,400.00-$216,850.00. So we should include Pay section. - Schedule: Not mentioned; location remote with travel to Wisconsin. Could be Schedule? Not exactly schedule. Could be "Location" but not in list. Probably we should not create Schedule section unless posting states schedule. It does not mention schedule (like full-time, part-time). So we omit Schedule. - Also we have "Why You Will Love this Job" includes location and description of role. Could be part of About the role. - "About Us" and "Our Values" maybe could be omitted as boilerplate? But they contain substantive info about purpose, values. Might be considered part of About the role or separate. However we should avoid duplication and legal boilerplate. The "About Us" includes purpose and values, which is similar to earlier "Why Work at Rehlko". Might be duplicate. We can keep one section for purpose/values. We need to preserve all substantive information, not invent or summarize away detail. So we need to include details like: purpose, mission, product range, etc. Also the specific responsibilities list (many bullet points). Requirements list (degree, years, RPA, SAP, work authorization, state restrictions). Also note remote work opportunities unavailable for certain states. We also have "What We Offer" bullet list. We have salary range. We have location: Remote with travel to Wisconsin. We have "Why You Will Love this Job" includes location and description of role (Director – Global Shared Services (GSS) responsibilities). That overlaps with responsibilities. We need to avoid duplication. We'll combine. We need to output only HTML fragment, using

    headings,
    • for lists,

      for prose. We must not include navigation/legal/EEO boilerplate. So we must cut out the long EEO statement, ADA, etc. Also remove "Rehlko is an equal opportunity employer..." etc. Also remove "Learn more about Rehlko at http://www.rehlko.com/who-we-are." etc. Also remove "In addition to the investment in your development, Rehlko offers a benefits package including a competitive salary, health, vision, dental, 401(k) with Rehlko matching, and more!?" Actually that is part of benefits; we can keep benefits but not the duplicated line. We need to ensure we don't include the duplicated lines like "Rehlko proudly offers a rich history..." maybe that's okay as About Us. But we need to decide which headings to use. Potential sections: - About the role: combine "Why Work at Rehlko" purpose/mission, product range, and maybe "Why You Will Love this Job" description. - Responsibilities: list of specific responsibilities. - Requirements: list of requirements (education, experience, RPA, SAP, work auth, state restrictions). - Benefits: list from "What We Offer" plus maybe mention of competitive compensation. - Pay: salary range. We could also include a short paragraph for location under About the role or separate? Could add a

      under About the role: "Location: Remote with travel to Wisconsin." We must not create Schedule section. We must not include filler like "commensurate with experience". Not present. Now we need to ensure we preserve all substantive information. Let's extract substantive content. From "Why Work at Rehlko": - Purpose: creating an energy-resilient world for a better future. - Legacy: >100 years as global leader in energy resilience, delivering solutions critical to sustain and improve life. - Teams provide critical resource – energy – ensuring safety, security, independence. - Team members push boundaries, innovate, keep up with pace to create solutions for today’s world demands. - Product range includes engines, generators, power conversion, UPS systems, EV components and electrification solutions, microgrid controls and management, clean energy solutions serving OEM, residential, industrial, commercial customers. - Freedom to identify, create, deliver solutions – large and small – that help people and communities thrive. - Team members are essential energy powering organization’s success. - Commitment to fostering safe and sustainable work environment where safety is everyone’s responsibility. - Empower every team member to actively participate in Zero Is Possible safety culture by encouraging open communication, proactively reporting hazards, following protocols, suggesting improvements. - Join us in creating an energy resilient world for a better future. That's a lot. From "What We Offer": - Total Rewards programs designed to accelerate growth, energize performance, support culture of inclusion. - Offer total rewards that are easily understood, recognize results, enable career mobility, reflect commitment to valuing diverse needs. - We provide: - Competitive compensation and benefits - Work-life flexibility - Recognition and rewards - Development and career opportunities - A safe and inclusive workplace From "Why You Will Love this Job": - Location: Remote with travel to Wisconsin - Director – Global Shared Services (GSS) responsible for delivering shared service delivery operations (Hire to Retire, Order to Cash, Procure to Pay and Record to Report) for a global organization. - Also responsible for leading global payroll activities for manufacturing workforce that includes hourly plant employees, union labor, shift‑based operations, and salaried staff. - Collaborates with key stakeholders across Finance, Supply Chain, Procurement and HR functions to deliver expected results across all Joint Accountability Agreements (JAA). - Provides stewardship to assure that KPI/SLAs, quality, operating budgets, and customer satisfaction objectives are achieved. From "Specific Responsibilities" (list): - Develops and executes a comprehensive strategy for the Global Shared Services team to ensure alignment with the organization's HR & Finance objectives. - Provides visionary leadership to a diverse team, fostering a culture of collaboration, innovation, and continuous improvement. - Drives the implementation of best practices, policies, and procedures to enhance service delivery and optimize operational efficiency. - Oversees the end-to-end HR & Finance shared services operations, ensuring accuracy, compliance, and timely delivery of services across the global landscape. - Monitors service level agreements (SLAs), key performance indicators (KPIs), and metrics to measure team performance and identify areas for improvement. - Collaborates with stakeholders to streamline processes, standardize workflows, and implement automation tools to enhance productivity and reduce manual efforts. - Champions continuous improvement initiatives by identifying opportunities for process enhancements, cost savings, and service delivery optimization. - Stays up-to-date with industry trends, technological advancements, and regulatory changes, integrating these insights to drive innovation within the shared services function. - Collaborates with IT on system implementation / enhancement initiatives to the extent impacting the shares service function. - Ensures adequate and timely root cause analysis to understand problem drivers and implementation of necessary corrections and/or changes. - Identifies and drives process automation including robotics. - Experience leading payroll’s role in strategic initiatives such as M&A integration, new market entry, or global expansion. From "Requirements": - Bachelor’s degree in business, information technology, or related field required, with a preference towards a master’s degree. - 7+ years of experience in information technology, finance, or human resources within a global shared services function. - Knowledge of RPA technologies and SAP R/3 experience. - Applicants must be authorized to work in the US without requiring sponsorship now or in the future. - Rehlko hires candidates only in states where we have an established business presence. - We do not hire candidates residing in the following states: AK, AR, DE, HI, ME, ND, NE, VT, WV, WY. - Remote work opportunities are also unavailable for these locations. From "About Us": - Rehlko proudly offers a rich history steeped in creativity and commitment to our associates and communities, along with competitive benefits and compensation. - Our Purpose—Creating an energy resilient world for a better future—and Values: Curiosity, Trust, Pace, and Excellence, are important cultural components that shape the way we work and relate to one another. - Learn more about Rehlko at http://www.rehlko.com/who-we-are. (we can drop as navigation) - In addition to the investment in your development, Rehlko offers a benefits package including a competitive salary, health, vision, dental, 401(k) with Rehlko matching, and more!? (some duplication) - EEO statement etc (drop) - ADA statement (drop) - Rehlko is an equal opportunity/affirmative action employer. (drop) - Our Values Curiosity – Seek, learn, share Trust – Go farther together Pace – Focus to go faster Excellence – Find the win every day (we can keep values maybe) We need to avoid duplication. The purpose already covered. Values could be included under About the role or separate section? Not in list of headings but we could include as a

      under About the role. We need to ensure we don't include boilerplate like EEO

Similar jobs