DevSecOps Engineer

Responsibilities

• Cloud infrastructure as codeBuild the cloud foundation in Terraform and OpenTofu, to a high standard. You design Azure infrastructure to be configurable, so the platform can provision clusters of different profiles, such as front-facing, data-oriented, and developer-oriented, from the same well-factored code.You treat infrastructure as code as software: small, composable modules that assemble into a coherent foundation, with the versioning, review, and testing that keep them reliable and reusable. The desired state lives in Git, the platform reconciles it through GitOps, and drift is detected rather than discovered.
• Platform engineering on KubernetesBuild platform-as-a-service on that foundation and operate both the platform and the capabilities that run on it: observability, multi-tenancy, RBAC, governance, and FinOps.Alongside the security controls that keep it sound, including Pod Security Standards and Admission, a zero-trust posture with workload-to-workload mTLS, and supply-chain integrity through image signing.New initiative also includes enabling AI workloads, such as model serving and a governed AI gateway.
• DevOps and golden pathsWork across teams to build the golden paths developers follow paved routes for build, test, and release that are efficient and enforce code quality and security by default, so the secure path is also the easy one.You also build the services that support delivery, integrating testing, security scanning, SBOM generation, and observability into the pipeline, so pipeline health, runner configuration, and the state of the delivery system stay visible and well managed.
• Developer self-serviceBuild the interfaces that let developers' provision what they need, such as team identity and access, correctly configured repositories, namespaces, and cluster resources, without the platform team becoming a bottleneck.The goal is a platform that scales through self-service rather than manual requests, with every capability maturing toward being self-served or provided by default. You document these paths as you build them, so runbooks and golden-path guides are part of the deliverable.
• Operate and keep it reliableOwn the platform at runtime, not just at provisioning. You define and measure the SLIs and SLOs for the capabilities you ship, write the runbooks that make failure recoverable, and lead incident response when the platform degrades.You plan and run lifecycle work, such as cluster and component upgrades, with no data loss and minimal disruption to the teams on top, and when something breaks, you trace it to root cause and fix it accordingly.

REQUIREMENTS:

Education

• Bachelor's degree in computer science, Information Technology or related field.
• Master's degree in Computer Science or Information Technology if applicable

Essential Skills/Experience

• Several years building platform or DevOps capabilities end to end, from a developer problem to a production-grade, self-service solution (three to five years is a useful guide).
• Strong, hands-on Kubernetes experience in production, including RBAC, admission control, and diagnosing and resolving platform issues under pressure.
• Solid infrastructure-as-code practice (Terraform or OpenTofu) and a GitOps approach to delivery (FluxCD or Argo CD).
• A working command of CI/CD pipelines and release strategy (GitLab pipelines, or equivalent).
• A sound grasp of cloud-native security: least privilege, network segmentation, secrets management, identity, and supply-chain integrity.
• Operational maturity: defining SLOs, responding to incidents, and running upgrades safely in production.
• Proficiency in at least one of Go, Python, or Bash, and comfort operating Linux.
• The conviction that infrastructure is code: version-controlled, reviewed, tested, and secured.

Desirable Skills/Experience

• Depth in Azure and its native services (AKS, AI Foundry, Network Manager, Key Vault, Entra ID, Application Gateway, Firewall, Private Endpoints).
• Experience building or operating an internal developer platform or developer portal.
• Familiarity with supply chain tooling (Sigstore/cosign, Trivy, DefectDojo, or equivalent) and policy engines (Kyverno, OPA/Gatekeeper).
• Exposure to data-platform components such as a lakehouse, event streaming, or workflow orchestration.
• Exposure to safety-critical or regulated environments and the assurance discipline they require.

Essential / Desirable Traits

• You see systems end to end and resist thinking in silos.
• You translate technology into developer experience and hold several stakeholders' perspectives at once.
• You treat the platform as a product: you measure adoption and developer experience, and let that evidence, not assumption, guide what to build, harden, or retire next.
• You have learning agility, flexibility, and initiative.
• You are comfortable in an agile team and engaging directly with the developers you serve.
• You hold your convictions with humility, welcome constructive feedback, and stay resilient.