AWS Cloud Engineer

We need to output HTML fragment with sections: headings using

for section headings 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. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it. Avoid filler like "commensurate with experience". No Pay/Schedule/Benefits sections unless posting actually states them. The posting mentions "Why Stout?" includes benefits, compensation, flexible work schedules, discretionary time off, etc. So we can have Benefits section. Pay? Not specific numbers, just "competitive compensation". That's vague; we should not create Pay section unless posting actually states them. It says "competitive compensation" but not specific. Likely we should not create Pay section because it's not specific. Schedule? It mentions flexible work schedules and discretionary time off policy. That's schedule info. Could we create Schedule section? It says "Stout provides flexible work schedules and a discretionary time off policy". That's specific enough? It's not a specific schedule but mentions flexible work schedules. Might be considered schedule info. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state flexible work schedules and discretionary time off. So we can include Schedule section with that content. Benefits section: they mention comprehensive Total Rewards program with competitive compensation, benefits, wellness options, professional growth, etc. That's benefits. So include Benefits. We also need sections: About the role? The posting starts with "At Stout, we’re dedicated..." then "Impact You’ll Make". Could treat "About the role" as a heading? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to include based on content. We have content: Impact You’ll Make (could be Responsibilities). What You’ll Do (Responsibilities). What You’ll Bring (Requirements/Qualifications/Skills). How You’ll Thrive (maybe Skills or Qualities). Why Stout? (Benefits). Also maybe "About the role" could be the introductory paragraph about Stout and the role. We can include an About the role section with the introductory paragraph: "At Stout, we’re dedicated to exceeding expectations...". That seems appropriate. We must not repeat job title as heading. The job title is AWS Cloud Engineer, but we shouldn't put that as heading. We need to use

  • for any list of duties/requirements/benefits. So for responsibilities list, we should convert the bullet-like sentences into
    • . The posting has sentences separated by periods; we can treat each as a list item. Similarly for requirements. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all details. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement, etc. Remove that. Also remove the link to benefits? The instruction says remove application instructions. The link to benefits might be considered part of benefits but it's a URL; we could keep it as part of benefits? It's a link to learn more about benefits. Might be considered application instruction? It's not exactly instruction to apply, but it's a link. Might keep as part of benefits? Safer to keep the URL as part of benefits paragraph? The instruction: remove application instructions. The link is not an instruction to apply, it's just a link to learn more about benefits. I'd keep it. We also need to remove duplicated lines. I don't see duplicates. Now craft HTML. Structure:

      About the role

      At Stout, we’re dedicated to exceeding expectations in all we do – we call it Relentless Excellence ®. Both our client service and culture are second to none, stemming from our firmwide embrace of our core values: Positive and Team-Oriented, Accountable, Committed, Relationship-Focused, Super-Responsive, and being Great communicators. Sound like a place you can grow and succeed? Read on to learn more about an exciting opportunity to join our team.

      Impact You’ll Make

      maybe we treat as Responsibilities. Could use heading Responsibilities. But the posting uses "Impact You’ll Make". Should we use that as heading? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict; we can use those exact headings if they match content. However we could also use "Impact You’ll Make" as a heading but it's not in the list. Safer to map to Responsibilities. Use

      Responsibilities

      . Then list items. Similarly "What You’ll Do" could also be responsibilities but we already have responsibilities. Might combine? Actually "Impact You’ll Make" and "What You’ll Do" are similar; we could merge them under Responsibilities. But we must preserve all info; we can just put all under Responsibilities list. Then "What You’ll Bring" could be Requirements or Qualifications. We'll use

      Requirements

      (or Qualifications). The list includes experience, skills, preferred. We'll put as list. "How You’ll Thrive" could be Skills or Qualities. Could be Skills section. Use

      Skills

      . "Why Stout?" could be Benefits. Use

      Benefits

      . Also maybe Schedule section: flexible work schedules and discretionary time off. We'll add

      Schedule

      with that info. We must not create Pay section. Now ensure we use
      • for any list of duties/requirements/benefits. For Benefits, we have a paragraph describing benefits; we could also make a list if there are bullet points. The benefits description includes: comprehensive Total Rewards program with competitive compensation, benefits, and wellness options tailored to support employees at every stage of life; culture of inclusion and respect; leadership committed to inclusion and belonging; invest in professional growth through ongoing training, mentorship, employee resource groups, clear performance feedback; flexible work schedules and discretionary time off policy. That's more prose; we could keep as

        . But the instruction says use

        • for any list of duties/requirements/benefits. If we have a list, we should use list. The benefits description is not a list but we could split into items. However to be safe, we can keep as

          for benefits because it's not explicitly a list. The instruction says "Use

          • for any list of duties/requirements/benefits". If it's not a list, we can use

            . So we'll use

            . Similarly for Schedule we have flexible work schedules and discretionary time off policy; could be

            . Now we need to ensure we don't include any boilerplate like EEO statement. Remove that. Now craft HTML. Let's extract responsibilities from "Impact You’ll Make" and "What You’ll Do". Combine. Impact You’ll Make sentences: - As an AWS Cloud Engineer, you will support the reliability, scalability, and security of Stout’s cloud infrastructure. - You will manage AWS environments, infrastructure automation, CI/CD pipelines, and containerized workloads while helping teams improve deployment processes and production operations. - Build and maintain reliable AWS infrastructure using Infrastructure as Code practices. - Support containerized applications and production environments with a focus on availability, security, and performance. - Improve deployment consistency through automated CI/CD pipelines and Git-based workflows. - Monitor cloud environments, respond to incidents, and address infrastructure and application reliability issues. - Identify opportunities to improve cloud operations, automation, security, and cost management. What You’ll Do sentences: - Build, manage, and maintain AWS infrastructure using Terraform and Infrastructure as Code practices. - Administer AWS services including ECS, EC2, VPC, ALB/NLB, Auto Scaling, IAM, S3, Secrets Manager, and Systems Manager. - Manage Docker-based workloads and ECS services, including deployments, scaling, capacity management, and production troubleshooting. - Build and maintain CI/CD pipelines using AWS CodePipeline, CodeBuild, GitHub Actions, or comparable technologies. - Configure and maintain AWS networking, security groups, load balancing, TLS certificates, private connectivity, and access controls. - Maintain monitoring, logging, and alerting through CloudWatch and related observability tools. - Troubleshoot production incidents involving AWS infrastructure, containers, networking, and deployment pipelines. - Support high availability, backup and recovery, capacity planning, cloud security, and cloud cost management. - Maintain infrastructure and deployment configurations in Git using peer-reviewed, GitOps-based workflows. - Develop and maintain operational documentation, automation, and runbooks that support reliable cloud operations. - Partner with technology teams to improve platform engineering practices, developer tooling, and operational processes. We should combine and deduplicate similar items. There's overlap: Build and maintain reliable AWS infrastructure using IaC appears in both; we can keep one. Also monitor etc. We'll keep all but avoid exact duplicates. We'll just list all unique items. Now requirements from "What You’ll Bring": - Strong hands-on experience managing AWS infrastructure and production environments. - Advanced Terraform experience, including reusable modules, remote state management, and multi-environment deployments. - Strong Docker and container orchestration experience, preferably with AWS ECS. - Experience building or supporting CI/CD pipelines using AWS CodePipeline, CodeBuild, GitHub Actions, Jenkins, GitLab CI, or similar tools. - Strong knowledge of AWS networking, including VPCs, subnets, security groups, load balancers, NAT, and IAM. - Experience with CloudWatch, monitoring, logging, incident response, and production troubleshooting. - Strong understanding of Git, Infrastructure as Code, GitOps, cloud security, and highly available AWS architectures. - Experience with MongoDB Atlas, OpenSearch, Redis, ElastiCache, or Valkey is preferred. - Familiarity with security tools such as Wazuh, Falco, Rapid7, Action1, or comparable technologies is preferred. - Experience with EC2 Image Builder, Lambda, SNS, Fluentd, or related AWS automation and observability tools is a plus. - Familiarity with PHP/Laravel, Python/Flask, Celery, and Redis-based application architectures is preferred. - Experience with platform engineering, developer tooling, operational automation, or runbook development is a plus. Now "How You’ll Thrive" (Skills): - Take ownership of cloud infrastructure and follow operational issues through resolution. - Apply sound judgment when troubleshooting production incidents and making infrastructure changes. - Balance reliability, security, performance, and cost when evaluating cloud solutions. - Maintain clear documentation and disciplined change management practices. - Collaborate effectively with engineering and technology teams to improve deployment and operational processes. - Stay current with AWS services, cloud infrastructure practices, and emerging technologies relevant to the environment. - Embody Stout’s core values: Positive and Team-Oriented, Accountable, Committed, Relationship-Focused, Super-Responsive, and Great Communicators. - Deliver Relentless Excellence® through reliable infrastructure, disciplined execution, and continuous improvement. Now Benefits from "Why Stout?": - At Stout, we offer a comprehensive Total Rewards program with competitive compensation, benefits, and wellness options tailored to support employees at every stage of life. - We foster a culture of inclusion and respect, embracing diverse perspectives and experiences to drive innovation and success. - Our leadership is committed to inclusion and belonging across the organization and in the communities we serve. - We invest in professional growth through ongoing training, mentorship, employee resource groups, and