DevOps Engineer
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 info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove Interview Technology Notice and Text Messaging Notice? Those are likely boilerplate; they are not part of job description content. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Interview Technology Notice and Text Messaging Notice are likely part of application instructions, so remove them.
We need to include sections only when posting has real, specific content. The posting includes:
- Intro about company (Established in 2021...). That could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: maybe the Role Summary paragraph.
- Responsibilities: Key Responsibilities bullet list.
- Requirements: maybe Required Qualifications.
- Qualifications: maybe Preferred Qualifications? But they said use both Requirements and Qualifications sections. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications (or Skills). But we also have Skills maybe from required qualifications? Could combine.
We need to avoid filler sections like Pay or Schedule if not present. The posting does not mention pay or schedule. So we should not include Pay or Schedule sections.
Benefits: there is a benefits list after "#iph". So we should include Benefits section.
Thus sections: About the role (Role Summary), Responsibilities (Key Responsibilities), Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Benefits (benefits list). Possibly Skills? Could embed skills within qualifications. But we could also create a Skills section if there is explicit skills list. The posting includes many skill-like items in qualifications. Might be okay to not create separate Skills.
We must use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, required qualifications, preferred qualifications, benefits.
We need to ensure we don't include boilerplate like "Established in 2021, Independence Pet Holdings is a corporate holding company..." That's substantive about company; we can include in About the role? Actually About the role should be role summary. The company description could be part of About the role or maybe we could include a brief About the company paragraph. The instruction says use headings like About the role, Responsibilities, etc. It didn't forbid adding an About the company paragraph under About the role? Might be okay to include company description as part of About the role (since it's about the role's context). But we need to preserve all substantive info; we can include it in a
under About the role.
Let's extract sections:
Company description: "Established in 2021, Independence Pet Holdings is a corporate holding company that manages a diverse and broad portfolio of modern pet health brands and services, including insurance, pet education, lost recovery services, and more throughout North America. We believe pet insurance is more than a financial product and build solutions to simplify the pet parenting journey and help improve the well-being of pets. As a leading authority in the pet category, we operate with a full stack of resources, capital, and services to support pet parents. Our multi-brand and omni-channel approach include our own insurance carrier, insurance brands and partner brands."
Role Summary: "This role provisions, manages, and supports cloud infrastructure and DevOps capabilities for Clarus DevOps workloads. The Cloud Engineer translates architecture decisions and platform requirements into production-ready Terraform modules and reliable CI/CD pipelines covering compute, storage, PaaS services, environment scaffolding, and deployment automation. The role partners closely with application teams, DevOps leads, networking, security, and operations to deliver governed, reproducible, supportable, and cost-aware infrastructure aligned to Calandra Blueprint and Azure Landing Zone standards."
We could combine company description and role summary under About the role.
Responsibilities: list bullet points under Key Responsibilities.
Let's extract each bullet:
- Provision Clarus workload-specific Azure resources - compute (VMs, AKS), storage, PaaS services (Container Apps, App Services, Azure Functions, Azure SQL, Cosmos DB), Key Vault, and managed identities per architecture-approved patterns.
- Author and maintain Terraform IaC modules - resource provisioning, testing, peer review, versioning, and CI validation for reusable workload and platform components.
- Build, maintain, and support CI/CD pipelines - Azure DevOps YAML pipelines, reusable templates, build and release stages, approvals, quality gates, and environment-specific deployment flows.
- Troubleshoot pipeline and deployment issues - failed builds, blocked releases, service connection problems, agent pool issues, package or artifact failures, container image deployments, and rollback scenarios.
- Manage secure deployment integrations - Azure service connections, federated credentials, managed-identity authentication, Key Vault-backed secrets, artifact feeds, container registries, and least-privilege access patterns.
- Scaffold and manage workload landing-zone structures - subscriptions, resource groups, RBAC assignments, tagging, Azure Policy, and dev / stg / prd environment alignment within the Calandra Azure Landing Zone.
- Integrate workload resources with shared network services - private endpoints, VNet integration, DNS registration, firewall rule requests, and connectivity validation for Clarus environments.
- Maintain environment parity and operational readiness - governance guardrails, policy compliance, cost tagging, quota management, secure defaults, runbooks, and release support procedures.
- Support DevSecOps controls - pipeline security checks, SAST integration, dependency scanning, infrastructure validation, branch policies, pull request checks, and audit-friendly deployment evidence.
- Monitor resource health, cost, and compliance - contribute to observability dashboards, alerting baselines, incident troubleshooting, and cost optimization recommendations.
That's all.
Required Qualifications (list):
- 3-5 years in Cloud Engineering or DevOps engineering, with hands-on Azure infrastructure provisioning and operational support experience.
- Proven Terraform skills - authoring, testing, reviewing, and maintaining modules in a team environment with CI validation.
- Strong CI/CD pipeline experience - Azure DevOps, YAML pipeline authoring, reusable templates, approvals, quality gates, and release troubleshooting.
- Working knowledge of Azure resource hierarchy (management groups, subscriptions, resource groups), Azure RBAC, Azure Policy, and tagging standards.
- Hands-on experience with Azure PaaS and workload services: App Service, AKS, Container Apps, Azure Functions, Azure SQL, Cosmos DB, Storage, and Key Vault.
- Experience with secure connectivity patterns - private endpoints, VNet integration, DNS, firewall dependencies, and PaaS workload validation.
- Experience supporting deployment security - service connections, managed identities, service principals, Key Vault integration, branch policies, and least-privilege access.
- Hands-on experience with monitoring and observability platforms including Azure Monitor, Log Analytics, Application Insights, Prometheus, Grafana, Site24x7, or equivalent enterprise monitoring solutions.
- Experience configuring alerts, dashboards, and service health monitoring for cloud infrastructure, applications, CI/CD pipelines, and platform services to support proactive operations.
- Proven incident response and production support experience, including triage, root cause analysis, service restoration, and post-incident documentation in business-critical environments.
- Ability to troubleshoot complex infrastructure and deployment issues across Azure resources, networking, identity services, container platforms, and CI/CD pipelines.
- Clear written communication and the ability to work across application, platform, security, networking, vendor, and operations teams.
Preferred Qualifications (list):
- Experience supporting Azure DevOps platform capabilities - agent pools, variable groups, environments, approvals, artifacts, package feeds, release gates, and pipeline library management.
- Familiarity with GitHub Advanced Security or similar DevSecOps tooling for SAST, dependency scanning, secret scanning, and pull request enforcement.
- Familiarity with Azure Landing Zone / Calandra-style environment patterns (landing-zone accelerators, policy-as-code, subscription vending, and workload governance).
- Azure certifications: AZ-104 (Azure Administrator), AZ-204 (Azure Developer), AZ-400 (DevOps Engineer), or equivalent experience.
- Experience with cloud cost management (Azure Cost Management, FinOps practices) in a multi-subscription environment.
Success in the First 90 Days: This is like expectations; could be considered part of Responsibilities or maybe a separate section? The instruction says include sections only when posting has real, specific content. This is specific content; we could treat as a section maybe "First 90 Days Goals" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could incorporate the First 90 Days content under Responsibilities or maybe under Requirements? It's more like objectives. Could put under Responsibilities as additional bullet points? But they are not responsibilities but early goals. However we must preserve all substantive info; we could add a
under Responsibilities summarizing? But we should not invent headings not allowed. So we can incorporate as a paragraph under Responsibilities (maybe after the list). Or we could create a separate section "Requirements" but that's already used. Better to add as a
under Responsibilities after the list, describing early success expectations.
Benefits list: after "#iph". Let's extract:
- Comprehensive full medical, dental and vision Insurance
- Basic Life Insurance at no cost to the employee
- Company paid short-term and long-term disability
- 12 weeks of 100% paid Parental Leave
- Health Savings Account (HSA)
- Flexible Spending Accounts (FSA)
- Retirement savings plan
- Personal Paid Time Off
- Paid holidays and company-wide Wellness Day off
- Paid time off to volunteer at nonprofit organizations
- Pet friendly office environment
- Commuter Benefits
- Group Pet Insurance
- On the job training and skills development
- Employee Assistance Program (EAP)
We should preserve all.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll structure:
About the role
Company description...
Role summary...
Responsibilities
- ...
...
Success in the First 90 Days: ...
(maybe as a paragraph after list)
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
We must not include Pay or Schedule.
Check for any duplicated lines: ensure we didn't repeat.
Now ensure we preserve all details exactly as in posting. Need to copy text verbatim? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the wording as close as possible. Slight modifications for readability? Probably okay to keep same phrasing.
Let's craft.
Company description paragraph: exactly as given.
Role summary paragraph: exactly as given.
Now responsibilities bullets: need to keep the dash and details.
Let's copy each bullet exactly as in posting:
- Provision Clarus workload-specific Azure resources - compute (VMs, AKS), storage, PaaS services (Container Apps, App Services, Azure Functions, Azure SQL, Cosmos DB), Key Vault, and managed identities per architecture-approved patterns.
- Author and maintain Terraform IaC modules -
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove Interview Technology Notice and Text Messaging Notice? Those are likely boilerplate; they are not part of job description content. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Interview Technology Notice and Text Messaging Notice are likely part of application instructions, so remove them. We need to include sections only when posting has real, specific content. The posting includes: - Intro about company (Established in 2021...). That could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: maybe the Role Summary paragraph. - Responsibilities: Key Responsibilities bullet list. - Requirements: maybe Required Qualifications. - Qualifications: maybe Preferred Qualifications? But they said use both Requirements and Qualifications sections. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications (or Skills). But we also have Skills maybe from required qualifications? Could combine. We need to avoid filler sections like Pay or Schedule if not present. The posting does not mention pay or schedule. So we should not include Pay or Schedule sections. Benefits: there is a benefits list after "#iph". So we should include Benefits section. Thus sections: About the role (Role Summary), Responsibilities (Key Responsibilities), Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Benefits (benefits list). Possibly Skills? Could embed skills within qualifications. But we could also create a Skills section if there is explicit skills list. The posting includes many skill-like items in qualifications. Might be okay to not create separate Skills. We must use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, required qualifications, preferred qualifications, benefits.
We need to ensure we don't include boilerplate like "Established in 2021, Independence Pet Holdings is a corporate holding company..." That's substantive about company; we can include in About the role? Actually About the role should be role summary. The company description could be part of About the role or maybe we could include a brief About the company paragraph. The instruction says use headings like About the role, Responsibilities, etc. It didn't forbid adding an About the company paragraph under About the role? Might be okay to include company description as part of About the role (since it's about the role's context). But we need to preserve all substantive info; we can include it in a
under About the role.
Let's extract sections:
Company description: "Established in 2021, Independence Pet Holdings is a corporate holding company that manages a diverse and broad portfolio of modern pet health brands and services, including insurance, pet education, lost recovery services, and more throughout North America. We believe pet insurance is more than a financial product and build solutions to simplify the pet parenting journey and help improve the well-being of pets. As a leading authority in the pet category, we operate with a full stack of resources, capital, and services to support pet parents. Our multi-brand and omni-channel approach include our own insurance carrier, insurance brands and partner brands."
Role Summary: "This role provisions, manages, and supports cloud infrastructure and DevOps capabilities for Clarus DevOps workloads. The Cloud Engineer translates architecture decisions and platform requirements into production-ready Terraform modules and reliable CI/CD pipelines covering compute, storage, PaaS services, environment scaffolding, and deployment automation. The role partners closely with application teams, DevOps leads, networking, security, and operations to deliver governed, reproducible, supportable, and cost-aware infrastructure aligned to Calandra Blueprint and Azure Landing Zone standards."
We could combine company description and role summary under About the role.
Responsibilities: list bullet points under Key Responsibilities.
Let's extract each bullet:
- Provision Clarus workload-specific Azure resources - compute (VMs, AKS), storage, PaaS services (Container Apps, App Services, Azure Functions, Azure SQL, Cosmos DB), Key Vault, and managed identities per architecture-approved patterns.
- Author and maintain Terraform IaC modules - resource provisioning, testing, peer review, versioning, and CI validation for reusable workload and platform components.
- Build, maintain, and support CI/CD pipelines - Azure DevOps YAML pipelines, reusable templates, build and release stages, approvals, quality gates, and environment-specific deployment flows.
- Troubleshoot pipeline and deployment issues - failed builds, blocked releases, service connection problems, agent pool issues, package or artifact failures, container image deployments, and rollback scenarios.
- Manage secure deployment integrations - Azure service connections, federated credentials, managed-identity authentication, Key Vault-backed secrets, artifact feeds, container registries, and least-privilege access patterns.
- Scaffold and manage workload landing-zone structures - subscriptions, resource groups, RBAC assignments, tagging, Azure Policy, and dev / stg / prd environment alignment within the Calandra Azure Landing Zone.
- Integrate workload resources with shared network services - private endpoints, VNet integration, DNS registration, firewall rule requests, and connectivity validation for Clarus environments.
- Maintain environment parity and operational readiness - governance guardrails, policy compliance, cost tagging, quota management, secure defaults, runbooks, and release support procedures.
- Support DevSecOps controls - pipeline security checks, SAST integration, dependency scanning, infrastructure validation, branch policies, pull request checks, and audit-friendly deployment evidence.
- Monitor resource health, cost, and compliance - contribute to observability dashboards, alerting baselines, incident troubleshooting, and cost optimization recommendations.
That's all.
Required Qualifications (list):
- 3-5 years in Cloud Engineering or DevOps engineering, with hands-on Azure infrastructure provisioning and operational support experience.
- Proven Terraform skills - authoring, testing, reviewing, and maintaining modules in a team environment with CI validation.
- Strong CI/CD pipeline experience - Azure DevOps, YAML pipeline authoring, reusable templates, approvals, quality gates, and release troubleshooting.
- Working knowledge of Azure resource hierarchy (management groups, subscriptions, resource groups), Azure RBAC, Azure Policy, and tagging standards.
- Hands-on experience with Azure PaaS and workload services: App Service, AKS, Container Apps, Azure Functions, Azure SQL, Cosmos DB, Storage, and Key Vault.
- Experience with secure connectivity patterns - private endpoints, VNet integration, DNS, firewall dependencies, and PaaS workload validation.
- Experience supporting deployment security - service connections, managed identities, service principals, Key Vault integration, branch policies, and least-privilege access.
- Hands-on experience with monitoring and observability platforms including Azure Monitor, Log Analytics, Application Insights, Prometheus, Grafana, Site24x7, or equivalent enterprise monitoring solutions.
- Experience configuring alerts, dashboards, and service health monitoring for cloud infrastructure, applications, CI/CD pipelines, and platform services to support proactive operations.
- Proven incident response and production support experience, including triage, root cause analysis, service restoration, and post-incident documentation in business-critical environments.
- Ability to troubleshoot complex infrastructure and deployment issues across Azure resources, networking, identity services, container platforms, and CI/CD pipelines.
- Clear written communication and the ability to work across application, platform, security, networking, vendor, and operations teams.
Preferred Qualifications (list):
- Experience supporting Azure DevOps platform capabilities - agent pools, variable groups, environments, approvals, artifacts, package feeds, release gates, and pipeline library management.
- Familiarity with GitHub Advanced Security or similar DevSecOps tooling for SAST, dependency scanning, secret scanning, and pull request enforcement.
- Familiarity with Azure Landing Zone / Calandra-style environment patterns (landing-zone accelerators, policy-as-code, subscription vending, and workload governance).
- Azure certifications: AZ-104 (Azure Administrator), AZ-204 (Azure Developer), AZ-400 (DevOps Engineer), or equivalent experience.
- Experience with cloud cost management (Azure Cost Management, FinOps practices) in a multi-subscription environment.
Success in the First 90 Days: This is like expectations; could be considered part of Responsibilities or maybe a separate section? The instruction says include sections only when posting has real, specific content. This is specific content; we could treat as a section maybe "First 90 Days Goals" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could incorporate the First 90 Days content under Responsibilities or maybe under Requirements? It's more like objectives. Could put under Responsibilities as additional bullet points? But they are not responsibilities but early goals. However we must preserve all substantive info; we could add a
under Responsibilities summarizing? But we should not invent headings not allowed. So we can incorporate as a paragraph under Responsibilities (maybe after the list). Or we could create a separate section "Requirements" but that's already used. Better to add as a
under Responsibilities after the list, describing early success expectations.
Benefits list: after "#iph". Let's extract:
- Comprehensive full medical, dental and vision Insurance
- Basic Life Insurance at no cost to the employee
- Company paid short-term and long-term disability
- 12 weeks of 100% paid Parental Leave
- Health Savings Account (HSA)
- Flexible Spending Accounts (FSA)
- Retirement savings plan
- Personal Paid Time Off
- Paid holidays and company-wide Wellness Day off
- Paid time off to volunteer at nonprofit organizations
- Pet friendly office environment
- Commuter Benefits
- Group Pet Insurance
- On the job training and skills development
- Employee Assistance Program (EAP)
We should preserve all.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll structure:
About the role
Company description...
Role summary...
Responsibilities
- ...
...
Success in the First 90 Days: ...
(maybe as a paragraph after list)
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
We must not include Pay or Schedule.
Check for any duplicated lines: ensure we didn't repeat.
Now ensure we preserve all details exactly as in posting. Need to copy text verbatim? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the wording as close as possible. Slight modifications for readability? Probably okay to keep same phrasing.
Let's craft.
Company description paragraph: exactly as given.
Role summary paragraph: exactly as given.
Now responsibilities bullets: need to keep the dash and details.
Let's copy each bullet exactly as in posting:
- Provision Clarus workload-specific Azure resources - compute (VMs, AKS), storage, PaaS services (Container Apps, App Services, Azure Functions, Azure SQL, Cosmos DB), Key Vault, and managed identities per architecture-approved patterns.
- Author and maintain Terraform IaC modules -
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, required qualifications, preferred qualifications, benefits. We need to ensure we don't include boilerplate like "Established in 2021, Independence Pet Holdings is a corporate holding company..." That's substantive about company; we can include in About the role? Actually About the role should be role summary. The company description could be part of About the role or maybe we could include a brief About the company paragraph. The instruction says use headings like About the role, Responsibilities, etc. It didn't forbid adding an About the company paragraph under About the role? Might be okay to include company description as part of About the role (since it's about the role's context). But we need to preserve all substantive info; we can include it in a
under About the role. Let's extract sections: Company description: "Established in 2021, Independence Pet Holdings is a corporate holding company that manages a diverse and broad portfolio of modern pet health brands and services, including insurance, pet education, lost recovery services, and more throughout North America. We believe pet insurance is more than a financial product and build solutions to simplify the pet parenting journey and help improve the well-being of pets. As a leading authority in the pet category, we operate with a full stack of resources, capital, and services to support pet parents. Our multi-brand and omni-channel approach include our own insurance carrier, insurance brands and partner brands." Role Summary: "This role provisions, manages, and supports cloud infrastructure and DevOps capabilities for Clarus DevOps workloads. The Cloud Engineer translates architecture decisions and platform requirements into production-ready Terraform modules and reliable CI/CD pipelines covering compute, storage, PaaS services, environment scaffolding, and deployment automation. The role partners closely with application teams, DevOps leads, networking, security, and operations to deliver governed, reproducible, supportable, and cost-aware infrastructure aligned to Calandra Blueprint and Azure Landing Zone standards." We could combine company description and role summary under About the role. Responsibilities: list bullet points under Key Responsibilities. Let's extract each bullet: - Provision Clarus workload-specific Azure resources - compute (VMs, AKS), storage, PaaS services (Container Apps, App Services, Azure Functions, Azure SQL, Cosmos DB), Key Vault, and managed identities per architecture-approved patterns. - Author and maintain Terraform IaC modules - resource provisioning, testing, peer review, versioning, and CI validation for reusable workload and platform components. - Build, maintain, and support CI/CD pipelines - Azure DevOps YAML pipelines, reusable templates, build and release stages, approvals, quality gates, and environment-specific deployment flows. - Troubleshoot pipeline and deployment issues - failed builds, blocked releases, service connection problems, agent pool issues, package or artifact failures, container image deployments, and rollback scenarios. - Manage secure deployment integrations - Azure service connections, federated credentials, managed-identity authentication, Key Vault-backed secrets, artifact feeds, container registries, and least-privilege access patterns. - Scaffold and manage workload landing-zone structures - subscriptions, resource groups, RBAC assignments, tagging, Azure Policy, and dev / stg / prd environment alignment within the Calandra Azure Landing Zone. - Integrate workload resources with shared network services - private endpoints, VNet integration, DNS registration, firewall rule requests, and connectivity validation for Clarus environments. - Maintain environment parity and operational readiness - governance guardrails, policy compliance, cost tagging, quota management, secure defaults, runbooks, and release support procedures. - Support DevSecOps controls - pipeline security checks, SAST integration, dependency scanning, infrastructure validation, branch policies, pull request checks, and audit-friendly deployment evidence. - Monitor resource health, cost, and compliance - contribute to observability dashboards, alerting baselines, incident troubleshooting, and cost optimization recommendations. That's all. Required Qualifications (list): - 3-5 years in Cloud Engineering or DevOps engineering, with hands-on Azure infrastructure provisioning and operational support experience. - Proven Terraform skills - authoring, testing, reviewing, and maintaining modules in a team environment with CI validation. - Strong CI/CD pipeline experience - Azure DevOps, YAML pipeline authoring, reusable templates, approvals, quality gates, and release troubleshooting. - Working knowledge of Azure resource hierarchy (management groups, subscriptions, resource groups), Azure RBAC, Azure Policy, and tagging standards. - Hands-on experience with Azure PaaS and workload services: App Service, AKS, Container Apps, Azure Functions, Azure SQL, Cosmos DB, Storage, and Key Vault. - Experience with secure connectivity patterns - private endpoints, VNet integration, DNS, firewall dependencies, and PaaS workload validation. - Experience supporting deployment security - service connections, managed identities, service principals, Key Vault integration, branch policies, and least-privilege access. - Hands-on experience with monitoring and observability platforms including Azure Monitor, Log Analytics, Application Insights, Prometheus, Grafana, Site24x7, or equivalent enterprise monitoring solutions. - Experience configuring alerts, dashboards, and service health monitoring for cloud infrastructure, applications, CI/CD pipelines, and platform services to support proactive operations. - Proven incident response and production support experience, including triage, root cause analysis, service restoration, and post-incident documentation in business-critical environments. - Ability to troubleshoot complex infrastructure and deployment issues across Azure resources, networking, identity services, container platforms, and CI/CD pipelines. - Clear written communication and the ability to work across application, platform, security, networking, vendor, and operations teams. Preferred Qualifications (list): - Experience supporting Azure DevOps platform capabilities - agent pools, variable groups, environments, approvals, artifacts, package feeds, release gates, and pipeline library management. - Familiarity with GitHub Advanced Security or similar DevSecOps tooling for SAST, dependency scanning, secret scanning, and pull request enforcement. - Familiarity with Azure Landing Zone / Calandra-style environment patterns (landing-zone accelerators, policy-as-code, subscription vending, and workload governance). - Azure certifications: AZ-104 (Azure Administrator), AZ-204 (Azure Developer), AZ-400 (DevOps Engineer), or equivalent experience. - Experience with cloud cost management (Azure Cost Management, FinOps practices) in a multi-subscription environment. Success in the First 90 Days: This is like expectations; could be considered part of Responsibilities or maybe a separate section? The instruction says include sections only when posting has real, specific content. This is specific content; we could treat as a section maybe "First 90 Days Goals" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could incorporate the First 90 Days content under Responsibilities or maybe under Requirements? It's more like objectives. Could put under Responsibilities as additional bullet points? But they are not responsibilities but early goals. However we must preserve all substantive info; we could add a
under Responsibilities summarizing? But we should not invent headings not allowed. So we can incorporate as a paragraph under Responsibilities (maybe after the list). Or we could create a separate section "Requirements" but that's already used. Better to add as a
under Responsibilities after the list, describing early success expectations. Benefits list: after "#iph". Let's extract: - Comprehensive full medical, dental and vision Insurance - Basic Life Insurance at no cost to the employee - Company paid short-term and long-term disability - 12 weeks of 100% paid Parental Leave - Health Savings Account (HSA) - Flexible Spending Accounts (FSA) - Retirement savings plan - Personal Paid Time Off - Paid holidays and company-wide Wellness Day off - Paid time off to volunteer at nonprofit organizations - Pet friendly office environment - Commuter Benefits - Group Pet Insurance - On the job training and skills development - Employee Assistance Program (EAP) We should preserve all. Now we need to output HTML fragment only, no /, no markdown fences. We'll structure:
About the role
Company description...
Role summary...
Responsibilities
- ... ...
Success in the First 90 Days: ...
(maybe as a paragraph after list)Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...