Senior Modern Work Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key content: - Intro: "This is an opportunity to join our team of top-notch modern work engineers working closely together on interesting projects for our clients. This position is fully remote (indefinitely). ** Emergent Software is looking for a Senior Modern Work Engineer with deep experience delivering secure Microsoft 365 Modern Work solutions. This role leads mid- to large-sized client engagements from discovery through delivery, serves as the primary technical point of contact, and translates business requirements into scalable, supportable solutions. A qualified candidate brings strong consulting communication, architecture, automation, and troubleshooting skills; can guide teams and mentor engineers; and proactively manages delivery risks, dependencies, and outcomes. This 100% remote position is ideal for a smart, passionate, and curious self-starter." - Highlights & Benefits Of Working At Emergent Software: bullet list: Work closely with other talented engineers and team members. Our vetting process means you can count on your team members to know what they are talking about. Work from home or work remotely from anywhere you want. Flexible work schedule meaning you can work regular hours or whenever you work best. Work-life balance is essential and highly valued at Emergent Software. If you choose to work more than 40 hours, you’ll be compensated for the extra work! Work on interesting projects solving complex business problems with custom software. 100 hours per year to focus on your professional development. We invest in your growth! Profit sharing bonus means as we’re successful, you’re successful. Excellent benefits package including medical insurance, dental, vision, 401(k) matching, FSA, disability, life insurance, and paid parental leave. - Typical Tech Stack: list of technologies. - Primary Duties: bullet list with subheadings? Actually they have headings: Engagement Leadership and Accountability:, Client Communication and Requirements:, Architecture and Solution Design:, Security and Copilot Readiness:, Standardization and Automation:, Problem Solving and Technical Leadership:, Teamwork and Practice Contribution:. Each bullet with description. - Required Qualifications: list of bullet points. - Nice To Have Experience: list. - Our Vetting Process: steps. - Benefits Package Details: list with specifics. - About Emergent Software: paragraphs. We need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must decide which sections have content. - About the role: we can put the introductory paragraph describing role. - Responsibilities: we can use Primary Duties. - Requirements: maybe Required Qualifications. - Qualifications: maybe Nice To Have? But they said Qualifications separate from Requirements? Usually Requirements = required qualifications. Qualifications could be nice-to-have? But we need to avoid duplication. Could treat Required Qualifications as Requirements, and Nice To Have as Qualifications (or Skills). However they also have Skills section: maybe we can put Technical Skills (Tech Stack) under Skills. - Benefits: we have Highlights & Benefits and Benefits Package Details. - Pay: we have profit sharing bonus, extra compensation for >40 hours, maybe also mention profit sharing up to 15% salary, extra compensation. Also maybe mention salary? Not given. So we can include Pay section with profit sharing bonus and extra compensation. - Schedule: we have flexible work schedule, work from home, remote, work regular hours or whenever you work best, compensation for >40 hours. So schedule section. We must not include sections with filler like "commensurate with experience". Not present. We must not repeat job title. We must not include Job ID etc. We must not include boilerplate like cookie/navigation/legal/EEO etc. Not present. We must not include application instructions (like "Apply now"). We must not include duplicated lines. We must preserve all substantive info. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

...intro...

Responsibilities

• Engagement Leadership and Accountability: Lead mid- to large-sized engagements end-to-end by establishing scope, sequencing work, setting expectations, monitoring delivery, and serving as the primary technical point of contact. Own delivery outcomes for assigned workstreams and proactively surface risks, dependencies, decisions, and changes.
...

Requirements

• Previous consulting or professional services experience, including working directly with customer teams of varying sizes.
...

Qualifications

• Nice To Have Experience: Hands-on experience with Microsoft 365 Copilot, Copilot Studio, or agent-based solutions, including readiness, governance, security, and adoption considerations.
...

Skills

• Microsoft 365 Defender suite
• Microsoft 365 (Teams, SharePoint, OneDrive, Exchange)
• Entra ID
• Microsoft Intune
• Microsoft Sentinel
• Microsoft Information Protection (Purview)
• Data Loss Prevention (DLP)
• PowerShell
• Microsoft 365 Copilot & Copilot Studio
• Power Automate
• Migration Tools (BitTitan, ShareGate, AvePoint, Quest)

Benefits

• Work closely with other talented engineers and team members. Our vetting process means you can count on your team members to know what they are talking about.
• Work from home or work remotely from anywhere you want.
• Flexible work schedule meaning you can work regular hours or whenever you work best.
• Work-life balance is essential and highly valued at Emergent Software. If you choose to work more than 40 hours, you’ll be compensated for the extra work!
• Work on interesting projects solving complex business problems with custom software.
• 100 hours per year to focus on your professional development. We invest in your growth!
• Profit sharing bonus means as we’re successful, you’re successful.
• Excellent benefits package including medical insurance, dental, vision, 401(k) matching, FSA, disability, life insurance, and paid parental leave.
• Medical Insurance: up to 80% of your monthly medical premium (HSA options available)
• HSA Contribution: up to $200/month
• Dental & Vision Insurance: up to 50% of your monthly dental and vision premium costs
• 401(k) plan: company match up to 4% of salary
• Profit sharing bonus: up to 15% of salary paid quarterly
• Extra compensation: get paid extra for work over 40 hours/week
• Employee referral & customer referral bonuses
• Flex Spending Account (FSA) for Dependent Care & Healthcare Costs
• Dependent Care FSA Contribution: $90/month
• Short Term Disability: $500/week for 12 weeks
• Long Term Disability: up to $6,000/month
• Group term life and AD&D insurance: $50k
• PTO, standard holidays, 2 floating holidays
• Paid parental leave: 2 weeks
• Staff development program: 100 hours/year plus training costs

Pay

• Profit sharing bonus: up to 15% of salary paid quarterly
• Extra compensation: get paid extra for work over 40 hours/week

Schedule

• Fully remote (indefinitely)
• Flexible work schedule: work regular hours or whenever you work best
• Work from home or work remotely from anywhere you want
• Compensation for work over 40 hours/week

We need to ensure we didn't duplicate content. Some items appear both in Benefits and Pay; but it's okay as they are distinct sections. However we might want to avoid duplication: Pay section could just mention profit sharing and extra compensation; Benefits section includes those as well but it's okay to repeat? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but might be considered redundant. However we could keep Pay separate with those details, and Benefits could omit profit sharing and extra compensation to avoid duplication. But the Benefits section originally includes those points; we could keep them there and Pay could be omitted if no unique info. However they said include a section ONLY when posting has real, specific content for it. Pay section: we have profit sharing bonus and extra compensation; that is specific content. So we should include Pay. Benefits section also includes those; but we could keep them in Benefits as part of benefits package details. It's okay to have overlapping info; but maybe better to keep Pay separate and Benefits exclude profit sharing and extra compensation to avoid duplication. However the Benefits Package Details includes those items; we could keep them there and Pay could be omitted. But then we would lose the Pay section despite having content. The instruction: Prefer a few substantive sections over many thin ones. Having both Benefits and Pay might be thin. But we could combine Pay into Benefits? However they ask to use headings for Benefits, Pay, Schedule separately if content exists. So we need to decide. We could keep Benefits as the highlights and benefits package details (excluding profit sharing and extra compensation) and Pay as profit sharing and extra compensation. Let's extract from Benefits Package Details: medical insurance, HSA, dental/vision, 401k, profit sharing, extra compensation, referral bonuses, FSA, disability, life insurance, PTO, holidays, paid parental leave, staff development. Thus Benefits section can include all those except profit sharing and extra compensation? But profit sharing and extra compensation are part of benefits package details; but we could still include them there and Pay could be omitted. However then we would not have Pay section despite having content. The instruction: "include a section ONLY when the posting has real, specific content for it". It doesn't forbid having overlapping content; but we should not create a section with filler. Pay section has real specific content (profit sharing bonus, extra compensation). So we should include Pay. Benefits section also has real specific content (medical, dental, etc). So both are fine. Thus we can keep both sections with overlapping items; it's okay. Now we need to ensure we didn't include boilerplate like "Our Vetting Process". That's not a section heading we need to output; we could ignore it because not in list of allowed headings. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not output headings for Vetting Process, About Emergent Software, etc. We must drop those sections. However we must preserve ALL substantive information; does that mean we need to include that info somewhere else? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to drop "Our Vetting Process" or "About Emergent Software". But the allowed headings list only includes those specific ones. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements,