Senior Cloud Solutions Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - Intro paragraph about firm: "Faegre Drinker is a firm designed for clients and designed for you. We understand that our people are critical to our success and we are committed to investing in our paraprofessional, administrative and operations professionals. We are always looking for talented, service-focused individuals to join our flexible and high-performing culture. With technology tools and resources that support our hybrid work environment, our colleagues enjoy a culture of learning, support for work and personal goals, opportunities to give back to our communities, and competitive benefits and rewards programs. At Faegre Drinker, you will have the opportunity to share your expertise within and across teams and contribute to our success." - Job Description Summary: "Faegre Drinker has an opportunity for a Senior Cloud Solutions Engineer to work with our Technology and Innovation team in our Philadelphia or Minneapolis office. You will be part of a dynamic team dedicated to analyzing our current on prem and cloud computer networks, make recommendations to implement repairs, modifications, and upgrades, with the ability to diagnose and resolve system errors and technical issues. This position will work with other talented individuals who share a passion for doing great work in the best interest of our clients." - Job Description: bullet list of duties (What you would do): list of tasks. - What Is Expected: list of abilities/skills. - What We Offer: list of benefits. - Salary range: "The anticipated initial annual salary range for someone who is hired into this position is $139,300 - $159,200. Actual initial salary may be above or below the above-identified range and will be based on the relevant skills, training, experience, and other job-related factors, including the location where the position is filled, in all cases consistent with applicable law. This is an exempt role and the initial salary range listed above is just one component of Faegre Drinker's total compensation and benefits package for professional staff, which includes, but is not limited to, a discretionary bonus; life, health, accident, and disability insurance; and a 401(k) plan." - What Is Required: list of qualifications: Bachelor's degree, 8+ years infrastructure engineering experience, 5+ years Azure and Microsoft 365 engineering experience, strong experience with list. - At end: "Apply now if you are ready to join the Faegre Drinker team!" plus E-Verify, EEO, etc. Those are boilerplate to remove. We need to decide sections. We have: - About the role / Job Description Summary: could be "About the role" or "Job Description Summary". Use

  About the role. - Responsibilities: the "What you would do" list. - Requirements / Qualifications: "What Is Required" list. - Skills: maybe "What Is Expected" could be considered Skills/Abilities. - Benefits: "What We Offer" list. - Pay: salary range. - Schedule: not mentioned; no schedule info. So we should NOT create Schedule section. We must not create sections with placeholder text. So we include only sections with real content. Thus sections: About the role, Responsibilities, Requirements, Skills (or Expected), Benefits, Pay. We need to use

  for each section heading. Inside each section, we need to use

  for prose, and

  • for any list of duties/requirements/benefits. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to copy the exact text for each bullet. Let's extract. About the role: combine the intro paragraph and Job Description Summary? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can include the intro paragraph and summary as prose under About the role. Thus

    About the role

    then

    ... (intro paragraph + summary). We need to ensure we keep all content. Intro paragraph: "Faegre Drinker is a firm designed for clients and designed for you. We understand that our people are critical to our success and we are committed to investing in our paraprofessional, administrative and operations professionals. We are always looking for talented, service-focused individuals to join our flexible and high-performing culture. With technology tools and resources that support our hybrid work environment, our colleagues enjoy a culture of learning, support for work and personal goals, opportunities to give back to our communities, and competitive benefits and rewards programs. At Faegre Drinker, you will have the opportunity to share your expertise within and across teams and contribute to our success." Job Description Summary: "Faegre Drinker has an opportunity for a Senior Cloud Solutions Engineer to work with our Technology and Innovation team in our Philadelphia or Minneapolis office. You will be part of a dynamic team dedicated to analyzing our current on prem and cloud computer networks, make recommendations to implement repairs, modifications, and upgrades, with the ability to diagnose and resolve system errors and technical issues. This position will work with other talented individuals who share a passion for doing great work in the best interest of our clients." We can combine them into one paragraph or two paragraphs. Probably better to keep as two

    elements? The rule: use

    for prose. Could have multiple

    under same section. That's fine. Thus:

    About the role

    Faegre Drinker is a firm designed for clients and designed for you. We understand that our people are critical to our success and we are committed to investing in our paraprofessional, administrative and operations professionals. We are always looking for talented, service-focused individuals to join our flexible and high-performing culture. With technology tools and resources that support our hybrid work environment, our colleagues enjoy a culture of learning, support for work and personal goals, opportunities to give back to our communities, and competitive benefits and rewards programs. At Faegre Drinker, you will have the opportunity to share your expertise within and across teams and contribute to our success.

    Faegre Drinker has an opportunity for a Senior Cloud Solutions Engineer to work with our Technology and Innovation team in our Philadelphia or Minneapolis office. You will be part of a dynamic team dedicated to analyzing our current on prem and cloud computer networks, make recommendations to implement repairs, modifications, and upgrades, with the ability to diagnose and resolve system errors and technical issues. This position will work with other talented individuals who share a passion for doing great work in the best interest of our clients.

    Now Responsibilities: the "What you would do:" list. We need to capture each bullet exactly as in posting. List: - Design, deploy, and maintain Microsoft Azure and Microsoft 365 solutions that support business and operational objectives. - Architect secure, scalable, and resilient cloud environments using Azure best practices. - Lead cloud modernization, migration, and transformation initiatives. - Build and manage hybrid identity solutions across Microsoft Entra ID, Active Directory, and Microsoft 365. - Implement and support Identity and Access Management (IAM) controls, including Conditional Access, PIM, MFA, and Zero Trust security models. - Design, manage, and secure Azure infrastructure, including networking, storage, compute, backup, and platform services. - Develop automation and Infrastructure as Code (IaC) solutions using PowerShell, Azure CLI, Bicep, ARM, or Terraform. - Manage cloud security, compliance, monitoring, vulnerability remediation, and Microsoft security technologies such as Defender and Sentinel. - Administer and govern Microsoft 365 services, including Exchange Online, Teams, SharePoint, OneDrive, and Power Platform. - Lead technical projects, establish engineering standards, mentor team members, and provide advanced operational and escalation support. We need to preserve punctuation and line breaks? We'll output as
    • each. Thus:

      Responsibilities

      • Design, deploy, and maintain Microsoft Azure and Microsoft 365 solutions that support business and operational objectives.
      • Architect secure, scalable, and resilient cloud environments using Azure best practices.
      • Lead cloud modernization, migration, and transformation initiatives.
      • Build and manage hybrid identity solutions across Microsoft Entra ID, Active Directory, and Microsoft 365.
      • Implement and support Identity and Access Management (IAM) controls, including Conditional Access, PIM, MFA, and Zero Trust security models.
      • Design, manage, and secure Azure infrastructure, including networking, storage, compute, backup, and platform services.
      • Develop automation and Infrastructure as Code (IaC) solutions using PowerShell, Azure CLI, Bicep, ARM, or Terraform.
      • Manage cloud security, compliance, monitoring, vulnerability remediation, and Microsoft security technologies such as Defender and Sentinel.
      • Administer and govern Microsoft 365 services, including Exchange Online, Teams, SharePoint, OneDrive, and Power Platform.
      • Lead technical projects, establish engineering standards, mentor team members, and provide advanced operational and escalation support.
      Now Requirements: "What Is Required" list. List: - Bachelor's degree in Computer Science, Information Technology, or equivalent experience. - 8+ years of infrastructure engineering experience. - 5+ years of Azure and Microsoft 365 engineering experience. - Strong experience with: - Microsoft Entra ID / Azure AD - Active Directory Domain Services - Conditional Access - Privileged Identity Management (PIM) - Azure Networking - Azure Virtual Machines and Platform Services - Microsoft 365 Administration including Exchange Online - PowerShell Automation - Hybrid Identity and Authentication - Experience managing enterprise-scale cloud and hybrid environments. We need to preserve the sub-bullets under "Strong experience with:" as list items? The original shows a colon then indented list. We can treat as a nested list or just flat list with those items. The instruction: Use
      • for any list of duties/requirements/benefits. So we can have a top-level list for requirements, and within that a nested list for the strong experience items. That's acceptable. Thus:

        Requirements

        • Bachelor's degree in Computer Science, Information Technology, or equivalent experience.
        • 8+ years of infrastructure engineering experience.
        • 5+ years of Azure and Microsoft 365 engineering experience.
        • Strong experience with:
          • Microsoft Entra ID / Azure AD
          • Active Directory Domain Services
          • Conditional Access
          • Privileged Identity Management (PIM)
          • Azure Networking
          • Azure Virtual Machines and Platform Services
          • Microsoft 365 Administration including Exchange Online
          • PowerShell Automation
          • Hybrid Identity and Authentication
          • Experience managing enterprise-scale cloud and hybrid environments.
        Now Skills: "What Is Expected" list. List: - Ability to problem-solve - Excellent interpersonal, verbal and written communication skills, including the ability to communicate effectively in a virtual environment (e.g., via phone, web