Senior Engagement Manager
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, remove boilerplate, navigation, legal, EEO, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to include sections only when posting has real specific content.
Let's extract content:
Intro paragraph: "Your work days are brighter here...." That's about company culture. Could be part of "About the team" or maybe a general intro. But we have sections: About The Team, About The Role, About You (Basic Qualifications, Other Qualifications). Also we have Pay Transparency Statement, Flexible Work.
We should not include "About The Team" heading if we have content. The posting includes "About The Team" paragraph. So we create
About the Team
with that paragraph.
Then About the Role
with paragraph.
Then About You
maybe split into Basic Qualifications and Other Qualifications as lists.
We need to use - for any list of duties/requirements/benefits. So Basic Qualifications and Other Qualifications are lists; we can put each as
- items.
We need to preserve all substantive information: The bullet points under Basic Qualifications: "7+ years of experience of project management with HCM, Payroll, Financial or Student implementations within medium enterprise, large enterprise, higher education and/or state and local governments." "5+years of experience implementing Workday, Oracle, SAP, PeopleSoft or similar applications."
Other Qualifications: list items: "Functional domain expertise with HCM and Payroll deployments.", "Additionally, experience in deployment of Financials product suite is helpful.", "Proven strength in customer interactions, including successfully communicating with customers to understand their needs, as well as customer experience management, including analyzing customer feedback and implementing strategies to improve their experience.", "Excellent critical thinking, to identify, understand, and generate solutions to problems", "Experienced in executive presence, demonstrating confidence, poise under pressure and the ability to communicate effectively to influence key decision-makers.", "Experienced in issue management, including identifying the root cause of issues and implementing conflict resolution techniques", "Bachelor degree or equivalent work experience; Business or Technical degree preferred.", "Ability to travel up to 30%".
We need to keep them as list items.
Pay section: Provide salary ranges. The posting includes: "Primary Location: USA.IL.Chicago Primary Location Base Pay Range: $129,000 USD - $193,400 USD Additional US Location(s) Base Pay Range: $116,600 USD - $207,200 USD Additional Considerations: If performed in Colorado, the pay range for this job is $122,800 - $184,200 USD based on min and max pay range for that role if performed in CO."
We should output as
Pay
with maybe a describing ranges. Could also use
- but it's not a list; it's prose. Use
.
Schedule section: "Our Approach to Flexible Work With Flex Work, we’re combining the best of both worlds: in-person time and remote. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. We know that flexibility can take shape in many ways, so rather than a number of required days in-office each week, we simply spend at least half (50%) of our time each quarter in the office or in the field with our customers, prospects, and partners (depending on role). This means you'll have the freedom to create a flexible schedule that caters to your business, team, and personal needs, while being intentional to make the most of time spent together. Those in our remote "home office" roles also have the opportunity to come together in our offices for important moments that matter."
We'll put that in
Schedule
.
We should not include Benefits section because no specific benefits listed.
We must remove boilerplate: EEO, scam warning, application instructions, etc. Also remove "Workday Pay Transparency Statement" heading? We can incorporate content under Pay section; we can drop the heading.
Also remove "The application deadline for this role is the same as the posting end date stated as below: 10/16/2026" - that's application instruction? It's a date; maybe we can keep as metadata? The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. The deadline is minor metadata; we could fold into a short
maybe under Pay or Schedule? Probably better to drop it as it's not substantive? It's somewhat substantive but minor. The instruction says fold minor metadata into a short
or drop it. We could include a
with the deadline maybe under a generic "Additional Information" but we shouldn't create a heading for it. Safer to drop it.
Also remove "Pursuant to applicable Fair Chance law..." etc. That's EEO/legal boilerplate; remove.
Also remove "If you require a reasonable accommodation..." etc. Remove.
Also remove "Are you being referred to one of our roles? If so, ask your connection at Workday about our Employee Referral process!" etc. Remove.
Also remove "At Workday, we value our candidates’ privacy and data security..." etc. Remove.
Also remove "Workday will never ask candidates to apply to jobs through websites that are not Workday Careers." etc. Remove.
Now produce HTML fragment.
Structure:
About the Team
...
About the Role
...
About You
- Basic Qualifications:
maybe we need to separate? Actually we could have two subheadings? But we only allowed for section headings; we could keep Basic Qualifications and Other Qualifications as inside - or just list items. The instruction: Use
- for any list of duties/requirements/benefits. So we can make a list for Basic Qualifications and another list for Other Qualifications. Could also combine into one list with headings inside
- . Better to separate:
Basic Qualifications
... but that would be another heading level () which is allowed. However we already used for section headings; we could treat Basic Qualifications as a subsection heading also . The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists Qualifications as an example. So we could have Qualifications
and then inside have two lists: Basic and Other. Or we could have Basic Qualifications
and Other Qualifications
. Both are qualifications; but the instruction's example includes Qualifications as a heading. I'd go with Qualifications
then inside have two lists with headings maybe . But to keep simple, we can do Basic Qualifications
...
Other Qualifications
...
. That uses multiple headings, which is allowed as they are section headings. The instruction didn't forbid multiple h3s; just said use for section headings (list). So okay.
Thus:
Basic Qualifications
- 7+ years of experience of project management with HCM, Payroll, Financial or Student implementations within medium enterprise, large enterprise, higher education and/or state and local governments.
- 5+ years of experience implementing Workday, Oracle, SAP, PeopleSoft or similar applications.
Other Qualifications
- Functional domain expertise with HCM and Payroll deployments.
- Additionally, experience in deployment of Financials product suite is helpful.
- Proven strength in customer interactions, including successfully communicating with customers to understand their needs, as well as customer experience management, including analyzing customer feedback and implementing strategies to improve their experience.
- Excellent critical thinking, to identify, understand, and generate solutions to problems.
- Experienced in executive presence, demonstrating confidence, poise under pressure and the ability to communicate effectively to influence key decision-makers.
- Experienced in issue management, including identifying the root cause of issues and implementing conflict resolution techniques.
- Bachelor degree or equivalent work experience; Business or Technical degree preferred.
- Ability to travel up to 30%.
Then Pay:
Pay
Primary Location (Chicago, IL) Base Pay Range: $129,000 USD - $193,400 USD. Additional US Locations Base Pay Range: $116,600 USD - $207,200 USD. If performed in Colorado, the pay range is $122,800 - $184,200 USD.
Schedule:
Schedule
With Flex Work, we combine in‑person and remote time. Rather than a set number of required office days each week, we spend at least half (50%) of our time each quarter in the office or in the field with customers, prospects, and partners (depending on role). This gives you the freedom to create a flexible schedule that meets your business, team, and personal needs while being intentional about making the most of time spent together. Remote “home office” roles also have the opportunity to come together in our offices for important moments that matter.
We should also include the introductory paragraph about culture maybe as part of About the Team? The About the Team paragraph already covers team description. The initial paragraph about "Your work days are brighter here..." is more about company culture and values. Could be included under About the Team as well, or we could create a separate section like "About Workday" but not in the list of headings. The instruction's example headings include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". But we could incorporate that intro into About the Team paragraph, or we could just drop it? It's substantive information about culture; we should preserve it. Perhaps we can add it to About the Team as an introductory paragraph before the team description. So About the Team will have two paragraphs: first the culture intro, then the team description.
Thus:
About the Team
Your work days are brighter here. We’re obsessed with making hard work pay off, for our people, our customers, and the world around us. As a Fortune 500 company and a leading AI platform for managing people, money,
for prose. We need to preserve all substantive information, remove boilerplate, navigation, legal, EEO, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include sections only when posting has real specific content. Let's extract content: Intro paragraph: "Your work days are brighter here...." That's about company culture. Could be part of "About the team" or maybe a general intro. But we have sections: About The Team, About The Role, About You (Basic Qualifications, Other Qualifications). Also we have Pay Transparency Statement, Flexible Work. We should not include "About The Team" heading if we have content. The posting includes "About The Team" paragraph. So we create
About the Team
with that paragraph. ThenAbout the Role
with paragraph. ThenAbout You
maybe split into Basic Qualifications and Other Qualifications as lists. We need to use- for any list of duties/requirements/benefits. So Basic Qualifications and Other Qualifications are lists; we can put each as
- items.
We need to preserve all substantive information: The bullet points under Basic Qualifications: "7+ years of experience of project management with HCM, Payroll, Financial or Student implementations within medium enterprise, large enterprise, higher education and/or state and local governments." "5+years of experience implementing Workday, Oracle, SAP, PeopleSoft or similar applications."
Other Qualifications: list items: "Functional domain expertise with HCM and Payroll deployments.", "Additionally, experience in deployment of Financials product suite is helpful.", "Proven strength in customer interactions, including successfully communicating with customers to understand their needs, as well as customer experience management, including analyzing customer feedback and implementing strategies to improve their experience.", "Excellent critical thinking, to identify, understand, and generate solutions to problems", "Experienced in executive presence, demonstrating confidence, poise under pressure and the ability to communicate effectively to influence key decision-makers.", "Experienced in issue management, including identifying the root cause of issues and implementing conflict resolution techniques", "Bachelor degree or equivalent work experience; Business or Technical degree preferred.", "Ability to travel up to 30%".
We need to keep them as list items.
Pay section: Provide salary ranges. The posting includes: "Primary Location: USA.IL.Chicago Primary Location Base Pay Range: $129,000 USD - $193,400 USD Additional US Location(s) Base Pay Range: $116,600 USD - $207,200 USD Additional Considerations: If performed in Colorado, the pay range for this job is $122,800 - $184,200 USD based on min and max pay range for that role if performed in CO."
We should output as
Pay
with maybe adescribing ranges. Could also use
- but it's not a list; it's prose. Use
. Schedule section: "Our Approach to Flexible Work With Flex Work, we’re combining the best of both worlds: in-person time and remote. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. We know that flexibility can take shape in many ways, so rather than a number of required days in-office each week, we simply spend at least half (50%) of our time each quarter in the office or in the field with our customers, prospects, and partners (depending on role). This means you'll have the freedom to create a flexible schedule that caters to your business, team, and personal needs, while being intentional to make the most of time spent together. Those in our remote "home office" roles also have the opportunity to come together in our offices for important moments that matter." We'll put that in
Schedule
. We should not include Benefits section because no specific benefits listed. We must remove boilerplate: EEO, scam warning, application instructions, etc. Also remove "Workday Pay Transparency Statement" heading? We can incorporate content under Pay section; we can drop the heading. Also remove "The application deadline for this role is the same as the posting end date stated as below: 10/16/2026" - that's application instruction? It's a date; maybe we can keep as metadata? The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. The deadline is minor metadata; we could fold into a short
maybe under Pay or Schedule? Probably better to drop it as it's not substantive? It's somewhat substantive but minor. The instruction says fold minor metadata into a short
or drop it. We could include a
with the deadline maybe under a generic "Additional Information" but we shouldn't create a heading for it. Safer to drop it. Also remove "Pursuant to applicable Fair Chance law..." etc. That's EEO/legal boilerplate; remove. Also remove "If you require a reasonable accommodation..." etc. Remove. Also remove "Are you being referred to one of our roles? If so, ask your connection at Workday about our Employee Referral process!" etc. Remove. Also remove "At Workday, we value our candidates’ privacy and data security..." etc. Remove. Also remove "Workday will never ask candidates to apply to jobs through websites that are not Workday Careers." etc. Remove. Now produce HTML fragment. Structure:
About the Team
...
About the Role
...
About You
- Basic Qualifications: maybe we need to separate? Actually we could have two subheadings? But we only allowed
- or just list items. The instruction: Use
- for any list of duties/requirements/benefits. So we can make a list for Basic Qualifications and another list for Other Qualifications. Could also combine into one list with headings inside
- . Better to separate:
Basic Qualifications
- ... but that would be another heading level (
- 7+ years of experience of project management with HCM, Payroll, Financial or Student implementations within medium enterprise, large enterprise, higher education and/or state and local governments.
- 5+ years of experience implementing Workday, Oracle, SAP, PeopleSoft or similar applications.
- Functional domain expertise with HCM and Payroll deployments.
- Additionally, experience in deployment of Financials product suite is helpful.
- Proven strength in customer interactions, including successfully communicating with customers to understand their needs, as well as customer experience management, including analyzing customer feedback and implementing strategies to improve their experience.
- Excellent critical thinking, to identify, understand, and generate solutions to problems.
- Experienced in executive presence, demonstrating confidence, poise under pressure and the ability to communicate effectively to influence key decision-makers.
- Experienced in issue management, including identifying the root cause of issues and implementing conflict resolution techniques.
- Bachelor degree or equivalent work experience; Business or Technical degree preferred.
- Ability to travel up to 30%.
) which is allowed. However we already used
for section headings; we could treat Basic Qualifications as a subsection heading also
. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists Qualifications as an example. So we could have
Qualifications
and then inside have two lists: Basic and Other. Or we could haveBasic Qualifications
andOther Qualifications
. Both are qualifications; but the instruction's example includes Qualifications as a heading. I'd go withQualifications
then inside have two- lists with headings maybe . But to keep simple, we can do
Basic Qualifications
- ...
Other Qualifications
- ...
headings, which is allowed as they are section headings. The instruction didn't forbid multiple h3s; just said use
for section headings (list). So okay. Thus:
Basic Qualifications
Other Qualifications
Pay
Primary Location (Chicago, IL) Base Pay Range: $129,000 USD - $193,400 USD. Additional US Locations Base Pay Range: $116,600 USD - $207,200 USD. If performed in Colorado, the pay range is $122,800 - $184,200 USD.
Schedule:Schedule
With Flex Work, we combine in‑person and remote time. Rather than a set number of required office days each week, we spend at least half (50%) of our time each quarter in the office or in the field with customers, prospects, and partners (depending on role). This gives you the freedom to create a flexible schedule that meets your business, team, and personal needs while being intentional about making the most of time spent together. Remote “home office” roles also have the opportunity to come together in our offices for important moments that matter.
We should also include the introductory paragraph about culture maybe as part of About the Team? The About the Team paragraph already covers team description. The initial paragraph about "Your work days are brighter here..." is more about company culture and values. Could be included under About the Team as well, or we could create a separate section like "About Workday" but not in the list of headings. The instruction's example headings include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". But we could incorporate that intro into About the Team paragraph, or we could just drop it? It's substantive information about culture; we should preserve it. Perhaps we can add it to About the Team as an introductory paragraph before the team description. So About the Team will have two paragraphs: first the culture intro, then the team description. Thus:About the Team
Your work days are brighter here. We’re obsessed with making hard work pay off, for our people, our customers, and the world around us. As a Fortune 500 company and a leading AI platform for managing people, money,
for section headings; we could keep Basic Qualifications and Other Qualifications as inside
- but it's not a list; it's prose. Use
- items.
We need to preserve all substantive information: The bullet points under Basic Qualifications: "7+ years of experience of project management with HCM, Payroll, Financial or Student implementations within medium enterprise, large enterprise, higher education and/or state and local governments." "5+years of experience implementing Workday, Oracle, SAP, PeopleSoft or similar applications."
Other Qualifications: list items: "Functional domain expertise with HCM and Payroll deployments.", "Additionally, experience in deployment of Financials product suite is helpful.", "Proven strength in customer interactions, including successfully communicating with customers to understand their needs, as well as customer experience management, including analyzing customer feedback and implementing strategies to improve their experience.", "Excellent critical thinking, to identify, understand, and generate solutions to problems", "Experienced in executive presence, demonstrating confidence, poise under pressure and the ability to communicate effectively to influence key decision-makers.", "Experienced in issue management, including identifying the root cause of issues and implementing conflict resolution techniques", "Bachelor degree or equivalent work experience; Business or Technical degree preferred.", "Ability to travel up to 30%".
We need to keep them as list items.
Pay section: Provide salary ranges. The posting includes: "Primary Location: USA.IL.Chicago Primary Location Base Pay Range: $129,000 USD - $193,400 USD Additional US Location(s) Base Pay Range: $116,600 USD - $207,200 USD Additional Considerations: If performed in Colorado, the pay range for this job is $122,800 - $184,200 USD based on min and max pay range for that role if performed in CO."
We should output as