Cloud Infrastructure Engineer

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" and "What You Will Do" and "Essential Job Requirements" and "Skills, Knowledge, and Abilities". Also "Office Location", "Schedule", "Amount of Travel Required", "Expected salary range", "Our benefits package". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We must not repeat job title as heading. No Job ID. Remove boilerplate: disclaimers, EEO, etc. Also remove duplicated lines. Keep substantive info. We need sections only when posting has real specific content. So we can have: - About the firm? Could be "Who We Are" maybe map to About the role? But "About the role" is typical heading for description of role. However we have "Who We Are" describing firm. Could we use "About the firm"? Not in allowed headings list. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use those headings if appropriate. We need to decide which sections to include. We have content: Who We Are (firm overview). Could be placed under "About the role"? Might be odd but we could treat as "About the firm". But not in list. Perhaps we can omit that section if not matching allowed headings? But we need to preserve all substantive information. Could we put it under a

without heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. It doesn't forbid other headings, but says use

  for section headings (e.g. those). Likely they expect us to use those headings where applicable. We can still use other headings if needed, but better to stick to those. We have responsibilities: "What You Will Do:" includes many duties. That maps to Responsibilities. We have Essential Job Requirements: that could be Requirements or Qualifications. We have Skills, Knowledge, and Abilities: that maps to Skills. We have Office Location, Schedule, Amount of Travel Required, Salary range, Benefits package. We can have sections: Responsibilities (ul), Requirements (maybe combine Essential Job Requirements and Skills? But we have separate Skills section). Could do Requirements (Essential Job Requirements) and Qualifications (maybe education/certifications). But we have BS degree or equivalent experience and IT certifications within Skills section. Could treat that as Qualifications. We have Benefits: benefits package. Pay: salary range. Schedule: schedule and travel? Travel could be part of Schedule or separate but we can include travel in Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: Disclaimers, EEO, etc. We need to output only HTML fragment. Let's extract content. Who We Are: Lowenstein Sandler is a one of the most sophisticated law firms in the United States, with over 400 lawyers and 300 business services professionals serving clients from offices in New York, Palo Alto, Roseland, Salt Lake City, San Francisco, Washington, D.C., and Wilmington. We recruit candidates who seek a collaborative, entrepreneurial culture that prioritizes our clients, our colleagues, and the communities where we work and live. Committed to career development and to an inclusive workplace, the firm offers many programs and opportunities for personal and professional growth. We seek professionals for our business services group who share these values. We can put this as a

  maybe under a heading "About the firm"? Not in list. Could we omit heading and just put

  ? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but to follow the pattern we could treat "Who We Are" as a prose paragraph without heading. That's acceptable. Responsibilities: list of duties from "What You Will Do:" until before "Essential Job Requirements:"? Actually after "What You Will Do:" there is a paragraph then list of responsibilities. Let's extract: "Responsible for the day-to-day design, administration, and optimization of the firm’s cloud and hybrid infrastructure, with a primary focus on Microsoft Azure. Responds to platform alerts and incidents to troubleshoot and correct issues and maintain availability of essential systems. Partners with security, endpoint, network, and application teams to deploy and maintain production services in alignment with operational standards, governance, and compliance requirements." Then after that there is "Essential Job Requirements:" which starts a list. Thus responsibilities are those three sentences? Actually there may be more responsibilities later in the Essential Job Requirements list (like design, lead, assist, collaborate, optimize, work, implement, administer, automate, deliver, support, implement, troubleshoot, collaborate, support, evaluate, participate, respond, participate). Those are more like requirements/skills. So we treat the first block as responsibilities. We'll put them in

  • . Requirements: Essential Job Requirements list items (starting with "Design and architect end-to-end Azure infrastructure solutions..." etc). We'll extract each sentence as a list item. Qualifications: maybe education/certifications: "BS degree or equivalent experience and IT certifications." Also maybe "Minimum 5 years experience designing cloud architecture..." but that is in Skills section. Actually Skills section includes many items, including experience, proficiency, etc. So Qualifications could be education. Skills: list from "Skills, Knowledge, and Abilities:" includes many bullet-like sentences. Benefits: "Our benefits package includes coverage options for medical, dental, vision, prescription drug, life insurance, disability, FSAs, 401K, and paid time off." Pay: "The expected salary range for candidates meeting the requirements of this position is $165,000 to $175,000. The range provided is the salary that Lowenstein Sandler in good faith believes at the time of this posting that it is willing to pay for the advertised position. Exact compensation will be determined based on individual candidate qualifications and location." Schedule: "Office Location: Roseland, NJ (Hybrid) Schedule: Full-time, Monday through Friday, 9:00 AM – 5:00 PM ET Amount of Travel Required: Minimum one annual visit to the firm’s multiple offices as required." We could combine location and schedule and travel under Schedule heading? But we have separate headings for Schedule and maybe we can include location in Schedule or maybe we can create a separate heading? Not in list. Could put location in a

    without heading. Better: Use Schedule heading for schedule and travel; location maybe as a separate

    before. But we need to avoid creating sections with filler. We have real content for Schedule (full-time hours) and travel (annual visit). So we can make Schedule section with that info. We also have Office Location: we could put that as a

    before Schedule heading. Now we need to ensure we don't repeat content. Let's craft HTML:

    Who We Are: Lowenstein Sandler is a one of the most sophisticated law firms in the United States, with over 400 lawyers and 300 business services professionals serving clients from offices in New York, Palo Alto, Roseland, Salt Lake City, San Francisco, Washington, D.C., and Wilmington. We recruit candidates who seek a collaborative, entrepreneurial culture that prioritizes our clients, our colleagues, and the communities where we work and live. Committed to career development and to an inclusive workplace, the firm offers many programs and opportunities for personal and professional growth. We seek professionals for our business services group who share these values.

    Responsibilities

    • Responsible for the day-to-day design, administration, and optimization of the firm’s cloud and hybrid infrastructure, with a primary focus on Microsoft Azure.
    • Responds to platform alerts and incidents to troubleshoot and correct issues and maintain availability of essential systems.
    • Partners with security, endpoint, network, and application teams to deploy and maintain production services in alignment with operational standards, governance, and compliance requirements.

    Requirements

    • Design and architect end-to-end Azure infrastructure solutions aligned with business, security and technical requirements.
    • Lead cloud deployment initiatives, and work with the Director of Information Security to secure applications on Azure and other cloud platforms.
    • Assist in the development and enforcement of cloud architecture standards, governance frameworks, and best practices.
    • Collaborate with infrastructure, endpoint, security, and software engineering teams to ensure scalable and secure infrastructure design and compliance of cloud infrastructure systems.
    • Optimize cloud environments for cost, performance, scalability, and reliability.
    • Work with infrastructure engineers to implement and secure cloud networking solutions including VNets, VPNs, ExpressRoute, and hybrid connectivity.
    • Implement and maintain monitoring and observability across the Azure estate using Azure Monitor, Log Analytics, diagnostic settings, workbooks, and action groups; tune alerting for platform health, performance, capacity, and cost.
    • Work with the Director of Security to define and deploy Azure Policy and other initiatives to enforce governance, security baselines, resource tagging, and regulatory compliance; author custom policies and remediation tasks where built-in definitions fall short.
    • Administer Entra ID at scale: Conditional Access, Privileged Identity Management (PIM), named locations, passwordless / FIDO2 / YubiKey, administrative units, and Graph API automation.
    • Automate routine tasks and workflows using PowerShell, including modules, error handling, REST API consumption, and Microsoft Graph SDK.
    • Deliver infrastructure as code using Bicep, Terraform, or equivalent tooling.
    • Support and enhance Microsoft 365 services including Exchange Online, Teams, SharePoint, and Intune.
    • Implement and maintain hybrid environments integrating on-premises systems with Azure AD.
    • Troubleshoot complex infrastructure issues and provide root cause analysis.
    • Collaborate with security team to enforce compliance, patching, and vulnerability management.
    • Support backup, disaster recovery, and business continuity strategies.
    • Evaluate emerging technologies and recommend improvements to cloud architecture strategy.
    • Participate in infrastructure projects, upgrades, and migrations.
    • Respond to system and security alerts as required to maintain up-time and system performance.
    • Participate in on-call rotation once a month.

    Skills

    • Minimum 5 years experience designing cloud architecture and contributing to cloud strategy and standards.
    • Experience designing and supporting Azure infrastructure (IaaS, PaaS, networking, and identity).
    • Experience using Azure Monitor, Log Analytics, and related tools to monitor and troubleshoot platform health.
    • Experience implementing governance and compliance controls using Azure Policy and related standards.
    • Familiarity with best practices for securing cloud infrastructure and applications.
    • Experience administering Entra ID, including Conditional Access, Privileged Identity Management (PIM), and passwordless authentication (FIDO2 / YubiKey).
    • Experience delivering infrastructure as code using Bicep, Terraform, or equivalent tools.
    • Proficiency with PowerShell scripting and automation, including Microsoft Graph SDK.
    • Strong Windows Server administration skills and experience supporting hybrid environments.
    • Experience administering Active Directory and Group Policy in an enterprise environment.
    • Experience supporting Microsoft 365 services such as Exchange Online