DevOps Engineer (W2 ONLY)

We need to output HTML fragment with sections: About the role? Actually the posting includes responsibilities etc. We need to extract sections: About the role (maybe description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections if posting has real specific content. Let's parse. Posting text: "Our client is searching for a DevOps Engineer for a remote temp-to-perm position. ***All candidates must work directly for TEKsystems and no sponsorship will be available now or in the future*** Kubernetes Administration: Deploy, manage, and scale workloads on Kubernetes (GKE initially) utilizing Helm and Kustomize.Infrastructure as Code: Write modular, cloud-agnostic IaC using Terraform to provision workloads consistently across GCP, other public clouds, or on-prem environments.CI/CD Pipeline Ownership: Build, maintain, and optimize reusable GitHub Actions workflows for automated testing, containerization, and deployment.IAM & Platform Deployment: Deploy and scale high-availability Keycloak clusters; configure GitHub Workload Identity Federation (OIDC) to grant GitHub Actions secure, keyless access to GCP.Tooling Evaluation: Collaborate with technical leadership to evaluate deployment paradigms (e.g., traditional CI/CD vs. GitOps via ArgoCD/Flux). Pay will be based on experience and a drug and background check is required. Job Type & Location This is a Contract to Hire position based out of Dallas, TX. Pay And Benefits The pay range for this position is $40.00 - $50.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave) Workplace Type This is a fully remote position. Application Deadline This position is anticipated to close on Sep 30, 2026. About TEKsystems ... (boilerplate) ... etc." We need to remove boilerplate: About TEKsystems, equal opportunity, etc. Also remove application deadline? The instruction: remove application instructions. Application deadline is maybe considered application instruction? It's not exactly instruction but could be considered metadata. Probably we should drop it. Also remove "Job Type & Location" maybe we can incorporate location into a short p. But we should not repeat job title as heading. We need to include sections only if real content. We have responsibilities: list of duties: Kubernetes Administration, Infrastructure as Code, CI/CD Pipeline Ownership, IAM & Platform Deployment, Tooling Evaluation. Those are responsibilities. We have requirements? Not explicit but maybe "All candidates must work directly for TEKsystems and no sponsorship will be available now or in the future" is a requirement. Also "Pay will be based on experience and a drug and background check is required." That's a requirement. Also maybe "Contract to Hire position based out of Dallas, TX." That's job type/location. We have qualifications? Not explicit. Skills? Could be implied from responsibilities: Kubernetes, Helm, Kustomize, Terraform, GitHub Actions, Keycloak, OIDC, ArgoCD/Flux. Could list as skills. Benefits: listed many. Pay: range $40-50/hr. Schedule? Not given explicitly; remote fully remote but schedule not specified. So we should not create Schedule section unless posting states it. It does not. So omit Schedule. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each bullet as list items exactly as in posting? The posting uses colon headings with description after colon. We could turn each into list item with the full sentence. For responsibilities: "Kubernetes Administration: Deploy, manage, and scale workloads on Kubernetes (GKE initially) utilizing Helm and Kustomize." etc. For requirements: maybe list: "All candidates must work directly for TEKsystems and no sponsorship will be available now or in the future.", "Pay will be based on experience and a drug and background check is required.", "Contract to Hire position based out of Dallas, TX." Could also include "Remote fully remote position." Actually workplace type: fully remote. That could be a requirement or note. But we might include under responsibilities? Better as a requirement or note. Since it's not a responsibility, we could put under Requirements or maybe a separate section like "Workplace". But we only have allowed headings; we could put under Requirements or maybe under "About the role". However we need to avoid filler. Let's create sections: About the role (short description), Responsibilities, Requirements, Skills, Benefits, Pay. We need to ensure we don't repeat job title as heading. Good. Now craft HTML. First, About the role: maybe a paragraph summarizing: "Our client is searching for a DevOps Engineer for a remote temp-to-perm position. All candidates must work directly for TEKsystems and no sponsorship will be available now or in the future." That's substantive. But we already have that sentence in responsibilities? Actually it's a requirement. We could put in About the role. Let's decide: About the role: "Our client is searching for a DevOps Engineer for a remote temp-to-perm position. All candidates must work directly for TEKsystems and no sponsorship will be available now or in the future." Then Responsibilities: list the five items. Then Requirements: maybe include drug/background check, contract to hire, Dallas TX location, remote fully remote? Actually location: based out of Dallas, TX but fully remote. Could be contradictory but we keep both. We could also include "Contract to Hire position" as requirement. Skills: list the technologies: Kubernetes, GKE, Helm, Kustomize, Terraform, GitHub Actions, Keycloak, OIDC, ArgoCD, Flux. But we need to preserve all substantive information; we should not invent. The posting mentions "evaluate deployment paradigms (e.g., traditional CI/CD vs. GitOps via ArgoCD/Flux)". So we can list ArgoCD and Flux as examples. We could also list "modular, cloud-agnostic IaC using Terraform". So skill: Terraform. We could list "GitHub Workload Identity Federation (OIDC)". So skill: OIDC. We could list "Keycloak". So skill: Keycloak. We could list "CI/CD pipeline ownership using GitHub Actions". So skill: GitHub Actions. We could list "Kubernetes Administration". So skill: Kubernetes. We could list "Helm and Kustomize". So skill: Helm, Kustomize. We could list "Infrastructure as Code". So skill: IaC. We could list "Tooling Evaluation". Not a skill. We'll create a Skills section with bullet list of those. Benefits: list as given. Pay: paragraph with range. We must not include sections with filler like "commensurate with experience". Not present. Now produce HTML. We need to ensure no extra text outside HTML. Let's craft:

  About the role

  Our client is searching for a DevOps Engineer for a remote temp-to-perm position. All candidates must work directly for TEKsystems and no sponsorship will be available now or in the future.

  Responsibilities

  • Kubernetes Administration: Deploy, manage, and scale workloads on Kubernetes (GKE initially) utilizing Helm and Kustomize.
  • Infrastructure as Code: Write modular, cloud-agnostic IaC using Terraform to provision workloads consistently across GCP, other public clouds, or on-prem environments.
  • CI/CD Pipeline Ownership: Build, maintain, and optimize reusable GitHub Actions workflows for automated testing, containerization, and deployment.
  • IAM & Platform Deployment: Deploy and scale high-availability Keycloak clusters; configure GitHub Workload Identity Federation (OIDC) to grant GitHub Actions secure, keyless access to GCP.
  • Tooling Evaluation: Collaborate with technical leadership to evaluate deployment paradigms (e.g., traditional CI/CD vs. GitOps via ArgoCD/Flux).

  Requirements

  • Contract to Hire position based out of Dallas, TX.
  • Fully remote workplace.
  • Pay will be based on experience and a drug and background check is required.

  Skills

  • Kubernetes (including GKE)
  • Helm
  • Kustomize
  • Terraform (cloud-agnostic IaC)
  • GitHub Actions
  • Keycloak
  • OIDC (GitHub Workload Identity Federation)
  • ArgoCD
  • Flux

  Benefits

  • Medical, dental & vision
  • Critical Illness, Accident, and Hospital
  • 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
  • Life Insurance (Voluntary Life & AD&D for the employee and dependents)
  • Short and long-term disability
  • Health Spending Account (HSA)
  • Transportation benefits
  • Employee Assistance Program
  • Time Off/Leave (PTO, Vacation or Sick Leave)

  Pay

  The pay range for this position is $40.00 - $50.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.

  We should not include Schedule section. Check for any boilerplate leftover: we removed About TEKsystems, equal opportunity, etc. Good. Check if any content missing: we didn't include "Job Type & Location" as separate but we included contract to hire and Dallas TX and fully remote. That's covered. We didn't include "Application Deadline". That's okay to drop. We didn't include "Pay will be based on experience and a drug and background check is required." we included in Requirements. We didn't include "All candidates must work directly for TEKsystems and no sponsorship will be available now or in the future." we included in About the role. We didn't include "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms." That's somewhat boilerplate but it's substantive about benefits eligibility. Should we include? It's not a list but a statement. Could be included in Benefits section as a paragraph before list. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep that sentence. It's about benefits eligibility. Let's add a

  before the benefits list. Add under Benefits:

  Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan