M&A Integration Technology Lead
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse.
Job description includes:
- Intro paragraph: "Become a part of our caring community The M&A IT integration leader will provide strategic guidance ..." This is about the role. Could be "About the role". We'll put that in About the role
then
with that paragraph. - Responsibilities: multiple bullet points under "Key Responsibilities" with subheadings: IT Due Diligence, IT Integration Planning & Execution, IT Integration Governance & Process Excellence, Integration Results & Value Realization. We need to output a
- for any list of duties/requirements/benefits. So we can list each responsibility as
- . Probably combine all responsibilities into a single list.
- Requirements: "Required Qualifications" includes bullet list of qualifications. We'll put under
Requirements
with- .
- Qualifications: "Preferred Qualifications" includes bullet list. Could be under
Qualifications
(or maybe separate sections: Required Qualifications and Preferred Qualifications). The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements for required qualifications, Qualifications for preferred qualifications. Or we could combine but better separate. - Skills: Not explicitly listed; but we could infer from qualifications. However we should only include a section if posting has real specific content. There's no explicit "Skills" heading; but we could treat qualifications as skills? Might be better to omit Skills section if not explicit. The instruction: "Prefer a few substantive sections over many thin ones." So we may omit Skills if not directly given. - Benefits: There's "Description Of Benefits" paragraph. So includeBenefits
withdescribing benefits. - Pay: There's "Pay Range" with $142,300 - $195,700 per year, plus bonus incentive plan. So include
Pay
with. - Schedule: There's "Scheduled Weekly Hours 40". Also mention remote but must reside within commutable distance. Travel occasional. So we can include Schedule section with that info. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is Equal Opportunity Employer paragraph; we should remove that. Also "About Us" maybe not needed? It's not a required heading but could be considered "About the role"? Actually "About Us" is company description; could be considered part of About the role? Might be okay to include in About the role paragraph? But we already have intro about role. The "About Us" is separate; we could include it in About the role as additional context? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that info somewhere. Could add another paragraph under About the role after the initial description. Or we could create a separate section like "About the company" but not in allowed headings. Since only allowed headings are those listed, we could put company description under About the role as well. That seems okay. We must not include EEO paragraph; remove. Also remove "Work at Home Requirements:" maybe that's part of Schedule? It's about internet speed and dedicated space. Could be part of Schedule or maybe a separate section like "Work Requirements" but not in allowed headings. Could incorporate into Schedule or maybe under Responsibilities? Probably better to include under Schedule as additional details (like remote work requirements). However Schedule heading is for schedule; but we can still include other details like remote work requirements under Schedule? Might be stretching. Could create a separate section like "Requirements" already used for qualifications; but we could add a sub-list under Requirements for work-from-home requirements. However the instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can only use those headings. So we need to fit all info under those headings. Thus: - About the role: include intro paragraph + company description (About Us) maybe. - Responsibilities: list of duties. - Requirements: required qualifications. - Qualifications: preferred qualifications. - Benefits: benefits description. - Pay: pay range and bonus. - Schedule: scheduled weekly hours, remote work, travel, internet speed, dedicated space. We must not include Skills section (no explicit content). So omit. Now craft HTML. We need to ensure proper nesting:
About the role
...
etc. For lists:- ...
- with each bullet as
- . Might be long but okay. Now Requirements (Required Qualifications): List: - Bachelor's degree in Information Technology, Computer Science, Management Information Systems, Engineering, or related field. - 8+ years of progressive technology leadership experience, including experience in one or more of the following areas: * Enterprise applications and systems integration, architecture or technology transformation initiatives * Infrastructure, networking, and end-user computing * Cloud platforms and migration programs (Azure, AWS, or GCP) * Cybersecurity, identity and access management, and risk management * Data management, analytics, and information governance * IT program/project delivery in large, complex organizations - 8+ years of experience supporting mergers, acquisitions, divestitures, business transformations, or large-scale enterprise integration initiatives. - 8+ years of project, program, or cross-functional team leadership experience developing technology roadmaps, integration strategies, business cases, and executive-level presentations. - Demonstrated ability to influence and communicate effectively with executive leadership, technical teams, external partners, and acquired company representatives. - Strong understanding of IT governance, technology risk management, cybersecurity principles, and enterprise architecture concepts. We need to preserve the nested bullet structure? We can flatten but keep details. Use
- for each top-level bullet; sub-bullets could be separate
- indented? Simpler: each line as separate
- . We'll keep the sub-items as separate
- but maybe preceded by a dash. That's okay. Now Qualifications (Preferred Qualifications): List: - Direct IT M&A Leadership Experience: 10+ years leading IT due diligence, integration, or separation activities across mergers, acquisitions, divestitures, or joint ventures, preferably within a highly regulated industry such as healthcare, financial services, or insurance. - Experience with Microsoft Azure, AWS, or hybrid cloud environments. - Experience integrating enterprise platforms such as Microsoft 365, Active Directory/Azure AD (Entra ID), Salesforce, ServiceNow, ERP systems, or healthcare technology platforms. - Familiarity with cybersecurity frameworks, identity management, data migration, and application rationalization activities. - Experience using portfolio, project, and integration management tools such as Jira, Azure DevOps, Smartsheet, Clarity, or ServiceNow. - Relevant Professional Certifications: One or more of the following: * Project Management Professional (PMP) * TO
- .
- Qualifications: "Preferred Qualifications" includes bullet list. Could be under