Dev Ops Engineer

We need to output HTML fragment with sections: About Us? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. The posting includes "About Us" (description of company) but not "About the role". There's a "Job Description" paragraph. Could map that to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if content exists. We have content for About the role? The "Job Description" paragraph describes role. Could treat that as About the role. Also we have Responsibilities list. Requirements: there is "Required Experience". Qualifications: there is "Preferred Qualifications". Skills: maybe not separate; but we could combine required experience as Skills? However we should only create sections when posting has real specific content. We have content for Responsibilities, Required Experience (could be Requirements), Preferred Qualifications (could be Qualifications), Benefits & Rewards (Benefits). No explicit Pay or Schedule. So we should not include Pay or Schedule sections. Also we might include Skills? Not explicitly listed; but we could infer from Required Experience but better not to create a Skills section unless explicit. The instruction: "Prefer a few substantive sections over many thin ones." So we can have About the role, Responsibilities, Requirements, Qualifications, Benefits. Possibly also Skills? Not needed. We need to strip boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Our Recruitment Process Is As Follows Apply..." etc. Also remove "Equal Opportunities" line. Also remove "Fully Remote" time zone requirement? That's metadata; we can fold into short p or drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short p for time zone requirement maybe. We need to preserve all substantive information. So we need to keep the About Us description, the "What Makes Us Different" paragraph, the Job Description paragraph, Responsibilities list, Required Experience list, Preferred Qualifications list, Benefits & Rewards list. We must not repeat the job title as a heading. The job title is DevOps Engineer; we should not add heading for it. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

We are looking for an experienced DevOps Engineer to join our infrastructure team and help operate, maintain and evolve the infrastructure behind our core affiliate tracking platform. Our infrastructure is primarily hosted on AWS, so strong hands-on AWS experience is essential. You will work across cloud infrastructure, Linux systems, infrastructure as code, configuration management, containerised workloads, CI/CD pipelines, databases, monitoring and production operations. This is a hands-on engineering role suited to someone who is comfortable taking ownership of production infrastructure, troubleshooting complex issues and improving the reliability and automation of our environments.

Maybe also include About Us and What Makes Us Different as part of About the role? Could be separate section About Us? But headings limited to given list. Could treat About Us as part of About the role? Might be okay. But we also have "About Us" and "What Makes Us Different" which are substantive. Could we create a section "About the role" that includes both? Might be okay. Alternatively we could create a section "About the role" for job description, and another section "About the company"? Not in allowed headings. So we fold into About the role. Now Responsibilities: list items. We need

• for any list of duties/requirements/benefits. So:

  Responsibilities

  • Design, deploy, maintain and troubleshoot production infrastructure primarily hosted on AWS
  • Manage AWS environments and services including: AWS Organizations: EC2, Application Load Balancers (ALB), Lambdas, S3, RDS / Aurora MySQL, DynamoDB, ElastiCache / Redis, SQS and SNS, CloudWatch, AWS Backup, AWS WAF
  • Administer and troubleshoot Linux-based systems.
  • Build and maintain infrastructure using Terraform, with an emphasis on repeatable, version-controlled infrastructure.
  • Maintain and improve server and application configuration using Ansible.
  • Operate containerised applications using Docker and Docker Compose.
  • Build, maintain and improve Jenkins CI/CD pipelines for automated deployment and operational workflows.
  • Monitor infrastructure and applications using Grafana, Prometheus and AWS CloudWatch.
  • Manage and troubleshoot database infrastructure including MySQL / Aurora, DynamoDB and ClickHouse.
  • Operate and troubleshoot Redis-based workloads using AWS ElastiCache.
  • Investigate production incidents, identify root causes and implement permanent fixes.
  • Improve platform reliability, scalability, security and performance.
  • Automate repetitive operational tasks and reduce manual infrastructure management.
  • Review infrastructure changes and contribute to technical and architectural decisions.
  • Maintain appropriate backup, recovery, monitoring and alerting processes.
  • Work closely with developers and other technical teams to support application deployments and production environments.
  Now Requirements: we have Required Experience list.

  Requirements

  • Strong hands-on experience with AWS in production environments.
  • Strong Linux administration and troubleshooting skills.
  • Good understanding of AWS networking, security, IAM and infrastructure architecture.
  • Production experience with several of the AWS services used in our stack, particularly EC2, ALB, S3, RDS/Aurora, CloudWatch and AWS Organizations.
  • Strong experience with Terraform and infrastructure-as-code practices.
  • Experience with Ansible or comparable configuration-management tooling.
  • Good working knowledge of Docker and Docker Compose.
  • Experience building and maintaining CI/CD pipelines, ideally using Jenkins.
  • Experience operating and troubleshooting MySQL in production.
  • Experience with monitoring and observability platforms such as Prometheus, Grafana and CloudWatch.
  • Good understanding of networking concepts including DNS, HTTP/HTTPS, load balancing, firewalls, routing and TLS.
  • Ability to diagnose complex infrastructure and application issues across multiple layers of a production environment.
  • Comfortable working with Git and infrastructure-as-code development workflows.
  Qualifications: Preferred Qualifications list.

  Qualifications

  • Experience with any of the following would be beneficial, but is not required across the board: AWS Lambda and serverless architectures
  • DynamoDB
  • ClickHouse
  • Redis / AWS ElastiCache
  • SQS and SNS
  • AWS WAF
  • AWS Backup and disaster-recovery strategies
  • AWS multi-account environments and AWS Organizations
  • Infrastructure security and hardening
  • High-availability and scalable production architectures
  • Performance troubleshooting and capacity planning
  • Scripting and automation using Bash, Python or similar languages
  But note the original list is a paragraph: "Experience with any of the following would be beneficial, but is not required across the board: AWS Lambda and serverless architecturesDynamoDBClickHouseRedis / AWS ElastiCacheSQS and SNSAWS WAFAWS Backup and disaster-recovery strategiesAWS multi-account environments and AWS OrganizationsInfrastructure security and hardeningHigh-availability and scalable production architecturesPerformance troubleshooting and capacity planningScripting and automation using Bash, Python or similar languages". It's a bit messy; we need to split into items. We can keep as a single item? Better to split each separated by no punctuation. We'll parse: after colon, list: AWS Lambda and serverless architectures, DynamoDB, ClickHouse, Redis / AWS ElastiCache, SQS and SNS, AWS WAF, AWS Backup and disaster-recovery strategies, AWS multi-account environments and AWS Organizations, Infrastructure security and hardening, High-availability and scalable production architectures, Performance troubleshooting and capacity planning, Scripting and automation using Bash, Python or similar languages. We'll make each as
• . Now Benefits: Benefits & Rewards list.

  Benefits

  • A brilliant opportunity to grow your career & work with a fun, fast-paced & growing company, prepared to let you shine
  • An entrepreneurial environment where you learn more every day (we more than welcome and support people with their own projects)
  • Build an organization that continues to diversify its portfolio
  • Personal responsibility with a ton of autonomy
  • 33 free paid days
  • Market-leading remuneration and bonuses available
  • An international team with over 35 nationalities
  • Fully Remote working
  We might also include the description of Fully Remote meaning? That's more detail; could be included as a paragraph under Benefits? But we already have Fully Remote working as a bullet; we could add a paragraph after list describing what Fully Remote means. However that might be considered boilerplate? It's substantive. We'll add a

  after the list. Also we need to include time zone requirement: "Fully RemoteTime Zone Requirement: Candidates must be based in time zones spanning from the Americas through Southeast Asia to help maintain continuous 24/7 operational coverage." This is metadata; we can fold into a short p maybe under About the role or separate? Not a heading. We'll add a

  after About the role maybe. We must not include duplicated lines. Ensure we didn't repeat. Now output HTML fragment. Let's construct:

  About the role

  We are looking for an experienced DevOps Engineer to join our infrastructure team and help operate, maintain and evolve the infrastructure behind our core affiliate tracking platform. Our infrastructure is primarily hosted on AWS, so strong hands-on AWS experience is essential. You will work across cloud infrastructure, Linux systems, infrastructure as code, configuration management, containerised workloads, CI/CD pipelines, databases, monitoring and production operations. This is a hands-on engineering role suited to someone who is comfortable taking ownership of production infrastructure, troubleshooting complex issues and improving the reliability and automation of our environments.

  Time zone requirement: Candidates must be based in time zones spanning from the Americas through Southeast Asia to help maintain continuous 24/7 operational coverage.

  Then About Us and What Makes Us Different? We haven't included them. Could incorporate into About the role as additional paragraphs. Let's add after the role description a paragraph about company: "ClickOut Media is not just a company - it's a thriving ecosystem of diverse talent from around the globe. As a proudly remote-first organisation, we've cultivated an environment where creativity flourishes, collaboration is core, and innovation knows no bounds. With over +1000 team members, our startup culture fuels our growth, making us a leading force in multi-channel marketing. We specialise in delivering best-in-class SEO & Content solutions to esteemed clients worldwide." Then another paragraph: "What Makes Us Different At ClickOut Media, we thrive in the most competitive search verticals, operate across every major language, and conquer platforms you've probably never even heard of. Our dynamic approach, combined with our fast-paced environment, sets us apart in the industry. We're not just here to meet expectations; we're here to exceed them, every single time. Our relentless pursuit of excellence has been the cornerstone of our continuous success." We'll add those as

  elements. Now Responsibilities, Requirements, Qualifications, Benefits. Make sure no extra whitespace issues. Let's craft final HTML.