Senior DevOps Engineer
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. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. 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. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
Thus we need to decide which sections to include. We have content for About the role (intro paragraph). Responsibilities (list of duties). Requirements (list). Preferred Qualifications (list). Skills maybe not separate; could combine with Requirements? But they said we can have Skills section if there is specific content. The posting includes many skill-like items in Requirements; we could treat Requirements as skills. But we can still have Skills section if we want to separate? Probably better to have Requirements and Qualifications (Preferred). Skills maybe not needed. But we can include Skills if we want to list specific technical skills (AWS, Terraform, Kubernetes, GitHub Actions, Docker, Prometheus, Grafana, Sentry, etc). However those are already in Requirements. To avoid duplication, we could keep Requirements as list of experience years, and Skills as list of technologies. But the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one Requirements section. But they gave example headings including Skills. We can decide to include Skills if we have distinct content. Let's see: The posting includes "Experience with Docker and containerized application environments", "Experience with monitoring and logging tools such as Prometheus, Grafana, Sentry, or the ELK stack", "Experience with incident response, on-call rotations, and follow-the-sun support models", "Strong communication skills". Those could be considered skills. Meanwhile Requirements list includes years of experience with AWS, Kubernetes, Terraform, GitHub Actions, etc. So we could separate: Requirements = years of experience; Skills = specific technologies and soft skills. That seems reasonable.
Qualifications = Preferred Qualifications list.
Benefits = list.
Pay = compensation.
Schedule = contract length, hybrid, days onsite.
About the role = introductory paragraph(s) describing role.
We must not include boilerplate like EEO, diversity statement, visa sponsorship, etc. Remove those lines.
We must preserve all substantive information. So we need to include all details from the posting except boilerplate.
Let's extract substantive content:
- Expected compensation: 90.00 - 95.00 USD Per Hour
- HireArt is helping our client find a Senior DevOps Engineer to provide follow-the-sun coverage for the ADAS line of business, ensuring platform stability, SLA compliance, and rapid incident response during West Coast business hours.
- In this role, you’ll deliver critical coverage during Japan's off-hours, enabling 24/7 SLA adherence for ADAS production systems running on a multi-tenant ecosystem.
- You’ll partner closely with Japan-based DevOps teams, ADAS engineering (19+ engineers, scaling), and platform teams to maintain uptime, reliability, and operational excellence across multiple production environments.
- The ideal candidate is an experienced DevOps/SRE professional who thrives in high-availability environments, is comfortable owning incidents end-to-end, and brings a strong automation-first mindset.
- As a Senior DevOps Engineer, You'll Provide SEV-1/SEV-2 incident coverage during PST/PDT hours, ensuring 24/7 SLA adherence and meeting the 2-hour initial response target.
- Deploy, manage, and scale AWS infrastructure (S3, Aurora/Postgres, IAM, Route 53, WAF, CloudFront) using Terraform and infrastructure-as-code best practices.
- Build, maintain, and optimize CI/CD pipelines (GitHub Actions) to support consistent, reliable deployments across multiple environments (dev, stage, pre-production, production).
- Monitor and support AWS and Kubernetes-based workloads (Stargate platform) to meet a 99.5% uptime target.
- Track application and infrastructure performance using tools such as Prometheus, Grafana, Sentry, and related observability platforms.
- Respond to incidents, perform root cause analysis, and implement corrective actions to improve system reliability.
- Identify manual processes and implement automation to improve efficiency, reduce deployment times, and minimize operational overhead.
- Integrate security best practices into CI/CD pipelines and infrastructure, ensuring compliance with DevSecOps and IaC standards.
- Develop and maintain runbooks, documentation, and best practices to support knowledge sharing and seamless operations across global teams.
- Requirements:
- High school diploma or GED
- 5+ years of recent, hands-on professional experience in DevOps, Site Reliability Engineering (SRE), or a related role
- 5+ years of recent, hands-on experience with AWS
- 5+ years of recent, hands-on experience deploying, scaling, and managing Kubernetes environments
- 5+ years of recent, hands-on experience using Terraform for infrastructure-as-code
- 5+ years of recent, hands-on experience building and maintaining CI/CD pipelines using GitHub Actions
- Experience with Docker and containerized application environments
- Experience with monitoring and logging tools such as Prometheus, Grafana, Sentry, or the ELK stack
- Experience with incident response, on-call rotations, and follow-the-sun support models
- Strong communication skills with the ability to collaborate effectively across global teams and JP/NA time zones
- Preferred Qualifications:
- Experience with service mesh technologies (e.g., Istio)
- Understanding of DevSecOps practices, including secure deployments, vulnerability scanning, and incident response
- Familiarity with SDLC and agile methodologies (Scrum, Kanban)
- Experience working in multi-tenant or enterprise-scale platforms
- Experience with backup/restore automation and disaster recovery processes
- Familiarity with Nx monorepo tooling and multi-tenant architectures
- Benefits:
- PTO and paid holidays!
- Pre-tax commuter benefits
- Employer (HireArt) Subsidized healthcare benefits
- Flexible Spending Account for healthcare-related costs
- HireArt covers all costs for short and long term disability and life insurance
- 401k package
- Commitment: This is a full-time, 3-month contract position (with the possibility of extension) staffed via HireArt. This role is hybrid, requiring three days per week onsite in the Ann Arbor office.
- HireArt values diversity and is an Equal Opportunity Employer. We are interested in every qualified candidate who is eligible to work in the United States. Unfortunately, we are not able to sponsor visas or employ corp-to-corp. (This is boilerplate EEO/visa; remove.)
We must not include the EEO statement, visa sponsorship, etc.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
Expected compensation: 90.00 - 95.00 USD Per Hour
Schedule
This is a full-time, 3-month contract position (with the possibility of extension) staffed via HireArt. This role is hybrid, requiring three days per week onsite in the Ann Arbor office.
We need to ensure we don't duplicate content. Let's list responsibilities from the bullet points after "As a Senior DevOps Engineer, You'll Provide SEV-1/SEV-2 incident coverage..." and the subsequent bullet-like sentences. Actually the posting uses sentences not bullet list. We'll convert each to - .
Responsibilities list:
- Provide SEV-1/SEV-2 incident coverage during PST/PDT hours, ensuring 24/7 SLA adherence and meeting the 2-hour initial response target.
- Deploy, manage, and scale AWS infrastructure (S3, Aurora/Postgres, IAM, Route 53, WAF, CloudFront) using Terraform and infrastructure-as-code best practices.
- Build, maintain, and optimize CI/CD pipelines (GitHub Actions) to support consistent, reliable deployments across multiple environments (dev, stage, pre-production, production).
- Monitor and support AWS and Kubernetes-based workloads (Stargate platform) to meet a 99.5% uptime target.
- Track application and infrastructure performance using tools such as Prometheus, Grafana, Sentry, and related observability platforms.
- Respond to incidents, perform root cause analysis, and implement corrective actions to improve system reliability.
- Identify manual processes and implement automation to improve efficiency, reduce deployment times, and minimize operational overhead.
- Integrate security best practices into CI/CD pipelines and infrastructure, ensuring compliance with DevSecOps and IaC standards.
- Develop and maintain runbooks, documentation, and best practices to support knowledge sharing and seamless operations across global teams.
Also earlier sentences about delivering coverage during Japan's off-hours, partnering with Japan-based teams, etc. Could be part of responsibilities or about the role. We'll keep them in About the role paragraph.
Now Requirements list:
- High school diploma or GED
- 5+ years of recent, hands-on professional experience in DevOps, Site Reliability Engineering (SRE), or a related role
- 5+ years of recent, hands-on experience with AWS
- 5+ years of recent, hands-on experience deploying, scaling, and managing Kubernetes environments
- 5+ years of recent, hands-on experience using Terraform for infrastructure-as-code
- 5+ years of recent, hands-on experience building and maintaining CI/CD pipelines using GitHub Actions
- Experience with Docker and containerized application environments
- Experience with monitoring and logging tools such as Prometheus, Grafana, Sentry, or the ELK stack
- Experience with incident response, on-call rotations, and follow-the-sun support models
- Strong communication skills with the ability to collaborate effectively across global teams and JP/NA time zones
Skills list: maybe we can separate out specific technologies and soft skills not covered by years-of-experience. But we already have many overlapping. To avoid duplication, we could decide not to have Skills section; but the instruction says we can include if we have real specific content. We have content for skills like "Experience with Docker...", "Experience with monitoring and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. 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. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include. We have content for About the role (intro paragraph). Responsibilities (list of duties). Requirements (list). Preferred Qualifications (list). Skills maybe not separate; could combine with Requirements? But they said we can have Skills section if there is specific content. The posting includes many skill-like items in Requirements; we could treat Requirements as skills. But we can still have Skills section if we want to separate? Probably better to have Requirements and Qualifications (Preferred). Skills maybe not needed. But we can include Skills if we want to list specific technical skills (AWS, Terraform, Kubernetes, GitHub Actions, Docker, Prometheus, Grafana, Sentry, etc). However those are already in Requirements. To avoid duplication, we could keep Requirements as list of experience years, and Skills as list of technologies. But the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one Requirements section. But they gave example headings including Skills. We can decide to include Skills if we have distinct content. Let's see: The posting includes "Experience with Docker and containerized application environments", "Experience with monitoring and logging tools such as Prometheus, Grafana, Sentry, or the ELK stack", "Experience with incident response, on-call rotations, and follow-the-sun support models", "Strong communication skills". Those could be considered skills. Meanwhile Requirements list includes years of experience with AWS, Kubernetes, Terraform, GitHub Actions, etc. So we could separate: Requirements = years of experience; Skills = specific technologies and soft skills. That seems reasonable. Qualifications = Preferred Qualifications list. Benefits = list. Pay = compensation. Schedule = contract length, hybrid, days onsite. About the role = introductory paragraph(s) describing role. We must not include boilerplate like EEO, diversity statement, visa sponsorship, etc. Remove those lines. We must preserve all substantive information. So we need to include all details from the posting except boilerplate. Let's extract substantive content: - Expected compensation: 90.00 - 95.00 USD Per Hour - HireArt is helping our client find a Senior DevOps Engineer to provide follow-the-sun coverage for the ADAS line of business, ensuring platform stability, SLA compliance, and rapid incident response during West Coast business hours. - In this role, you’ll deliver critical coverage during Japan's off-hours, enabling 24/7 SLA adherence for ADAS production systems running on a multi-tenant ecosystem. - You’ll partner closely with Japan-based DevOps teams, ADAS engineering (19+ engineers, scaling), and platform teams to maintain uptime, reliability, and operational excellence across multiple production environments. - The ideal candidate is an experienced DevOps/SRE professional who thrives in high-availability environments, is comfortable owning incidents end-to-end, and brings a strong automation-first mindset. - As a Senior DevOps Engineer, You'll Provide SEV-1/SEV-2 incident coverage during PST/PDT hours, ensuring 24/7 SLA adherence and meeting the 2-hour initial response target. - Deploy, manage, and scale AWS infrastructure (S3, Aurora/Postgres, IAM, Route 53, WAF, CloudFront) using Terraform and infrastructure-as-code best practices. - Build, maintain, and optimize CI/CD pipelines (GitHub Actions) to support consistent, reliable deployments across multiple environments (dev, stage, pre-production, production). - Monitor and support AWS and Kubernetes-based workloads (Stargate platform) to meet a 99.5% uptime target. - Track application and infrastructure performance using tools such as Prometheus, Grafana, Sentry, and related observability platforms. - Respond to incidents, perform root cause analysis, and implement corrective actions to improve system reliability. - Identify manual processes and implement automation to improve efficiency, reduce deployment times, and minimize operational overhead. - Integrate security best practices into CI/CD pipelines and infrastructure, ensuring compliance with DevSecOps and IaC standards. - Develop and maintain runbooks, documentation, and best practices to support knowledge sharing and seamless operations across global teams. - Requirements: - High school diploma or GED - 5+ years of recent, hands-on professional experience in DevOps, Site Reliability Engineering (SRE), or a related role - 5+ years of recent, hands-on experience with AWS - 5+ years of recent, hands-on experience deploying, scaling, and managing Kubernetes environments - 5+ years of recent, hands-on experience using Terraform for infrastructure-as-code - 5+ years of recent, hands-on experience building and maintaining CI/CD pipelines using GitHub Actions - Experience with Docker and containerized application environments - Experience with monitoring and logging tools such as Prometheus, Grafana, Sentry, or the ELK stack - Experience with incident response, on-call rotations, and follow-the-sun support models - Strong communication skills with the ability to collaborate effectively across global teams and JP/NA time zones - Preferred Qualifications: - Experience with service mesh technologies (e.g., Istio) - Understanding of DevSecOps practices, including secure deployments, vulnerability scanning, and incident response - Familiarity with SDLC and agile methodologies (Scrum, Kanban) - Experience working in multi-tenant or enterprise-scale platforms - Experience with backup/restore automation and disaster recovery processes - Familiarity with Nx monorepo tooling and multi-tenant architectures - Benefits: - PTO and paid holidays! - Pre-tax commuter benefits - Employer (HireArt) Subsidized healthcare benefits - Flexible Spending Account for healthcare-related costs - HireArt covers all costs for short and long term disability and life insurance - 401k package - Commitment: This is a full-time, 3-month contract position (with the possibility of extension) staffed via HireArt. This role is hybrid, requiring three days per week onsite in the Ann Arbor office. - HireArt values diversity and is an Equal Opportunity Employer. We are interested in every qualified candidate who is eligible to work in the United States. Unfortunately, we are not able to sponsor visas or employ corp-to-corp. (This is boilerplate EEO/visa; remove.) We must not include the EEO statement, visa sponsorship, etc. Now produce HTML. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
Expected compensation: 90.00 - 95.00 USD Per Hour
Schedule
This is a full-time, 3-month contract position (with the possibility of extension) staffed via HireArt. This role is hybrid, requiring three days per week onsite in the Ann Arbor office.
We need to ensure we don't duplicate content. Let's list responsibilities from the bullet points after "As a Senior DevOps Engineer, You'll Provide SEV-1/SEV-2 incident coverage..." and the subsequent bullet-like sentences. Actually the posting uses sentences not bullet list. We'll convert each to