Senior Cloud Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Position Summary, Role Expectations, Required Qualifications, Preferred Qualifications, Language Skills, Physical Capabilities, EEO etc. We need to map content to sections. We should not repeat job title as heading. No Job ID. We need to remove boilerplate: EEO, equal opportunity, legal, etc. Also remove application instructions (none). Remove duplicated lines. We need to preserve all substantive info. We need to decide sections: "About the role" could be Position Summary. "Responsibilities" could be Role Expectations (includes many duties). "Requirements" maybe Required Qualifications. "Qualifications" maybe Preferred Qualifications? But we have both Required and Preferred; we could combine into Requirements and Qualifications? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections have content. We have Position Summary -> About the role. Role Expectations -> Responsibilities. Required Qualifications -> Requirements (or Qualifications). Preferred Qualifications could go under Qualifications (maybe as preferred). Could also put under Skills? But Skills section maybe for language skills, physical capabilities? Actually language skills and physical capabilities could be under Skills? But they are not typical skills; they'd be more like "Skills" maybe language skills and physical capabilities. However the instruction says use Skills heading for skills. We could put Language Skills and Physical Capabilities under Skills. Benefits, Pay, Schedule: none present, so omit those sections. Thus output:

About the role

... position summary ...

Responsibilities

• ... list items ...

We need to convert prose into

and lists into

• . The Role Expectations contains many sentences; we can break into list items for each duty. But we must preserve all substantive info; we can either keep as paragraphs or list. The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. So if we have a list of duties, we should use

    • . The Role Expectations is a series of duties; we can treat each sentence as a list item. However we need to ensure we don't lose nuance. Could also keep as prose paragraphs; but instruction says use list for any list of duties/requirements/benefits. So better to make list. Similarly Required Qualifications is a list; we can make
      • . Preferred Qualifications also list. Language Skills and Physical Capabilities could be under Skills heading as list or prose? They are enumerated items; we can make list. Thus sections: About the role (position summary) ->

        Responsibilities (role expectations) ->

        • Requirements (required qualifications) ->
          • Qualifications (preferred qualifications) ->
            • Skills (language skills + physical capabilities) -> maybe combine into one list? Could separate but still under Skills heading. We must not create empty sections. Now we need to extract content exactly, preserving all substantive information, not inventing or summarizing away detail. Must not omit any detail. So we need to copy all sentences from each section. Let's extract Position Summary: "Senior Cloud Infrastructure Engineer designs, builds, supports, and improves cloud infrastructure using Terraform and software-engineering practices, across a multi-account, multi-organization AWS environment. The role partners closely with application development, information security, architecture, and other technology teams to deliver secure, reliable, maintainable, and cost-conscious infrastructure at scale. This position serves as a senior technical resource for assigned cloud accounts and platforms, develops reusable Infrastructure as Code capabilities, reviews infrastructure designs and changes, supports production environments, and mentors less-experienced engineers." That's the summary. Now Role Expectations: It's a long paragraph with many sentences. We need to break into list items, each representing a duty. Let's parse: "The Senior Cloud Infrastructure Engineer applies software-development principles to infrastructure engineering: automated, version-controlled, reviewable, reusable, testable, documented, and supportable." "The engineer operates with significant technical independence within established architectural, security, compliance, and change-management requirements." "Infrastructure as Code — primarily Terraform and HashiCorp Configuration Language — is the standard approach for provisioning and managing cloud resources, designed for reuse across multiple environments and teams." "Cloud infrastructure must be secure, reliable, maintainable, observable, recoverable, and cost-conscious, spanning networking, identity and access management, compute, storage, security, monitoring, logging, secrets management, backup, and disaster recovery." "Infrastructure changes follow source-control, peer-review, testing, documentation, and change-management practices, including CI/CD pipelines built on GitHub Actions." "The engineer serves as a primary technical owner for assigned cloud accounts, platforms, and services — partnering with application teams on architecture, deployment patterns, scalability, resiliency, and supportability, and reviewing the infrastructure designs and IaC changes of other engineers." "The engineer troubleshoots complex infrastructure, deployment, and performance issues; participates in production support, incident response, and root-cause analysis; and identifies improvements to reliability, security, cost, and manual-effort reduction." "The engineer mentors less-experienced engineers through design discussions, code review, and technical guidance, and contributes to evolving cloud infrastructure standards and practices." "Manual configuration may occasionally be required, but automation is the default approach." "Participation in an on-call rotation, after-hours maintenance, and production-support activities is required." We need to keep each as list item. Now Required Qualifications list: "Seven or more years of professional experience designing, implementing, and supporting infrastructure in Amazon Web Services." "Five or more years of experience developing and maintaining production Infrastructure as Code." "Strong proficiency with Terraform and HashiCorp Configuration Language, including modules, providers, state management, dependency handling, expressions, data sources, lifecycle controls, and reusable configuration patterns." "Experience using Python, TypeScript, or JavaScript to develop infrastructure tooling, automation, or operational utilities." "Demonstrated ability to design reusable, maintainable, and testable infrastructure components." "Experience using Git-based source control, pull requests, peer review, branching strategies, and automated delivery workflows, including GitHub Actions or comparable CI/CD platforms." "Experience designing and supporting highly available, secure, and resilient cloud infrastructure." "Strong understanding of cloud networking, identity and access management, compute, storage, security, observability, and managed-service concepts." "Experience designing and supporting infrastructure across multi-account or multi-environment cloud platforms." "Experience supporting Linux and Windows operating-system environments." "Experience troubleshooting complex distributed systems and production cloud environments." "Ability to evaluate technical requirements, identify risks and tradeoffs, and recommend appropriate solutions." "Ability to communicate effectively with software engineers, infrastructure engineers, security professionals, architects, and technology leaders." "Ability to independently manage technical work while collaborating across multiple technology disciplines." "Experience mentoring engineers and providing constructive technical review." "Equivalent professional experience may be considered in place of formal education." Now Preferred Qualifications list: "Experience supporting infrastructure subject to HIPAA, PCI DSS, or similar regulatory and security requirements is a meaningful differentiator for this role, given the sensitivity of the environments this team supports; candidates with this background will be viewed more favorably, all else being equal." "Experience with Pulumi for infrastructure component development." "Experience with container technologies and Kubernetes." "Experience supporting applications developed in C# or Java." "Experience with CircleCI or other CI/CD platforms beyond GitHub Actions." "Experience implementing policy as code, automated infrastructure testing, security validation, or compliance controls." "Experience with Microsoft Azure, Google Cloud Platform, Oracle Cloud Infrastructure, or other public-cloud platforms." "AWS, Terraform, Pulumi, cloud, security, or Kubernetes certifications are beneficial but are not required." Now Language Skills: "Ability to read, analyze and interpret general business periodicals, professional journals, technical procedures or governmental regulations." "Ability to write reports, business correspondence and procedure manuals." "Ability to effectively present information and respond to questions from a variety of both internal and external sources." Physical Capabilities: "The physical capabilities described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. While performing the duties of this job, the employee is regularly required to sit; use hands to finger, handle, or feel; reach with hands and arms; and talk or hear. The employee is occasionally required to stand and walk. The employee must occasionally lift and/or move up to 10 pounds. Specific vision abilities required by this job include close vision, distance vision, color vision, peripheral vision, depth perception, and ability to adjust focus." We need to include all that under Skills heading. Could split into two lists: Language Skills and Physical Capabilities, but both under Skills heading. Could make separate
              • for each? Might be okay to have two lists under same heading. But instruction: Use
                • for any list of duties/requirements/benefits, and

                  for prose. Language Skills and Physical Capabilities are lists; we can make

                  • . Could also combine into one list but that would mix categories; better to keep separate lists but still under same heading. We'll output:

                    Skills

                    Language Skills

                    ? But we only allowed h3 for section headings; we cannot use h4? Not prohibited but they said use

                    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only h3 for sections. Inside we can have

                    or

                    • . We could have two
                      • groups separated by a

                        heading? But we cannot add extra headings besides h3. Could we add a

                        with bold? Not allowed? Probably better to just make one list combining both language and physical capabilities items. But that would lose distinction but still preserve all items. The instruction: "Prefer a few substantive sections over many thin ones." So combining is okay. We'll just make a single list under Skills containing all language and physical capabilities items. Thus Skills list items: - Ability to read, analyze and interpret general business periodicals, professional journals, technical procedures or governmental regulations. - Ability to write reports, business correspondence and procedure manuals. - Ability to effectively present information and respond to questions from a variety of both internal and external sources. - The physical capabilities described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. - While performing the duties of this job, the employee is regularly required to sit; use hands to finger, handle, or feel; reach with hands and arms; and talk or hear. - The employee is occasionally required to stand and walk. - The employee must occasionally lift and/or move up to 10 pounds. - Specific vision abilities required by this job include close vision, distance vision, color vision, peripheral vision, depth perception, and ability to adjust focus. Now we need to ensure we didn't include boilerplate: EEO, equal opportunity, etc. We removed those lines. Also remove "Note: This Job Description may not describe all of the job responsibilities..." etc. That's boilerplate; remove. Also remove "RevSpring is an equal opportunity employer..." etc. Also remove "Nothing in this job description constitutes a contract for employment." Now produce HTML fragment. Let's craft. We'll need to escape any HTML special characters? The text includes punctuation like em dashes, etc. Should be fine as plain text. We'll output:

                        About the role

                        Senior Cloud Infrastructure Engineer designs, builds, supports, and improves cloud infrastructure using Terraform and software-engineering practices, across a multi-account, multi-organization AWS environment. The role partners closely with application development, information security,