We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Location, Pay DOE (Pay depends on experience) but not specific numbers. According to rule: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. Pay DOE is a statement but not a specific amount. The rule says: 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. "Pay DOE" is essentially "depends on experience" which is placeholder. So we should not include Pay section. Benefits not mentioned. Schedule not mentioned. So we can include About the role (maybe from description), Responsibilities (list of duties), Requirements (maybe required qualifications), Qualifications (desired qualifications), Skills (technical skills). We need to decide which headings to use.
We must preserve all substantive information. Not repeat job title as heading. Not include Job ID etc. Remove boilerplate.
We need to parse the posting.
Key content:
- Company: Enormous Enterprise LLC
- Location: Hopewell, NJ (also mentions Charlotte, NC / Plano, TX but need locals or nearby candidates only)
- Posted September 15, 2026
- Apply (ignore)
- Description: Senior Workday Developer/Configuration Analyst
- Location(s): Either Hopewell, NJ / Charlotte, NC / Plano, TX --- Needs Locals or Nearby Candidates ONLY!)
- Interview Process: Online Video Interview + In-Person/Onsite interview (maybe not needed? It's part of posting but could be considered metadata; we can drop as not substantive? Might be considered part of process but not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Interview process maybe not boilerplate but could be considered part of posting; but we can keep if we think it's substantive. However we have no section for interview process; we could include under About the role or Responsibilities? Probably better to include in About the role as a brief note.
- Must Have Key Skills/Experience: list bullet points.
- Job Description Role: Workday Configuration Analyst/Developer
- PROJECT: International Payroll
- Must Have: Looking for resources with experience in Payroll of EMEA and LATAM
- Position Summary: paragraph.
- Required Qualifications: list bullet points.
- Desired Qualifications: list bullet points.
- Technical Skills: list.
We need to map to sections.
About the role: could include Position Summary and maybe project info.
Responsibilities: from Required Qualifications bullet points (they are duties). Also from Position Summary duties.
Requirements: maybe the Must Have Key Skills/Experience (the "Must Have" list). Or we could treat Required Qualifications as Requirements.
Qualifications: Desired Qualifications.
Skills: Technical Skills.
We must not create empty sections.
Let's extract specifics.
Must Have Key Skills/Experience:
- Min. 5+ years of Workday Core HCM Exp. Required.
- Workday Core HCM
- Workday Payroll
- Workday integrations
- Workday Configurations
- Workday End-to-End Implementations
- End-to-end Workday implementations (Not Just Maintenance)
- Built integrations from scratch (Not just maintained the existing)
- Full development lifecycle experience
- Requirement gathering experience
- Business partner interaction experience
- Documentation maintenance
- Deep domain expertise in at least one area (Core HCM, Payroll, Talent Acquisition, etc.)
Also later: Must Have: Looking for resources with experience in Payroll of EMEA (Europe, Middle East, Africa) and LATAM (Latin America)
Position Summary paragraph: "The Workday Configuration Analyst provides HR system administration, including business process configuration, reporting development, end user training, and data management in support of maintaining Workday as a best-in-class employee experience forward platform. This role will partner with the other Workday team members, IT, business partners, vendors and business leaders to effectively meet the HR technology needs of the organization. The focus modules are Core HCM, Compensation, Talent, Payroll, Time, Absence, Benefits, Integrations, and Reporting."
Required Qualifications bullet list:
- Configure complex Workday business processes.
- Support configuration and troubleshooting of business processes with a focus on Payroll, Time, and Absence.
- Perform additional Workday administrative functions including tenant configuration, data loads, integrations, and reporting.
- Review business procedures/workflows to ensure system features are being fully utilized and identify Workday features that may improve efficiency.
- Cohabitate in Sandbox environments and work within an established, well-controlled systems environment by defining, documenting, and enforcing system standards.
- Provide pre- and post-launch end-user support, change management, issue resolution, testing, and training to enhance and optimize Workday processes.
- Ability to mass load information via EIBs and knowledge on how to test integration inputs and outputs based on transactional changes.
- Knowledge on how to create reports and use them in auditing configuration change effectiveness.
- Document technology specifications for current and future configuration.
- Maintain accurate change management documentation to satisfy Bank of Americas internal/external audit controls and compliance practices.
- Understand Workdays Implementation Methodology and use it on all projects.
- Act as the domain support for feature releases and issue resolution, supporting the Workday Architect to define scope, prioritize, plan and implement system changes and enhancements.
- Maintain working functional knowledge of HR and HR systems across multiple functions and teams, driving community collaboration and a commitment to a great support service experience.
- Foster ongoing Workday relationships - relevant memberships and engagement in Workday Community, User Groups, and Conferences.
- Act as support to business partners and work to enhance their understanding of Workday.
Desired Qualifications bullet list:
- Bachelors Degree in Information Technology or related field; or an equivalent combination of education and experience sufficient to perform the key accountabilities of the job required
- 5+ years of Workday HCM experience required.
- Workday Pro or Workday Certifications strongly preferred
- A solid understanding in at least three Workday modules including Core HCM, Compensation, Talent, Payroll, Time, Absence, and Benefits
- Workday Integrations experience preferred
- Knowledge of Workday business process, core setup, and security framework
- Deep understanding of Workday data model, corporate system architecture, interfaces, reporting, and data loading procedures
- Attention to detail and relentless commitment to follow-through
- Ability to convey ideas and recommendations to a wide variety of audiences at all levels in a clear, compelling and succinct way in written and verbal communications
- Strong expertise in cloud-based multi-tenant systems
- Strong ability to work with others on solutions.
Technical Skills:
- Workday
- SQL-WINDOWS
- Windows
Probably "SQL-WINDOWS" and "Windows" as separate.
Now we need to output HTML fragment with headings
for each section.
We'll include sections: About the role, Responsibilities, Requirements, Qualifications, Skills.
We should not include Pay, Benefits, Schedule.
Now we need to put content.
About the role: include Position Summary paragraph plus maybe project info: International Payroll, focus on EMEA/LATAM payroll experience. Also location info? Might be considered metadata but could be included. However location is not a responsibility; maybe we can include location in About the role as a brief note. The instruction: 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. Location is minor metadata; we could fold into a short
under About the role. Also posted date maybe minor metadata; we can drop.
Thus About the role
containing: Position Summary sentence(s) plus mention of International Payroll project and EMEA/LATAM payroll experience, plus location (Hopewell, NJ with options Charlotte, NC / Plano, TX, locals/nearby only). Also maybe interview process? Could be included but not necessary.
We'll keep it concise but preserve all substantive information. Must not invent or summarize away detail. We need to preserve all substantive information; we cannot drop details like "Must Have: Looking for resources with experience in Payroll of EMEA and LATAM". That is substantive; we need to keep it somewhere. Could be in About the role or Responsibilities. Probably About the role.
Also "Must Have Key Skills/Experience" list is substantive; we could put those under Requirements.
"Required Qualifications" list is also substantive; could be under Requirements as well, but we might split: Requirements = Must Have Key Skills/Experience; Qualifications = Desired Qualifications; Responsibilities = from Position Summary and Required Qualifications duties? However there is overlap. We need to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include each piece somewhere, but we can group similar items.
We could structure:
- About the role: Position Summary paragraph + project + location + interview process? (maybe not needed)
- Responsibilities: list of duties from Required Qualifications (the bullet points that describe what the role does)
- Requirements: Must Have Key Skills/Experience list (the "Must Have" bullet points)
- Qualifications: Desired Qualifications list
- Skills: Technical Skills list
Check for duplication: Required Qualifications includes many duty-like items; we are using them for Responsibilities. That's okay; they are substantive. The Must Have Key Skills/Experience list includes some overlapping items (like Workday Core HCM, Payroll, integrations, configurations, end-to-end implementations, etc.) which are more about experience/skills. We'll keep them under Requirements.
Now ensure we don't miss any substantive info:
From posting:
- Company name: Enormous Enterprise LLC (maybe not needed but could be in About the role as minor metadata)
- Location: Hopewell, NJ (also Charlotte, NC / Plano, TX) and locals/nearby only.
- Posted date: September 15, 2026 (maybe drop as minor metadata)
- Apply (drop)
- Description Senior Workday Developer/Configuration Analyst (job title, not repeat)
- Location(s): Either Hopewell, NJ / Charlotte, NC / Plano, TX --- Needs Locals or Nearby Candidates ONLY!)
- Interview Process: Online Video Interview + In-Person/Onsite interview (maybe include in About the role as a note)
- As a Workday Configuration Analyst/Developer Must Have Key Skills/Experience: list (we have)
- Job Description Role: Workday Configuration Analyst/Developer (title)
- PROJECT: International Payroll
- Must Have: Looking for resources with experience in Payroll of EMEA (Europe, Middle East, Africa) and LATAM (Latin America)
- Position Summary paragraph (we have)
- Required Qualifications list (we have as Responsibilities)
- Desired Qualifications list (we have as Qualifications)
- Technical Skills list (we have as Skills)
Also there is a line: "Workday SQL-WINDOWS Windows" maybe meaning skills: Workday, SQL-WINDOWS, Windows.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML.
We'll wrap each section in
heading then content.
For lists, use - .
For prose, use
.
We'll need to escape any HTML special characters? Not needed.
Let's craft.
About the role
:
Combine: Position Summary: "The Workday Configuration Analyst provides HR system administration, including business process configuration, reporting development, end user training, and data management in support of maintaining Workday as a best-in-class employee experience forward platform. This role will partner with the other Workday team members, IT, business partners, vendors and business leaders to effectively meet the HR technology needs of the organization. The