Stop applying to remote jobs that are already dead.
Every listing shows the evidence: when we last checked it, how, and when it was posted and closed.

All listings

Phizenix via Greenhouse

Principal Platform Engineer

Location not stated senior
still open verified just now posted 3h ago seen 1h ago
Apply at job-boards.greenhouse.io

This is the employer's own posting, not a copy on a job board.

What we know

Is it still open?

Confirmed still open

Last checked just now — checked against the employer's own applicant tracking system, which is the company answering directly.

We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.

Check this listing's status as JSON

How old is it?

Posted 3h ago

The date the source published, not the day we noticed it (2026-10-14). Last seen at its source 1h ago.

Is it remote?

Remote

That is the location the employer filed this posting under. Quoted as written — we do not re-word the source's own location.

Who may apply?

Not stated

The description states no restriction of its own. This is the source's own tag.

Skills named in the ad

AgileAzureCI/CDCode ReviewGitGitHub ActionsISO 27001Incident ManagementInfrastructure as CodeKubernetesObservabilityPythonSLI/SLOSOC 2Supply ChainTerraformTypeScript

Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.

Carried by 1 source

The listing

Required

  • 15+ years in software engineering, platform or infrastructure engineering, or a closely related technical field.
  • Deep, hands-on expertise in infrastructure as code at fleet scale (Terraform or OpenTofu with Terragrunt or equivalent): module architecture, remote state, multi-environment topology.
  • Demonstrated experience operating multi-tenant Kubernetes platforms in production: GitOps, network and admission policy, workload identity, tenant isolation.
  • Proven track record building CI/CD as a shared platform (GitHub Actions or equivalent), with reusable workflow contracts, fleet-scale branch protection, and enforced quality and security gates.
  • Strong hands-on command of cloud identity and network security on Azure/AWS/GCP or a comparable hyperscaler: workload identity federation, RBAC, private networking, WAF, DNS.
  • Substantive experience with security and compliance as code: scanning toolchains (Snyk, Checkov, Trivy), policy engines (OPA, Kyverno, Azure Policy), supply chain controls (signing, provenance, SBOM), and SOC2 / ISO 27001 control evidence.
  • Production observability with OpenTelemetry or equivalent: collector topology, SLOs and error budgets, alert routing, incident management, fault injection.
  • Has built and operated production application software as a software engineer, in at least one of Go, Python, or TypeScript, and is fluent in testing strategy, code review, trunk-based delivery, and release management.
  • Excellent written and verbal communication skills in English; ability to translate complex technical topics to diverse audiences, including executive stakeholders.
  • Experience with Agile methodologies and cross-functional product team collaboration.

 

Preferred / Additional Qualifications

  • Experience building platforms for consulting, advisory, or professional services, including client-isolation and data-residency requirements.
  • Familiarity with virtual-cluster and control-plane tooling (vcluster, Crossplane) and developer portals (Backstage, Port).
  • Experience operating a platform used by AI coding assistants (Claude Code, GitHub Copilot or similar), including sandboxing of agent tooling.
  • Advanced certifications in cloud architecture, Kubernetes, or security (e.g., Azure Solutions Architect, CKA/CKS, CISSP).
  • FinOps experience: cost allocation, showback, and cloud cost optimization.
  • Demonstrated enthusiasm for developer education — writing internal guides, running workshops, or building internal tooling communities.
Apply at job-boards.greenhouse.io