Principal, AI Operations & Infrastructure Automation
for section headings. 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. Remove boilerplate like EEO, equal-opportunity, scam-warning, navigation, cookie, legal, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract content.
We have sections: About The Role & Team (the first paragraph). Then "What You’ll Do" which is responsibilities. Then "Responsibilities" bullet list. Then "Additional responsibilities include:" more bullet list. Then "Lead the team and prove the results" more bullet list. Then "Required What You Bring" (requirements). Then "Preferred". Then "What Success Looks Like" (maybe could be considered as expectations but not required section; but we can include under Responsibilities? Probably not needed. The instruction: include a section only when posting has real, specific content for it. We have sections: About the role, Responsibilities, Requirements (maybe Qualifications), Skills (maybe we can combine required and preferred into Requirements and Skills?), Benefits, Pay, Schedule. Pay is present: "Compensation Transparency" with salary range. Schedule? Not mentioned. So we should not create Schedule section. Benefits: there is "What We Offer" list. So Benefits section.
We need to avoid filler like "prorated based on start date" is okay; it's specific. "may vary by state" is okay.
We need to remove EEO, Equal Opportunity Employer, etc. Also remove "LI-ED1 -Remote". Also remove "Compensation Transparency" heading? We'll keep Pay section with the salary range.
We need to format using
headings.
We need to use - for any list of duties/requirements/benefits. So for responsibilities we need list items. For requirements we need list. For skills maybe we can combine required and preferred? The instruction: Use
- for any list of duties/requirements/benefits. So we can have separate sections: Responsibilities (list), Requirements (list), Skills (list), Benefits (list). Pay: we can put as
maybe.
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, preferred, benefits, pay.
We must not create sections with filler/placeholder text. So we must ensure each section has actual content.
Let's extract.
About the role & team: The first paragraph(s) up to "What You’ll Do". Actually the section "About The Role & Team" includes paragraphs: IDC is the premier global provider... Our analysts turn data... That standard applies internally too. The infrastructure our analysts... has to be fast, reliable, and quietly excellent — at a scale manual operations can no longer reach. What You’ll Do IDC is modernizing how infrastructure is run... We're looking for a Principal of AI Operations & Infrastructure Automation to lead this transformation... This is a hands-on, high-velocity leadership role for someone who has actually built AIOps and infrastructure-as-code capability before — not just overseen it.
We should keep that as prose under About the role heading.
Responsibilities: There's a heading "Responsibilities" with bullet: "You'll personally write and review automation, get into the tooling directly, and lead by example for the team you manage. You'll partner closely with the CIO, Cyber & Infrastructure leadership, and AWS as a strategic cloud and co-development partner to re-architect how infrastructure operations get done. This role builds and leads the team responsible for automation — setting technical direction, reviewing their work, and growing their skills as the operating model evolves." Then "Additional responsibilities include:" with a list of bullet points (starting with Own the end-to-end redesign...). Then later "Lead the team and prove the results" with bullet points (Directly manage and develop a team..., Partner with AWS..., Establish new operational KPIs..., Set guardrails..., Ensure automated operations...). All these are responsibilities. So we can combine all bullet points under Responsibilities.
We need to keep them as list items.
Let's list them:
- You'll personally write and review automation, get into the tooling directly, and lead by example for the team you manage.
- You'll partner closely with the CIO, Cyber & Infrastructure leadership, and AWS as a strategic cloud and co-development partner to re-architect how infrastructure operations get done.
- This role builds and leads the team responsible for automation — setting technical direction, reviewing their work, and growing their skills as the operating model evolves.
- Own the end-to-end redesign of the infrastructure operating model, moving core workflows (provisioning, monitoring, incident response, patching, capacity management) from manual execution to automated, self-healing pipelines.
- Define a phased transformation roadmap with clear milestones, automation-coverage targets, and go-live gates — and drive execution against it at pace.
- Lead change management for the infrastructure team through the transition — defining new roles, skills, and ways of working as automation is adopted.
- Build the AIOps layer; evaluate, select, and deploy AIOps platforms and agentic tooling — anomaly detection, predictive alerting, automated remediation — suited to IDC's AWS-centric environment.
- Implement event correlation and noise reduction so a hundred alerts resolve into one actionable incident with a probable root cause attached.
- Stand up LLM (large language model)-assisted triage that classifies, enriches, and routes incidents, pulling relevant runbooks, past resolutions, and change history into the ticket automatically.
- Develop predictive capacity and failure models for critical services, and act on them before thresholds are breached.
- Automate end to end, build and champion an infrastructure-as-code (IaC) standard across the organization, converting legacy manual processes into version-controlled, repeatable automation.
- Deliver self-healing automation and closed-loop remediation for the highest-volume recurring incidents — restart, rollback, scale, reroute, and verify without a human in the loop.
- Automate service request fulfillment: access provisioning, environment setup, onboarding and offboarding, and routine change execution.
- Own CI/CD (continuous integration/continuous delivery-deployment) pipelines for operational tooling, including testing and safe rollback for automations that touch production.
- Directly manage and develop a team of infrastructure and automation engineers — hiring, coaching, and setting technical direction — while staying hands-on in the tooling and code yourself.
- Partner with AWS and other strategic vendors to pilot and scale automation and AI-driven operations capabilities, including Bedrock/AgentCore-based tooling where relevant.
- Establish new operational KPIs — automation coverage, mean time to detect and resolve, deployment frequency, toil eliminated — and report progress in concise, executive-ready formats.
- Set guardrails for AI in operations: human-in-the-loop thresholds, blast-radius limits, audit logging, evaluation of model output quality, and clear rollback paths.
- Ensure automated operations meet IDC's security, compliance, and resiliency standards, working closely with Cyber & Compliance.
That seems comprehensive.
Now Requirements: Under "Required What You Bring". Bullets:
- 8+ years in infrastructure, platform engineering, or IT operations, including 3+ years leading automation or AIOps initiatives.
- Demonstrated track record of redesigning an operations function around automation — not just introducing point tools but changing how a team works.
- Deep hands-on experience with cloud infrastructure automation (AWS strongly preferred), infrastructure-as-code (Terraform, CloudFormation, or similar), and CI/CD pipelines.
- Working knowledge of AIOps and agentic automation platforms, and a clear point of view on where AI genuinely improves operational outcomes versus adds noise.
- Practical automation skill in Python or an equivalent language, including building integrations against REST APIs and operational tooling.
- Hands-on experience with observability and monitoring platforms — Datadog, Splunk, Dynatrace, New Relic, Prometheus/Grafana, Elastic, or similar — including instrumenting services and building useful alerting.
- Strong program leadership skills: able to define a roadmap, sequence dependencies, and hit aggressive milestones.
- Excellent executive communication skills — comfortable distilling complex technical transformation into clear, concise updates for senior leadership.
Now Preferred: Under "Preferred". Bullets:
- Experience operating in a regulated or compliance-sensitive environment (SOC 2, ISO 27001, or similar).
- Prior experience partnering directly with a hyperscaler (AWS, Azure, or GCP) on joint automation or AI initiatives.
- Background in site reliability engineering (SRE) practices and observability tooling.
- Experience with agentic AI frameworks, RAG pipelines, or building internal AI copilots for technical teams.
- Familiarity with ITSM platforms and process — ServiceNow, Jira Service Management, or similar — and comfort automating against them.
- Familiarity with FinOps practices and cloud cost automation.
- Relevant certifications (cloud architect or engineer, Kubernetes, ITIL v4, Terraform).
Now Benefits: Under "What We Offer". Bullets:
- 15 vacation days (prorated based on start date)
- 12 company-paid holidays
- 6 paid sick days (prorated based on start date; may vary by state)
- Medical, dental, and vision coverage
- 2 floating holidays (prorated based on start date)
- 1 volunteer day
- 401(k) company match (IDC matches 3% on the first 6% of employee contributions)
- Company-paid short-term disability
- Company-paid life insurance
- Company-paid parental leave
Now Pay: Under "Compensation Transparency". Paragraph: "At IDC, we are committed to fair and equitable pay practices. Employees are compensated equitably for their work, aligned with their skills and experience. Salary and incentive structures are determined through a rigorous process that considers experience, education, certifications, role-specific requirements, internal equity, and verified U.S. market data from an independent third-party partner. The expected total annual compensation, depending on location and experience, is between $139,000-$240,000, inclusive of base salary and variable compensation. If this role relocates to a different country, the salary range will be updated to reflect that country's range, rather than a currency conversion of the original range."
We need to keep that as prose under Pay heading. Possibly we could also include the note about location adjustment.
Now Schedule: Not present, so omit.
Now we need to avoid boilerplate: Remove Equal Opportunity Employer, etc. Also remove "LI-ED1 -Remote". Also remove any duplicated lines. Also remove navigation/cookie/legal etc. Not present.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... (the about text)
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
...
We need to ensure we don't repeat job title. Good.
Now we need to check that we haven't included any filler like "commensurate with experience". Not present.
Now we need to ensure we didn't include any sections that are empty. All have content.
Now we need to ensure we didn't include any duplicated lines. We'll just output each bullet once.
Now we need to check that we didn't include any application instructions. Not present.
Now we need to ensure we didn't include any EEO etc.
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate like EEO, equal-opportunity, scam-warning, navigation, cookie, legal, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract content. We have sections: About The Role & Team (the first paragraph). Then "What You’ll Do" which is responsibilities. Then "Responsibilities" bullet list. Then "Additional responsibilities include:" more bullet list. Then "Lead the team and prove the results" more bullet list. Then "Required What You Bring" (requirements). Then "Preferred". Then "What Success Looks Like" (maybe could be considered as expectations but not required section; but we can include under Responsibilities? Probably not needed. The instruction: include a section only when posting has real, specific content for it. We have sections: About the role, Responsibilities, Requirements (maybe Qualifications), Skills (maybe we can combine required and preferred into Requirements and Skills?), Benefits, Pay, Schedule. Pay is present: "Compensation Transparency" with salary range. Schedule? Not mentioned. So we should not create Schedule section. Benefits: there is "What We Offer" list. So Benefits section. We need to avoid filler like "prorated based on start date" is okay; it's specific. "may vary by state" is okay. We need to remove EEO, Equal Opportunity Employer, etc. Also remove "LI-ED1 -Remote". Also remove "Compensation Transparency" heading? We'll keep Pay section with the salary range. We need to format using
headings.
We need to use - for any list of duties/requirements/benefits. So for responsibilities we need list items. For requirements we need list. For skills maybe we can combine required and preferred? The instruction: Use
- for any list of duties/requirements/benefits. So we can have separate sections: Responsibilities (list), Requirements (list), Skills (list), Benefits (list). Pay: we can put as
maybe.
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, preferred, benefits, pay.
We must not create sections with filler/placeholder text. So we must ensure each section has actual content.
Let's extract.
About the role & team: The first paragraph(s) up to "What You’ll Do". Actually the section "About The Role & Team" includes paragraphs: IDC is the premier global provider... Our analysts turn data... That standard applies internally too. The infrastructure our analysts... has to be fast, reliable, and quietly excellent — at a scale manual operations can no longer reach. What You’ll Do IDC is modernizing how infrastructure is run... We're looking for a Principal of AI Operations & Infrastructure Automation to lead this transformation... This is a hands-on, high-velocity leadership role for someone who has actually built AIOps and infrastructure-as-code capability before — not just overseen it.
We should keep that as prose under About the role heading.
Responsibilities: There's a heading "Responsibilities" with bullet: "You'll personally write and review automation, get into the tooling directly, and lead by example for the team you manage. You'll partner closely with the CIO, Cyber & Infrastructure leadership, and AWS as a strategic cloud and co-development partner to re-architect how infrastructure operations get done. This role builds and leads the team responsible for automation — setting technical direction, reviewing their work, and growing their skills as the operating model evolves." Then "Additional responsibilities include:" with a list of bullet points (starting with Own the end-to-end redesign...). Then later "Lead the team and prove the results" with bullet points (Directly manage and develop a team..., Partner with AWS..., Establish new operational KPIs..., Set guardrails..., Ensure automated operations...). All these are responsibilities. So we can combine all bullet points under Responsibilities.
We need to keep them as list items.
Let's list them:
- You'll personally write and review automation, get into the tooling directly, and lead by example for the team you manage.
- You'll partner closely with the CIO, Cyber & Infrastructure leadership, and AWS as a strategic cloud and co-development partner to re-architect how infrastructure operations get done.
- This role builds and leads the team responsible for automation — setting technical direction, reviewing their work, and growing their skills as the operating model evolves.
- Own the end-to-end redesign of the infrastructure operating model, moving core workflows (provisioning, monitoring, incident response, patching, capacity management) from manual execution to automated, self-healing pipelines.
- Define a phased transformation roadmap with clear milestones, automation-coverage targets, and go-live gates — and drive execution against it at pace.
- Lead change management for the infrastructure team through the transition — defining new roles, skills, and ways of working as automation is adopted.
- Build the AIOps layer; evaluate, select, and deploy AIOps platforms and agentic tooling — anomaly detection, predictive alerting, automated remediation — suited to IDC's AWS-centric environment.
- Implement event correlation and noise reduction so a hundred alerts resolve into one actionable incident with a probable root cause attached.
- Stand up LLM (large language model)-assisted triage that classifies, enriches, and routes incidents, pulling relevant runbooks, past resolutions, and change history into the ticket automatically.
- Develop predictive capacity and failure models for critical services, and act on them before thresholds are breached.
- Automate end to end, build and champion an infrastructure-as-code (IaC) standard across the organization, converting legacy manual processes into version-controlled, repeatable automation.
- Deliver self-healing automation and closed-loop remediation for the highest-volume recurring incidents — restart, rollback, scale, reroute, and verify without a human in the loop.
- Automate service request fulfillment: access provisioning, environment setup, onboarding and offboarding, and routine change execution.
- Own CI/CD (continuous integration/continuous delivery-deployment) pipelines for operational tooling, including testing and safe rollback for automations that touch production.
- Directly manage and develop a team of infrastructure and automation engineers — hiring, coaching, and setting technical direction — while staying hands-on in the tooling and code yourself.
- Partner with AWS and other strategic vendors to pilot and scale automation and AI-driven operations capabilities, including Bedrock/AgentCore-based tooling where relevant.
- Establish new operational KPIs — automation coverage, mean time to detect and resolve, deployment frequency, toil eliminated — and report progress in concise, executive-ready formats.
- Set guardrails for AI in operations: human-in-the-loop thresholds, blast-radius limits, audit logging, evaluation of model output quality, and clear rollback paths.
- Ensure automated operations meet IDC's security, compliance, and resiliency standards, working closely with Cyber & Compliance.
That seems comprehensive.
Now Requirements: Under "Required What You Bring". Bullets:
- 8+ years in infrastructure, platform engineering, or IT operations, including 3+ years leading automation or AIOps initiatives.
- Demonstrated track record of redesigning an operations function around automation — not just introducing point tools but changing how a team works.
- Deep hands-on experience with cloud infrastructure automation (AWS strongly preferred), infrastructure-as-code (Terraform, CloudFormation, or similar), and CI/CD pipelines.
- Working knowledge of AIOps and agentic automation platforms, and a clear point of view on where AI genuinely improves operational outcomes versus adds noise.
- Practical automation skill in Python or an equivalent language, including building integrations against REST APIs and operational tooling.
- Hands-on experience with observability and monitoring platforms — Datadog, Splunk, Dynatrace, New Relic, Prometheus/Grafana, Elastic, or similar — including instrumenting services and building useful alerting.
- Strong program leadership skills: able to define a roadmap, sequence dependencies, and hit aggressive milestones.
- Excellent executive communication skills — comfortable distilling complex technical transformation into clear, concise updates for senior leadership.
Now Preferred: Under "Preferred". Bullets:
- Experience operating in a regulated or compliance-sensitive environment (SOC 2, ISO 27001, or similar).
- Prior experience partnering directly with a hyperscaler (AWS, Azure, or GCP) on joint automation or AI initiatives.
- Background in site reliability engineering (SRE) practices and observability tooling.
- Experience with agentic AI frameworks, RAG pipelines, or building internal AI copilots for technical teams.
- Familiarity with ITSM platforms and process — ServiceNow, Jira Service Management, or similar — and comfort automating against them.
- Familiarity with FinOps practices and cloud cost automation.
- Relevant certifications (cloud architect or engineer, Kubernetes, ITIL v4, Terraform).
Now Benefits: Under "What We Offer". Bullets:
- 15 vacation days (prorated based on start date)
- 12 company-paid holidays
- 6 paid sick days (prorated based on start date; may vary by state)
- Medical, dental, and vision coverage
- 2 floating holidays (prorated based on start date)
- 1 volunteer day
- 401(k) company match (IDC matches 3% on the first 6% of employee contributions)
- Company-paid short-term disability
- Company-paid life insurance
- Company-paid parental leave
Now Pay: Under "Compensation Transparency". Paragraph: "At IDC, we are committed to fair and equitable pay practices. Employees are compensated equitably for their work, aligned with their skills and experience. Salary and incentive structures are determined through a rigorous process that considers experience, education, certifications, role-specific requirements, internal equity, and verified U.S. market data from an independent third-party partner. The expected total annual compensation, depending on location and experience, is between $139,000-$240,000, inclusive of base salary and variable compensation. If this role relocates to a different country, the salary range will be updated to reflect that country's range, rather than a currency conversion of the original range."
We need to keep that as prose under Pay heading. Possibly we could also include the note about location adjustment.
Now Schedule: Not present, so omit.
Now we need to avoid boilerplate: Remove Equal Opportunity Employer, etc. Also remove "LI-ED1 -Remote". Also remove any duplicated lines. Also remove navigation/cookie/legal etc. Not present.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... (the about text)
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
...
We need to ensure we don't repeat job title. Good.
Now we need to check that we haven't included any filler like "commensurate with experience". Not present.
Now we need to ensure we didn't include any sections that are empty. All have content.
Now we need to ensure we didn't include any duplicated lines. We'll just output each bullet once.
Now we need to check that we didn't include any application instructions. Not present.
Now we need to ensure we didn't include any EEO etc.
- for any list of duties/requirements/benefits. So we can have separate sections: Responsibilities (list), Requirements (list), Skills (list), Benefits (list). Pay: we can put as
maybe. 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, preferred, benefits, pay. We must not create sections with filler/placeholder text. So we must ensure each section has actual content. Let's extract. About the role & team: The first paragraph(s) up to "What You’ll Do". Actually the section "About The Role & Team" includes paragraphs: IDC is the premier global provider... Our analysts turn data... That standard applies internally too. The infrastructure our analysts... has to be fast, reliable, and quietly excellent — at a scale manual operations can no longer reach. What You’ll Do IDC is modernizing how infrastructure is run... We're looking for a Principal of AI Operations & Infrastructure Automation to lead this transformation... This is a hands-on, high-velocity leadership role for someone who has actually built AIOps and infrastructure-as-code capability before — not just overseen it. We should keep that as prose under About the role heading. Responsibilities: There's a heading "Responsibilities" with bullet: "You'll personally write and review automation, get into the tooling directly, and lead by example for the team you manage. You'll partner closely with the CIO, Cyber & Infrastructure leadership, and AWS as a strategic cloud and co-development partner to re-architect how infrastructure operations get done. This role builds and leads the team responsible for automation — setting technical direction, reviewing their work, and growing their skills as the operating model evolves." Then "Additional responsibilities include:" with a list of bullet points (starting with Own the end-to-end redesign...). Then later "Lead the team and prove the results" with bullet points (Directly manage and develop a team..., Partner with AWS..., Establish new operational KPIs..., Set guardrails..., Ensure automated operations...). All these are responsibilities. So we can combine all bullet points under Responsibilities. We need to keep them as list items. Let's list them: - You'll personally write and review automation, get into the tooling directly, and lead by example for the team you manage. - You'll partner closely with the CIO, Cyber & Infrastructure leadership, and AWS as a strategic cloud and co-development partner to re-architect how infrastructure operations get done. - This role builds and leads the team responsible for automation — setting technical direction, reviewing their work, and growing their skills as the operating model evolves. - Own the end-to-end redesign of the infrastructure operating model, moving core workflows (provisioning, monitoring, incident response, patching, capacity management) from manual execution to automated, self-healing pipelines. - Define a phased transformation roadmap with clear milestones, automation-coverage targets, and go-live gates — and drive execution against it at pace. - Lead change management for the infrastructure team through the transition — defining new roles, skills, and ways of working as automation is adopted. - Build the AIOps layer; evaluate, select, and deploy AIOps platforms and agentic tooling — anomaly detection, predictive alerting, automated remediation — suited to IDC's AWS-centric environment. - Implement event correlation and noise reduction so a hundred alerts resolve into one actionable incident with a probable root cause attached. - Stand up LLM (large language model)-assisted triage that classifies, enriches, and routes incidents, pulling relevant runbooks, past resolutions, and change history into the ticket automatically. - Develop predictive capacity and failure models for critical services, and act on them before thresholds are breached. - Automate end to end, build and champion an infrastructure-as-code (IaC) standard across the organization, converting legacy manual processes into version-controlled, repeatable automation. - Deliver self-healing automation and closed-loop remediation for the highest-volume recurring incidents — restart, rollback, scale, reroute, and verify without a human in the loop. - Automate service request fulfillment: access provisioning, environment setup, onboarding and offboarding, and routine change execution. - Own CI/CD (continuous integration/continuous delivery-deployment) pipelines for operational tooling, including testing and safe rollback for automations that touch production. - Directly manage and develop a team of infrastructure and automation engineers — hiring, coaching, and setting technical direction — while staying hands-on in the tooling and code yourself. - Partner with AWS and other strategic vendors to pilot and scale automation and AI-driven operations capabilities, including Bedrock/AgentCore-based tooling where relevant. - Establish new operational KPIs — automation coverage, mean time to detect and resolve, deployment frequency, toil eliminated — and report progress in concise, executive-ready formats. - Set guardrails for AI in operations: human-in-the-loop thresholds, blast-radius limits, audit logging, evaluation of model output quality, and clear rollback paths. - Ensure automated operations meet IDC's security, compliance, and resiliency standards, working closely with Cyber & Compliance. That seems comprehensive. Now Requirements: Under "Required What You Bring". Bullets: - 8+ years in infrastructure, platform engineering, or IT operations, including 3+ years leading automation or AIOps initiatives. - Demonstrated track record of redesigning an operations function around automation — not just introducing point tools but changing how a team works. - Deep hands-on experience with cloud infrastructure automation (AWS strongly preferred), infrastructure-as-code (Terraform, CloudFormation, or similar), and CI/CD pipelines. - Working knowledge of AIOps and agentic automation platforms, and a clear point of view on where AI genuinely improves operational outcomes versus adds noise. - Practical automation skill in Python or an equivalent language, including building integrations against REST APIs and operational tooling. - Hands-on experience with observability and monitoring platforms — Datadog, Splunk, Dynatrace, New Relic, Prometheus/Grafana, Elastic, or similar — including instrumenting services and building useful alerting. - Strong program leadership skills: able to define a roadmap, sequence dependencies, and hit aggressive milestones. - Excellent executive communication skills — comfortable distilling complex technical transformation into clear, concise updates for senior leadership. Now Preferred: Under "Preferred". Bullets: - Experience operating in a regulated or compliance-sensitive environment (SOC 2, ISO 27001, or similar). - Prior experience partnering directly with a hyperscaler (AWS, Azure, or GCP) on joint automation or AI initiatives. - Background in site reliability engineering (SRE) practices and observability tooling. - Experience with agentic AI frameworks, RAG pipelines, or building internal AI copilots for technical teams. - Familiarity with ITSM platforms and process — ServiceNow, Jira Service Management, or similar — and comfort automating against them. - Familiarity with FinOps practices and cloud cost automation. - Relevant certifications (cloud architect or engineer, Kubernetes, ITIL v4, Terraform). Now Benefits: Under "What We Offer". Bullets: - 15 vacation days (prorated based on start date) - 12 company-paid holidays - 6 paid sick days (prorated based on start date; may vary by state) - Medical, dental, and vision coverage - 2 floating holidays (prorated based on start date) - 1 volunteer day - 401(k) company match (IDC matches 3% on the first 6% of employee contributions) - Company-paid short-term disability - Company-paid life insurance - Company-paid parental leave Now Pay: Under "Compensation Transparency". Paragraph: "At IDC, we are committed to fair and equitable pay practices. Employees are compensated equitably for their work, aligned with their skills and experience. Salary and incentive structures are determined through a rigorous process that considers experience, education, certifications, role-specific requirements, internal equity, and verified U.S. market data from an independent third-party partner. The expected total annual compensation, depending on location and experience, is between $139,000-$240,000, inclusive of base salary and variable compensation. If this role relocates to a different country, the salary range will be updated to reflect that country's range, rather than a currency conversion of the original range." We need to keep that as prose under Pay heading. Possibly we could also include the note about location adjustment. Now Schedule: Not present, so omit. Now we need to avoid boilerplate: Remove Equal Opportunity Employer, etc. Also remove "LI-ED1 -Remote". Also remove any duplicated lines. Also remove navigation/cookie/legal etc. Not present. Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:
About the role
... (the about text)
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
...
We need to ensure we don't repeat job title. Good. Now we need to check that we haven't included any filler like "commensurate with experience". Not present. Now we need to ensure we didn't include any sections that are empty. All have content. Now we need to ensure we didn't include any duplicated lines. We'll just output each bullet once. Now we need to check that we didn't include any application instructions. Not present. Now we need to ensure we didn't include any EEO etc.