Infrastructure Engineer

We need to output HTML fragment with sections: About the role (but we already have About Us and About The Role). The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a 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. We need to include sections only when posting has real, specific content. So we need sections: About the role (maybe from "About The Role" paragraph). Responsibilities (list of primary responsibilities). Requirements (maybe "Required Qualifications"). Qualifications? Actually they have Required Qualifications and Preferred Skills. Could combine into Requirements and Preferred Skills? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide which sections to include based on content. We have: - About Us (company description) - not a required heading but could be included? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow those examples. Probably we should include About the role (the paragraph after "About The Role"). - Responsibilities: list of primary responsibilities (bulleted). We'll output

• for each. - Requirements: maybe "Required Qualifications". Could be heading "Required Qualifications" but instruction says use headings like Requirements, Qualifications. We could use "Requirements" heading and put the required qualifications list. - Qualifications: maybe "Preferred Skills" could go under "Preferred Skills" heading (Skills). Or we could combine under "Skills". The instruction says we can use Skills heading. So we could have a Skills section for preferred skills. - Benefits: we have "What Orveon Offers You" with bullet list of benefits. So Benefits heading. - Pay: we have pay range. So Pay heading. - Schedule: we have hybrid model details (3 days per week in office, work from anywhere 6 weeks). That's schedule info. So Schedule heading. We must not include boilerplate like EEO, fraud warnings, etc. We must not repeat job title as heading. Not present. We must not include duplicated lines. We need to preserve all substantive information. So we need to include the About Us description? The instruction didn't list About Us as a heading but we could include it as a paragraph before sections? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should likely include About Us as a paragraph (

  ) maybe without heading? The instruction says "Prefer a few substantive sections over many thin ones." Could include About Us as a paragraph before sections. But we need to output only HTML fragment, no /. So we can start with

  About Us ...

  then

  About the role

  etc. We must ensure we don't include filler like "commensurate with experience" etc. In Required Qualifications they have "Bachelor’s degree in Computer Science, Information Technology, or commensurate experience." That's a phrase "commensurate experience" which is filler? It's part of the requirement; we should keep it as it's substantive? It's not a placeholder like "N/A". It's okay. We must not include sections with only filler. All sections we add have content. Now let's extract content. About Us paragraph: "Orveon is a new kind of beauty company on a powerful mission: to change the way the world thinks about beauty. We dare to do things differently — pushing boundaries with purpose, inspiring creativity, and moving with intention in everything we do. We are a collective of three premium and prestige beauty brands: bareMinerals, BUXOM, and Laura Mercier. With offices in New York, London, and Columbus, we combine the energy of an entrepreneurial spirit with the scale and ambition to change the way the world thinks about beauty. Our culture is built on our IMPACT values — Innovative, Motivated, Passionate, Accountable, Collaborative, and Thoughtful. These aren't just words; they define how we show up for each other, for our brands, and for the world around us. We gain strength from our differences and believe that progress happens when we move as one. We are proud to offer a hybrid work model to support the work-life balance of our teams, and we are committed to fostering an inclusive, agile environment where everyone can thrive." That's substantive. About The Role paragraph: "We are seeking a skilled Infrastructure Engineer to join our Infrastructure and Security team to manage our Microsoft 365, Azure and other cloud/SaaS environments. This role is pivotal in designing, implementing, and managing enterprise-scale cloud environments that support business-critical applications and services while maintaining our overall security posture. In addition to cloud engineering responsibilities, this role will act as the face of IT and escalation point for the users at our New York office, facilitating timely resolution of technical issues and maintaining high levels of user satisfaction." We'll put that under

  About the role

  as a

  . Responsibilities: list under "Primary Responsibilities". The text after that heading includes a run-on sentence with periods but we need to split into bullet points. Let's parse: "Microsoft 365 Security Administration (Exchange 365, Teams, SharePoint 365, Entra ID).Implement compliance and data governance policies using Purview.Oversee Azure services and enforce security best practices.Design and deploy scalable, secure, and resilient cloud solutions.Manage and monitor Azure infrastructure, ensuring performance, reliability, and cost optimization.Monitor identity and access management controls.Support integration and security for multiple SaaS platforms.Ensure compliance with security policies and best practices using Entra ID, RBAC, Azure Key Vault, and secure linked services.Troubleshoot and resolve issues related to cloud infrastructure and services.Provide technical guidance and mentorship on Azure and other cloud technologies.Stay up to date with Azure innovations and recommend improvements.Document support procedures and contribute to knowledge base articles for recurring issues.Deliver frontline support for end users in the New York office, including:Triaging hardware/software issues.Administering local physical and wireless networks.Coordinating with remote support teams." We need to split each sentence into separate

• . Ensure we keep the content. Let's list: 1. Microsoft 365 Security Administration (Exchange 365, Teams, SharePoint 365, Entra ID). 2. Implement compliance and data governance policies using Purview. 3. Oversee Azure services and enforce security best practices. 4. Design and deploy scalable, secure, and resilient cloud solutions. 5. Manage and monitor Azure infrastructure, ensuring performance, reliability, and cost optimization. 6. Monitor identity and access management controls. 7. Support integration and security for multiple SaaS platforms. 8. Ensure compliance with security policies and best practices using Entra ID, RBAC, Azure Key Vault, and secure linked services. 9. Troubleshoot and resolve issues related to cloud infrastructure and services. 10. Provide technical guidance and mentorship on Azure and other cloud technologies. 11. Stay up to date with Azure innovations and recommend improvements. 12. Document support procedures and contribute to knowledge base articles for recurring issues. 13. Deliver frontline support for end users in the New York office, including: - Triaging hardware/software issues. - Administering local physical and wireless networks. - Coordinating with remote support teams. We could keep the sub-bullets as part of the same li or separate. Simpler: keep as one li with colon and subitems separated by commas or semicolons. But better to keep as one li with the subitems as separate sentences? We'll keep as one li: "Deliver frontline support for end users in the New York office, including: Triaging hardware/software issues; Administering local physical and wireless networks; Coordinating with remote support teams." Now Required Qualifications: list: - 3+ years of experience administering Microsoft 365 (Outlook, Teams, SharePoint, Entra, Purview). - 3+ years of experience in cloud infrastructure role (Azure and others) - Strong understanding of Azure infrastructure and security principles. - Familiarity with SaaS application management and security. - Proficiency in Azure services including Azure Data Factory, Azure Synapse, Azure SQL, Azure Blob Storage, Azure Purview. Entra ID, RBAC, Azure Key Vault, and secure linked services - Experience with Microsoft Fabric, Power BI, and cloud-based reporting tools. - Experience with scripting languages (Python, Bash, PowerShell). - Experience providing hands-on technical support in a multi-office environment. - Bachelor’s degree in Computer Science, Information Technology, or commensurate experience. We need to ensure we keep the content exactly. Some lines have missing punctuation; we can keep as is. Preferred Skills: list: - Microsoft Certified: Azure Administrator Associate (highly preferred) - Microsoft Certified: Security, Compliance, and Identity Fundamentals (highly preferred) - CompTIA Security+ or CISSP - Certifications such as AZ-104 Azure Fundamentals or AZ-305 Designing Azure Infrastructure. - Experience in GCP infrastructure - Familiarity with security frameworks and penetration testing protocols. - Good understanding of Wireless networks - Excellent problem-solving, communication, and collaboration skills. - Ability to work independently and manage support requests efficiently. We'll put under

  Skills

  maybe. Benefits: list from "What Orveon Offers You": - “Hybrid First” Model – 3 days per week in office, balancing virtual and face-to-face interactions. - “Work From Anywhere” – Freedom to work six (6) weeks annually from the location of your choice. - Complimentary Products – Free and discounted products on new releases and fan-favorites. - Professional Development – Exposure to senior leadership, learning and development programs, and career advancement opportunities. - Community Engagement – Volunteer opportunities in the communities in which we live and work. We'll put under

  Benefits

  . Pay: The pay range paragraph: "Pay Transparency - One of our values is Stark Honesty and the following represents a good faith estimate of the compensation range for this position. At Orveon Global, we carefully consider a wide range of non-discriminatory factors when determining salary. Actual salaries will vary depending on factors including but not limited to location, education, experience, and qualifications. The pay range for this position is $98,000-$130,000. Supplemented with all the amazing benefits above for full-time employees!" We need to keep substantive info: pay range $98,000-$130,000. We can include the preceding sentences as they are substantive? They are somewhat boilerplate but still part of posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those; it's about pay transparency. It's okay to keep. We'll keep the whole paragraph but maybe we can trim to just the range? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the whole paragraph as is. Schedule: The hybrid model details are already in Benefits (Hybrid First Model, Work From Anywhere). But schedule could be separate. However we already have schedule info in Benefits. The instruction says include a section ONLY when the posting has real, specific content for it. We have schedule info in Benefits; we could still have a Schedule section but that would duplicate. Better to not duplicate; we can put schedule info under Benefits or Schedule. Since we already have Benefits covering hybrid model and work from anywhere, we could keep Benefits and not have separate Schedule. But the instruction says we can use Schedule heading