Infrastructure Automation Engineer

maybe. But we must not invent headings not present. We could have Qualifications heading and then two

paragraphs introducing required and preferred, each followed by

. That seems okay. Skills: Could be derived from qualifications but not explicit separate list. Might not need Skills section if not explicit. The posting does not have a separate "Skills" heading. So we may omit Skills. Benefits: not mentioned. Pay: we have Salary Range. Schedule: not mentioned beyond full-time; but we could include Schedule if we infer full-time? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "Position Type: Full-time, Direct W2". That's a schedule type (full-time). So we could include Schedule section with that info. It's specific enough. So include Schedule. Thus sections: About the role, Responsibilities, Qualifications (with required and preferred), Pay, Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, application instructions, etc. Also remove "How to Apply" etc. Also remove "Powered by JazzHR". Also remove sponsorship lines? Sponsorship is part of eligibility; maybe keep under Qualifications? It's not a qualification but a requirement. Could be placed under Requirements? But we don't have Requirements section; we could include under Qualifications as a note. However we might create a Requirements section for experience required and sponsorship. But we already have Required Qualifications list. The sponsorship line is separate: "Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position." This is eligibility. Could be placed under Requirements or Qualifications. Since we have Qualifications heading, we could add a

after the heading describing eligibility. But we must not invent filler. It's real content, so we can include. Thus structure:

About the role

... (company description and opportunity)

Responsibilities

... list items ...

Qualifications

Required:

... required qualifications list ...

Preferred:

... preferred qualifications list ...

Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position.

Pay

Salary Range: $100,000–$180,000 Annually

Schedule

Position Type: Full-time, Direct W2

We need to ensure we preserve all substantive information from the posting. Let's extract About the role paragraph: "Infrastructure Automation Engineer - Remote Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential." We should keep that as is. Responsibilities list: we need to copy each bullet exactly as in posting. Let's list them: - Design, develop, and maintain modular, composable Terraform code that codifies the entire infrastructure estate across cloud accounts and environments - Build a library of well-tested, reusable Terraform modules with clear interfaces, semantic versioning, and comprehensive documentation - Implement Terraform automation pipelines using GitHub Actions, GitLab CI, Atlantis, Terraform Cloud, or Spacelift, with plan/apply gating, drift detection, and policy enforcement - Define and enforce policy-as-code using Sentinel, Open Policy Agent (OPA), Conftest, or Checkov to prevent insecure or non-compliant infrastructure changes - Manage Terraform state at scale with appropriate backend strategies, state locking, workspace organization, and disaster recovery patterns - Drive multi-account, multi-region, and multi-cloud infrastructure provisioning strategies with clear isolation, naming, and tagging standards - Implement infrastructure testing including unit tests with terraform-compliance, integration tests with Terratest, and policy tests across pull requests - Collaborate with security, networking, and platform teams to embed guardrails directly into reusable modules and pipelines - Standardize patterns for secrets management, identity federation, and least-privilege IAM through reusable Terraform abstractions - Lead migrations from legacy, ClickOps, or non-IaC infrastructure into managed Terraform footprints with minimal disruption - Drive cost optimization, tagging hygiene, and lifecycle management across the Terraform-managed estate - Mentor engineering teams on Terraform best practices, anti-patterns, and pull-request review standards - Maintain comprehensive runbooks, architecture diagrams, and onboarding materials for the infrastructure platform - Stay current with Terraform, OpenTofu, and broader IaC ecosystem developments and recommend adoption where beneficial Required Qualifications list: - Bachelor’s degree in Computer Science, Engineering, or a related field - Five or more years of experience in cloud infrastructure or DevOps engineering, with significant Terraform focus - Deep, hands-on expertise authoring and maintaining production Terraform across at least one major cloud provider - Strong experience designing reusable Terraform modules with clean APIs and version discipline - Hands-on experience with Terraform state management, backends, and large-scale workspace organization - Strong scripting skills in Python, Go, or Bash - Experience with CI/CD pipelines for infrastructure code and automated policy enforcement - Solid understanding of cloud networking, identity, and security primitives - Strong Git-based workflows including code review, branching, and release management - Excellent troubleshooting and root-cause analysis skills Preferred Qualifications list: - Experience with multi-cloud Terraform (AWS + Azure or AWS + GCP) - Familiarity with Terragrunt, Atlantis, Spacelift, or env0 - Experience with policy-as-code engines (Sentinel, OPA, Checkov) - Contributions to public Terraform modules or providers - Exposure to FinOps practices and tagging-driven cost governance Also there is "Experience Required: 12+ years" earlier. That seems to conflict with Required Qualifications which says 5+ years. The posting includes both: "Experience Required: 12+ years" and then Required Qualifications says 5+ years. We must preserve ALL substantive information. So we need to include both. Where to place? Could be under Qualifications as a note: "Experience Required: 12+ years". Or we could have a Requirements section for that. Since we have Qualifications heading, we could add a

before required list: "Experience Required: 12+ years". Then required qualifications list. Also Sponsorship line we already added. Also there is "Position Type: Full-time, Direct W2" we used for Schedule. Also there is "Location: 100% Remote (U.S.)". That's location info; we could include under About the role or maybe a separate section? Not listed as a heading option but we could fold into About the role paragraph. The About the role currently doesn't mention location. We could add a sentence: "Location: 100% Remote (U.S.)". Since we must preserve all substantive information, we should include it. Where to put? Could be in About the role paragraph after company description. Let's incorporate: "Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential. Location: 100% Remote (U.S.)." That preserves. Also there is "Job Title: Infrastructure Automation Engineer" but we must not repeat as heading. So we can ignore. Also there is "We are unable to sponsor new H-1B visa petitions for this position." Already in sponsorship note. Also there is "Learn more about Bright Vision Technologies at www.bvteck.com." That's boilerplate? It's not navigation/legal/EEO but it's a link. Might be considered application instructions? It's not exactly application instructions but could be considered extra info. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly application instructions but could be considered promotional. Might be safe to keep? It's not required. I'd say we can keep it as part of About the role? It's not essential but it's substantive. However it's a link to learn more; could be considered application instructions? Not exactly. I'd keep it maybe as a separate

under About the role. But to be safe, maybe omit as it's not critical. The instruction says remove application instructions; this is not that. It's just a link to learn more. I'd keep it. Also "We are seeking an Infrastructure Automation Engineer with deep Terraform expertise..." That's part of About the role? Actually after company description, there is a paragraph: "We are seeking an Infrastructure Automation Engineer with deep Terraform expertise to design, build, and maintain the infrastructure-as-code foundations that power our cloud and hybrid environments. This role focuses on creating reusable Terraform modules, hardening pipelines, enforcing policy-as-code, and standardizing infrastructure delivery across multiple teams and cloud providers. The ideal candidate brings strong software engineering discipline to infrastructure work, has shipped production-grade Terraform at scale, and understands the operational realities of managing thousands of resources across many environments and accounts." This is also substantive; we should include it maybe in About the role or as a separate section? Could be part of About the role. Let's incorporate into About the role paragraph(s). We'll have maybe two paragraphs: first about company and opportunity, second about the role specifics. Thus About the role could contain multiple

elements. Now we need to output only HTML fragment, no /. We'll output:

About the role

Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential.

We are seeking an Infrastructure Automation Engineer with deep Terraform expertise to design, build, and maintain the infrastructure-as-code foundations that power our cloud and hybrid environments. This role focuses on creating reusable Terraform modules, hardening pipelines, enforcing policy-as-code, and standardizing