Microsoft M365 Senior Technology Manager
ALPFA Baltimore Chapter · Charlotte, NC · 1 mo ago
Engineering$136k–$220k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have description (About the role) content: the initial paragraphs about Bank of America purpose, culture, etc. That can be About the role. Then Responsibilities: there is a "Responsibilities" heading with bullet list. Also there are sub-sections like Managerial Responsibilities, Enterprise Microsoft 365 Operational Leadership, etc. Those are part of responsibilities. We'll combine them under Responsibilities.
Requirements: there is "Required Qualifications" and "Desired Qualifications". Those can be Requirements (maybe split into Required and Desired). But we can have a Requirements section with both required and desired? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Qualifications separate? Actually they list both Requirements and Qualifications as possible headings. We need to decide based on content. The posting has "Required Qualifications" and "Desired Qualifications". That fits under Qualifications heading. Also there is "Skills" heading with list of skills. So we can have Qualifications and Skills sections.
Pay: there is Pay range and discretionary incentive. So Pay section.
Schedule: there is Shift 1st shift (United States of America) Hours Per Week 40. So Schedule section.
Benefits: there is mention of benefits earlier: "affordable, competitive and flexible benefits" but not detailed. There's also "Discretionary incentive eligible". That's more pay. There's no explicit benefits list like health, retirement. So we should not create Benefits section unless specific content. The posting mentions benefits in the intro but not specific. The rule: never create Benefits section unless posting actually states them. It does mention "affordable, competitive and flexible benefits" but not details. Might be considered vague. Safer to omit Benefits.
We also need to include metadata like Job ID etc folded into short p or drop. There's no explicit Job ID.
We must remove boilerplate: the AI insights disclaimer repeated, etc. Also remove navigation, EEO, etc. Not present.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
Structure:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have description (About the role) content: the initial paragraphs about Bank of America purpose, culture, etc. That can be About the role. Then Responsibilities: there is a "Responsibilities" heading with bullet list. Also there are sub-sections like Managerial Responsibilities, Enterprise Microsoft 365 Operational Leadership, etc. Those are part of responsibilities. We'll combine them under Responsibilities.
Requirements: there is "Required Qualifications" and "Desired Qualifications". Those can be Requirements (maybe split into Required and Desired). But we can have a Requirements section with both required and desired? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Qualifications separate? Actually they list both Requirements and Qualifications as possible headings. We need to decide based on content. The posting has "Required Qualifications" and "Desired Qualifications". That fits under Qualifications heading. Also there is "Skills" heading with list of skills. So we can have Qualifications and Skills sections.
Pay: there is Pay range and discretionary incentive. So Pay section.
Schedule: there is Shift 1st shift (United States of America) Hours Per Week 40. So Schedule section.
Benefits: there is mention of benefits earlier: "affordable, competitive and flexible benefits" but not detailed. There's also "Discretionary incentive eligible". That's more pay. There's no explicit benefits list like health, retirement. So we should not create Benefits section unless specific content. The posting mentions benefits in the intro but not specific. The rule: never create Benefits section unless posting actually states them. It does mention "affordable, competitive and flexible benefits" but not details. Might be considered vague. Safer to omit Benefits.
We also need to include metadata like Job ID etc folded into short p or drop. There's no explicit Job ID.
We must remove boilerplate: the AI insights disclaimer repeated, etc. Also remove navigation, EEO, etc. Not present.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
Structure:
About the role
... (combined intro paragraphs)
Responsibilities
- ... each bullet
- for any list. Could have two subheadings? Not allowed; only headings from list. Could have Qualifications section with two paragraphs: Required and Desired. But we need to preserve all info. Could do:
Qualifications
Required Qualifications:
- ...
Desired Qualifications:
- ...