Lead Payroll Integration Manager (Hybrid Role)

We need to output HTML fragment with sections: About the role? Actually the posting includes "What You'll Do" and "Who You Are" etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We have content for responsibilities (What You'll Do). We have qualifications/requirements (Who You Are). We have preferred qualifications (Skills That Will Help You Stand Out). We have salary range (Pay). We have work environment (maybe not a standard heading; but we could treat as "Work Environment" but not in allowed headings list; we should not create a heading not listed. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. We need to include Pay section with salary range. We have salary range: $69300 - $126000 / year. Also mention non-sales positions have opportunity to participate in a bonus program. That's part of compensation. We'll include that in Pay. We have Work Environment info: in-office and hybrid, locations. Not a standard heading; maybe we can put under About the role? But we should not invent headings. Could we include it as a paragraph under About the role? The About the role heading is allowed; we can put a brief description there. However we already have responsibilities; maybe we can put About the role as a summary of the role. But we must not repeat job title as heading. We can still have About the role section with a paragraph describing the role (maybe combine what you'll do?). But we already have Responsibilities section with detailed duties. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those headings if we have content. We have Responsibilities (What You'll Do). We have Requirements/Qualifications (Who You Are). We have Skills (Preferred Qualifications). We have Pay (Salary Range). We might not have Benefits, Schedule, About the role (maybe we can include a brief overview from the first paragraph). The first paragraph: "The Lead Payroll Integration Manager will serve as the primary owner and subject matter expert for payroll setup and integration within the Nonqualified (NQ) Retirement Solutions business. This role is responsible for leading client and payroll provider conversations, supporting accurate and secure data integration, and helping establish scalable processes that improve the client, participant, and operational experience. This individual will coordinate closely with clients, payroll vendors, consultants, technology partners, onboarding, administration, and the WSRS (401k) Payroll Integration Team to support new implementations, conversions, and migration efforts. The role requires strong ownership, consultative communication, technical curiosity, and the ability to drive progress in an evolving area of the business." That's a good About the role summary. We should not include boilerplate like Work Authorization/Sponsorship, Investment Code of Ethics, Experience Principal, Equal Opportunity Employer, Time Off Program, Pension Eligible, Posting Window, Original Posting Date, Most Recently Posted Date, AI tools, etc. Remove those. We also need to remove duplicated lines. Ensure we preserve all substantive information: responsibilities, qualifications, preferred qualifications, salary range, work environment? Work environment is not in allowed headings; but maybe we can include it under About the role as additional detail. The instructions: "Prefer a few substantive sections over many thin ones." So we could include About the role (summary), Responsibilities, Requirements, Qualifications, Skills, Pay. That's six sections. Could we combine Requirements and Qualifications? They are separate headings but we have both. The posting has "Who You Are" with required qualifications, and "Preferred Qualifications — Skills That Will Help You Stand Out". So we can map: Requirements = required qualifications (Bachelor’s degree or equivalent experience required, plus 4+ years of related experience, etc). Qualifications = maybe we could treat as same? But we have both headings allowed; we could put required under Requirements and preferred under Qualifications? Actually Qualifications heading is allowed; we could put preferred qualifications there. But we also have Skills heading allowed; we could put skills there. However we have both "Preferred Qualifications — Skills That Will Help You Stand Out" which includes skills. So we could put that under Skills. And we could put the required qualifications under Requirements. Then we might not need Qualifications heading. But we could also put the required qualifications under Requirements and the "Preferred Qualifications" under Qualifications, and maybe not use Skills. But we have both headings allowed; we need to decide. Better to follow typical structure: Requirements (mandatory), Qualifications (preferred), Skills (maybe specific skills). But the posting lumps preferred qualifications and skills together. We could put the preferred qualifications under Qualifications, and maybe not use Skills. Or we could split: Qualifications = preferred qualifications, Skills = specific skills listed (like knowledge of non-qualified deferred compensation plans, experience implementing payroll integrations, etc). That seems reasonable. Thus: - About the role: summary paragraph from first paragraph. - Responsibilities: list of duties from "Key Responsibilities" bullet points (the lines after that heading). We need to convert each line into

. The bullet points start with "Serve as the lead point of contact..." etc. We'll capture each. - Requirements: required qualifications: Bachelor’s degree or equivalent experience required, plus 4+ years of related experience. Working knowledge of business processes, financial services products, and supporting systems. Strong analytical, problem-solving, communication, and relationship management skills. Ability to manage multiple priorities, meet deadlines, and drive results in a fast-paced and ambiguous environment. Strong attention to detail with the ability to understand cross-functional impacts and downstream process implications. Demonstrated ability to work independently and collaboratively while proactively seeking information, resources, and partnerships. - Qualifications (preferred): Working knowledge of non-qualified deferred compensation plans, including plan design complexities, Section 409A requirements, payroll deduction structures, and related administrative impacts. Experience implementing or supporting payroll, HRIS, benefits, or retirement plan integrations. Experience with payroll setup, payroll deduction codes, payroll administration, or vendor payroll file requirements. Experience managing client implementations, onboarding projects, conversions, or complex operational initiatives involving multiple stakeholders. Knowledge of file transmission methods, data mapping, validation, testing, and integration controls. Experience supporting process improvement, operational excellence, automation, or scalable workflow design. - Skills: maybe we could treat as same as Qualifications? But we already used Qualifications for preferred qualifications. Could we put something else under Skills? The posting didn't list separate skills beyond those. Could we leave Skills section out? The instruction: "include a section ONLY when the posting has real, specific content for it". So if we don't have distinct content for Skills, we should omit it. So we will not include Skills heading. - Pay: salary range and bonus program info. Also maybe mention that non-sales positions have opportunity to participate in a bonus program. We'll include that. - Benefits: we have no specific benefits info (they mention benefits generically but not specific). So omit Benefits. - Schedule: we have work environment info (in-office and hybrid, at least three office days). That's schedule-related. Could we put that under Schedule? The posting says: "Work Environment This role offers in-office and hybrid (blending at least three office days in a typical workweek), in Des Moines, IA, Charlotte, NC or Raleigh, NC." That's schedule/location. We could treat that as Schedule section. The allowed heading Schedule is appropriate. So we will include Schedule with that info. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. We must not include any boilerplate like Work Authorization, etc. Now produce HTML fragment: use

for each heading, then content:

for prose,

• for lists. We need to ensure we preserve all substantive information. Let's extract details precisely. About the role paragraph: combine the first paragraph (maybe two sentences). Let's copy: "The Lead Payroll Integration Manager will serve as the primary owner and subject matter expert for payroll setup and integration within the Nonqualified (NQ) Retirement Solutions business. This role is responsible for leading client and payroll provider conversations, supporting accurate and secure data integration, and helping establish scalable processes that improve the client, participant, and operational experience. This individual will coordinate closely with clients, payroll vendors, consultants, technology partners, onboarding, administration, and the WSRS (401k) Payroll Integration Team to support new implementations, conversions, and migration efforts. The role requires strong ownership, consultative communication, technical curiosity, and the ability to drive progress in an evolving area of the business." That's the About the role. Responsibilities: list each bullet after "Key Responsibilities". Let's extract: - Serve as the lead point of contact for NQ payroll setup and integration efforts, including client, payroll provider, consultant, and internal partner coordination. - Lead end-to-end payroll implementation activities, including file specifications, configuration, testing, validation, issue resolution, and production readiness. - Provide subject matter expertise on NQ payroll setup and integration processes, payroll file requirements, provider capabilities, migration strategies, and downstream administrative impacts. - Partner across onboarding, administration, consulting, technology, operations, and WSRS Payroll Integration teams to align standards, share best practices, and deliver scalable solutions. - Lead and support FTP-to-IPP migration efforts, transitioning clients from legacy file solutions to more automated integration methods that improve efficiency, scalability, and risk controls. - Identify opportunities to reduce manual work, improve quality, strengthen controls, and enhance the overall client and participant experience. - Develop and maintain procedures, training resources, and quality standards related to payroll setup and integration processes. - Demonstrate initiative and ownership by leveraging available resources, building expertise, solving problems independently, and establishing credibility with limited day-to-day direction. We'll put each as
• . Requirements (mandatory): extract from "Who You Are" first paragraph: "Bachelor’s degree or equivalent experience required, plus 4+ years of related experience. Working knowledge of business processes, financial services products, and supporting systems. Strong analytical, problem-solving, communication, and relationship management skills. Ability to manage multiple priorities, meet deadlines, and drive results in a fast-paced and ambiguous environment. Strong attention to detail with the ability to understand cross-functional impacts and downstream process implications. Demonstrated ability to work independently and collaboratively while proactively seeking information, resources, and partnerships." We'll put each as
• under Requirements. Qualifications (preferred): extract from "Preferred Qualifications — Skills That Will Help You Stand Out" bullet list: - Working knowledge of non-qualified deferred compensation plans, including plan design complexities, Section 409A requirements, payroll deduction structures, and related administrative impacts. - Experience implementing or supporting payroll, HRIS, benefits, or retirement plan integrations. - Experience with payroll setup, payroll deduction codes, payroll administration, or vendor payroll file requirements. - Experience managing client implementations, onboarding projects, conversions, or complex operational initiatives involving multiple stakeholders. - Knowledge of file transmission methods, data mapping, validation, testing, and integration controls. - Experience supporting process improvement, operational excellence, automation, or scalable workflow design. We'll put each as
• under Qualifications. Pay: extract salary range and bonus program. Salary Range Information: "Salary ranges below reflect targeted base salaries. Non-sales positions have the opportunity to participate in a bonus program. Sales positions are eligible for sales incentives, and in some instances a bonus plan, whereby total compensation may far exceed base salary depending on individual performance. Actual compensation for all roles will be based upon geographic location, work experience, education, licensure requirements and/or skill level and will be finalized at the time of offer. Salary Range (Non-Exempt expressed as hourly; Exempt expressed as yearly) $69300 - $1