Platform Engineer

nOps; Northern (KY); Hybrid; USD 120,000 - 180,000; Full time

Job summary

nOps is a Series A FinOps platform managing cloud spend across AWS, Azure, and GCP. We seek a Platform Engineer to own core infrastructure, drive automation, and set architectural direction with engineering leadership.

You will work on securing, scaling, and automating a multi-cloud platform with strong emphasis on cost visibility and autonomous operations. You will design and maintain IaC, manage IAM at scale, and lead incident response while collaborating with cross-functional teams to ensure

Qualifications

• 3+ years of experience as a platform or infrastructure engineer.
• Deep hands-on experience with AWS IAM (trust policies, SCPs, role chaining, OIDC federation) and broader AWS architecture.
• Experience with OpenTelemetry and observability instrumentation.
• Strong experience operating Kubernetes in production, ideally EKS or GKE.
• Experience with GCP, including billing/cost data and BigQuery.
• Proficiency with OpenTofu or Terraform for infrastructure-as-code at scale.
• Experience owning CI/CD tooling and pipelines.
• Track record of leading or heavily contributing to incident response.
• Comfort operating as an autonomous individual contributor who owns infrastructure end to end.

Responsibilities

• Own and evolve multi-cloud infrastructure across AWS, Azure, and GCP, including compute, networking, storage, and cost/billing systems.
• Design and maintain Infrastructure-as-Code for provisioning, tagging, and governance across environments.
• Manage IAM and access controls at scale: trust policies, SCPs, role chaining, and OIDC federation.
• Operate and scale container orchestration platforms, including EKS, GKE, and ECS clusters supporting production workloads.
• Build and maintain data pipelines, including billing/cost data pipelines (e.g., GCP BigQuery, Databricks, CUR/FOCUS exports).
• Support and extend internal AI agent tooling used for DevOps and platform workflows.
• Own observability tooling and practices: metrics, logging, and alerting across the platform.
• Lead incident response for platform and infrastructure issues, from triage through resolution and postmortem.
• Partner with engineering leadership to set technical direction for platform investments and priorities.
• Document systems and processes to support knowledge continuity across the org.

Skills

Platform engineering

AWS IAM

Kubernetes (EKS/GKE)

OpenTelemetry

CI/CD tooling

Incident response leadership

Autonomous contributor

Documentation

Tools

Terraform/OpenTofu

Job description

About the nOps

nOps is a Series A FinOps platform managing over $5B in cloud spend across AWS, Azure, and GCP. We help engineering and finance teams gain real-time cloud cost visibility and achieve autonomous optimization.

The Role

nOps is looking for a Platform Engineer to help own our core cloud infrastructure and platform engineering function. This is a high-autonomy, high-impact role: working alongside our lead software engineer, you'll be responsible for keeping our multi-cloud platform running, secure, and scalable — with an eye toward building infrastructure resilient enough to largely take care of itself. You'll work directly with engineering leadership and cross-functional teams to help drive infrastructure strategy, not just execute tickets. This role suits someone who wants deep ownership over a broad, consequential piece of the stack rather than a narrow slice of a much larger platform team.

What You'll Do

• In this role, you'll spend as much energy building the automation and guardrails that prevent problems as you will responding to the ones that slip through.
• Own and evolve multi-cloud infrastructure across AWS, Azure, and GCP, including compute, networking, storage, and cost/billing systems
• Design and maintain Infrastructure-as-Code (OpenTofu/Terraform) for provisioning, tagging, and governance across environments
• Manage IAM and access controls at scale: trust policies, service control policies (SCPs), role chaining, and OIDC federation
• Operate and scale container orchestration platforms, including EKS, GKE, and ECS clusters supporting production workloads
• Build and maintain data pipelines, including billing/cost data pipelines (e.g., GCP BigQuery, Databricks, CUR/FOCUS exports)
• Support and extend internal AI agent tooling used for DevOps and platform workflows
• Own observability tooling and practices: metrics, logging, and alerting across the platform
• Lead incident response for platform and infrastructure issues, from triage through resolution and postmortem
• Partner with engineering leadership to set technical direction for platform investments and priorities
• Document systems and processes to support knowledge continuity across the org

What We're Looking For

• 3+ years of experience as a platform or infrastructure engineer
• Deep, hands-on experience with AWS IAM (trust policies, SCPs, role chaining, OIDC federation) and broader AWS architecture
• Experience with OpenTelemetry and observability instrumentation
• Strong experience operating Kubernetes in production, ideally EKS or GKE
• Experience with GCP, including billing/cost data and BigQuery
• Proficiency with OpenTofu or Terraform for infrastructure-as-code at scale
• Experience owning CI/CD tooling and pipelines
• A track record of leading or heavily contributing to incident response
• Comfort operating as an autonomous individual contributor who owns infrastructure end to end — someone who can set direction, not just follow it
• Motivated to build systems stable and well-automated enough that they run themselves — your input should be needed only when something actually fails, not for routine upkeep
• Strong written communication skills; this role requires clear documentation and cross-functional coordination
• Bonus: experience with cloud cost management/FinOps domains
• Bonus: experience building or integrating internal AI/agent tooling

Why This Role Matters

This is a foundational role at nOps. Whoever fills it will inherit and shape the infrastructure, tooling, and practices that the entire engineering org depends on daily.