Cyber - SOAR (Security Orchestration, Automation and Response) Engineer - Manager - Consulting
EY · Phoenix, AZ · 1 mo ago
Hybrid$174k–$290k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes location line, then intro paragraphs. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions.
We need to preserve all substantive information.
Let's parse content:
Location: Anywhere in Country (maybe irrelevant). At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. The Opportunity ... (description). Then "Your Key Responsibilities" list bullet points. Then "Skills And Attributes For Success" bullet points. Then "To Qualify for the Role, You Must Have" bullet points. Then "Ideally, You'll Also Have" bullet points. Then "What We Look For" paragraph. Then "What We Offer You At EY" paragraph includes salary ranges and benefits. Then "Are you ready..." etc (application instructions) which we should remove. Also EEO etc at end.
We need sections: About the role (maybe the intro paragraphs before responsibilities). Responsibilities (Your Key Responsibilities). Requirements? The posting has "To Qualify for the Role, You Must Have" which is qualifications. Also "Ideally, You'll Also Have" could be additional qualifications or preferred qualifications. Could combine into Requirements/Qualifications. Skills: "Skills And Attributes For Success". Benefits: "What We Offer You At EY" includes benefits and salary. Pay: salary ranges. Schedule: not mentioned. So we should not include Schedule section.
We need to avoid filler like "commensurate with experience". Not present.
We need to output HTML fragment only.
Structure: maybe:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions.
We need to preserve all substantive information.
Let's parse content:
Location: Anywhere in Country (maybe irrelevant). At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. The Opportunity ... (description). Then "Your Key Responsibilities" list bullet points. Then "Skills And Attributes For Success" bullet points. Then "To Qualify for the Role, You Must Have" bullet points. Then "Ideally, You'll Also Have" bullet points. Then "What We Look For" paragraph. Then "What We Offer You At EY" paragraph includes salary ranges and benefits. Then "Are you ready..." etc (application instructions) which we should remove. Also EEO etc at end.
We need sections: About the role (maybe the intro paragraphs before responsibilities). Responsibilities (Your Key Responsibilities). Requirements? The posting has "To Qualify for the Role, You Must Have" which is qualifications. Also "Ideally, You'll Also Have" could be additional qualifications or preferred qualifications. Could combine into Requirements/Qualifications. Skills: "Skills And Attributes For Success". Benefits: "What We Offer You At EY" includes benefits and salary. Pay: salary ranges. Schedule: not mentioned. So we should not include Schedule section.
We need to avoid filler like "commensurate with experience". Not present.
We need to output HTML fragment only.
Structure: maybe:
About the role
... intro paragraphs ...
Responsibilities
- ... each bullet ...
Qualifications
- ... from To Qualify ...
Preferred Qualifications
but not in list of allowed headings; we have Skills, Requirements, Qualifications. We could put "Ideally, You'll Also Have" under Qualifications as well, or maybe under Skills? Better to keep Qualifications covering both required and preferred, but we could split into two- with headings? Not allowed extra headings. Could combine into one list with both required and preferred items, but we might lose distinction. However we must preserve all substantive information; we can include both sets in same list, maybe with a note? But we cannot add extra headings. Could include a
before list describing required vs preferred. That's okay. Skills section: