Senior People & Culture Information Systems Analyst
for each section heading. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Must preserve all substantive information.
We need to parse the description.
Key parts:
- Description: "The application window will close October 31, 2026" (metadata, maybe include in a short p). Not a heading.
- Job Location: "The primary work location for this role is remote within the continental United States." (metadata)
- About Envestnet: paragraph.
- The Team You’ll Join: paragraph.
- How You’ll Contribute: bullet list of duties (list items). This is responsibilities.
- What You’ll Need to Bring: list of requirements (5+ years etc). This is requirements/qualifications/skills.
- Nice-to-Haves: list (optional). Could be under Skills or Qualifications.
- Why You’ll Enjoy Working at Envestnet: paragraph (maybe Benefits? Actually it's about culture, could be under Benefits? But we have Benefits section only if posting actually states benefits. There's later "Our Investment in You" which includes base salary range, incentive component, benefits list. So we have Pay and Benefits sections.
- Sponsorship: "This position is not open to candidates requiring visa sponsorship" (metadata maybe short p).
- Our Investment in You: includes base salary range, incentive component, benefits list.
- Our Commitment to Inclusion & Belonging: EEO boilerplate (should be removed).
- Recruitment Fraud: boilerplate (remove).
Thus we need sections:
- About the role? Could combine About Envestnet and The Team You’ll Join and How You’ll Contribute? But headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections to include based on content.
We have:
- About the role: could be a summary of role (maybe combine About Envestnet, The Team You’ll Join, How You’ll Contribute). But we must not invent placeholder. We have substantive content: About Envestnet, The Team You’ll Join, How You’ll Contribute. So we can put that under About the role.
- Responsibilities: the bullet list under How You’ll Contribute (the duties). That is responsibilities.
- Requirements: maybe the "What You’ll Need to Bring" list (mandatory). Could be Requirements.
- Qualifications: maybe also same as Requirements? But we could split: Requirements (experience) and Qualifications (certifications etc). However we have Nice-to-Haves which could be Skills or Qualifications. We need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But headings are separate; we can include both if they have content. Let's see:
What You’ll Need to Bring includes:
- 5+ years of hands-on experience configuring and supporting Workday across multiple modules
- Expertise in Workday Core HCM, Recruiting and additional SKUs; strong proficiency in Workday reporting .
- Proven ability to work independently while contributing to a collaborative, high-performing team environment through knowledge sharing, supporting peers and mentoring junior team members.
- Demonstrated ability to independently lead small-to-medium Workday initiatives or configuration projects from planning through execution
- Experience with EIBs and data loads across HR systems
- Proven track record of troubleshooting complex issues and developing effective, scalable solutions
- Strong interpersonal and communication skills, with a customer-centric approach to problem-solving
- High attention to detail, organizational and time management skills and commitment to data integrity and process compliance.
Nice-to-Haves:
- One or more Workday Pro certifications.
- Basic understanding of HRIS integrations and API workflows.
- Experience supporting a global HR team and processes.
- Superior knowledge of MS Excel, Word and PowerPoint.
Thus we could have Requirements (mandatory) and Qualifications (nice-to-haves) or Skills. But we also have Skills heading. Could put nice-to-haves under Skills.
Pay: base salary range $94,600 - $118,300, plus incentive component.
Benefits: list: medical insurance, paid time off (PTO), 401k company match, paid parental leave, education reimbursement, disability coverage and mental health & wellness support.
Schedule: not mentioned; remote work location but not schedule. No schedule info, so we should not include Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (or Skills), Benefits, Pay.
We need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We can include Qualifications and Skills both if we have content. But we have nice-to-haves which could be Skills. Qualifications could be the mandatory requirements? Actually Requirements heading is for mandatory requirements; Qualifications could be for certifications etc. But we have both mandatory and nice-to-haves. Let's assign:
- Requirements: mandatory experience list.
- Qualifications: maybe certifications etc? But we have nice-to-haves includes certifications, global HR experience, MS Office. Could be Qualifications.
- Skills: maybe we could put technical skills like Workday reporting, EIBs, etc. But those are already in mandatory. To avoid thin sections, maybe combine Requirements and Qualifications into one section called Requirements (or Qualifications). But the instruction says use headings only when posting has real specific content for it. It doesn't forbid having both Requirements and Qualifications if both have content. We have content for both: mandatory experience (Requirements) and nice-to-haves (Qualifications). So we can include both.
Skills heading: we could put technical skills like Workday Core HCM, Recruiting, reporting, EIBs, etc. But those are already in mandatory. Might be redundant. Better to omit Skills if not distinct.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if we have content for Benefits: yes list.
Pay: yes base salary range and incentive component.
Now we need to format.
We must not include HTML wrapper tags, just fragment.
We'll produce:
About the role
... combined paragraphs about Envestnet, team, contributions ...
But we must not repeat job title as heading. That's fine. We need to preserve all substantive information. So we need to include the paragraphs about Envestnet, The Team You’ll Join, How You’ll Contribute (but the latter we will move to Responsibilities as list). So About the role should include About Envestnet and The Team You’ll Join (maybe also a brief summary of role?). We'll include those two paragraphs. Responsibilities: list of duties from How You’ll Contribute (the bullet points). We'll convert each sentence intoor drop it. So we can include a short p for metadata like application window, location, sponsorship. Probably after About the role? Could be a separate
before sections. We'll include a
containing: "Application window closes October 31, 2026. Primary work location: remote within the continental United States. This position is not open to candidates requiring visa sponsorship." Now ensure we don't include boilerplate: EEO, recruitment fraud, etc. Now craft HTML. Let's write. About the role paragraph: combine About Envestnet and The Team You’ll Join. About Envestnet paragraph: "Envestnet is an adaptive WealthTech company that is redefining the future of wealth management by helping advisors meet the moment with its comprehensive technology, actionable insights, and industry leading support. Backed by over 25 years of experience and approximately $7.0 trillion in platform assets, Envestnet is trusted by over one third of financial advisors across leading banks, wealth managers, brokerages, and RIAs. For a deeper look at how Envestnet is shaping the future of financial advice, visit www.envestnet.com." The Team You’ll Join paragraph: "The P&C (People & Culture) Technology team builds and runs the systems that power the employee experience, with Workday at the center. We partner across P&C, Finance, IT, and the business to deliver scalable, well-governed solutions. We’re in a major transformational period; redesigning our Workday environment, rolling out recruiting and performance management, and introducing a new career framework. At the same time, we lead critical programs like compensation cycles, open enrollment, and payroll, making them more streamlined and automated. This team blends strategy and execution, focusing on simplifying processes, improving data and governance, and creating a more modern, employee-centric experience." We could also include a brief sentence about role? But not needed. Now Responsibilities list: extract each duty from How You’ll Contribute. How You’ll Contribute paragraph: It's a long paragraph with multiple sentences each starting with a verb. We'll split into list items. Sentences: - Serve as a subject matter expert for the Workday HR Technology application by owning end-to-end resolution of complex issues and configuration requests, while providing guidance and mentorship to junior team members. - Lead the analysis, design, and testing of Workday enhancements, collaborating closely with business stakeholders to translate functional requirements into technical specifications. - Develop, configure, and maintain EIBs and related tools to support efficient data loading and integration across systems. - Provide support for integrations and downstream data flow, including troubleshooting and recommending improvements to ensure system interoperability and data consistency. - Drive continuous improvement of Workday configuration, processes, and user experience, identifying opportunities for innovation and system optimization. - Assist with Workday security configuration and audits, including the maintenance of user- and role-based security groups. - Drive Workday release management by leading analysis and testing, assessing new features, coordinating stakeholder readiness, and promoting user adoption through education and support. - Maintain and enhance detailed documentation of HR Technology procedures, configuration decisions, and system updates to support internal controls, audit requirements and knowledge transfer. - Create, enhance, and maintain advanced Workday reports, dashboards, and analytics tools for key stakeholders using reporting best practices to ensure data accuracy and alignment with privacy and security policies. We'll make each a