Summary
✨ AI‑Generated
Join a Platform team as a Junior DevOps Engineer and grow from maintaining tooling, pipelines, and observability toward safely owning environments. You will work with Jenkins, Docker, monitoring dashboards, alerts, and scripting while receiving close mentorship and learning how changes move from pull request to production.
Highlights
Structured entry-level DevOps opportunity with close mentorship and a gradual path toward owning environments. The role provides hands-on experience in CI/CD, containers, observability, automation, and production delivery.
Description
About the role
You'll join the Platform team as our junior DevOps engineer.
You will not be handed the production estate on day one.
You'll start on tooling, pipelines and observability under close mentorship, and grow into owning environments as your judgement develops.
The goal for your first year is that you can safely take a change from a pull request to production and explain exactly what happened at every step.
This is a good fit if you like understanding how systems behave — not just how they're supposed to.
What you'll do
· Maintain and extend CI/CD pipelines in Jenkins: build, test, container image publishing, and deployment to our non-production environments.
· Write and review Dockerfiles and container configuration; help keep image sizes and build times sensible.
· Build and tune dashboards and alerts in [Grafana / Azure Monitor / your stack] so problems are visible before customers report them.
· Write scripts and small tools (Bash, PowerShell or Python) to remove repetitive manual work.
· Keep runbooks and environment documentation accurate — including the boring parts.
· Follow our access, secrets and change-control practices, and speak up when something looks unsafe.
What we're looking for
Essential
· Comfortable on the Linux command line: files and permissions, processes, logs, networking basics (DNS, ports, TLS at a conceptual level).
· Scripting ability in at least one of Bash, Python or PowerShell.
· A basic grasp of containers: what an image is, how it differs from a virtual machine, how to run and inspect one.
· Genuine curiosity and a habit of reading error messages properly before asking for help.
We're open to graduates, career changers and self-taught engineers.
If you've built and broken things in a home lab and can talk us through what you learned, that counts.
Desirable (we'll teach the rest)
· Any exposure to a cloud platform — Azure preferred, but AWS or GCP experience transfers well.
· Familiarity with Kubernetes concepts (pods, deployments, services), even if only from a local cluster.
· Any contact with infrastructure as code — Terraform, Bicep, CloudFormation or Ansible.
· Exposure to message brokers (Kafka) and to SQL databases.
Attributes that matter here
· Care about blast radius.
Ask "what breaks if this goes wrong?" before you run the command.
· Honest about not knowing.
We would much rather you ask than guess in production.
· Bias toward automation.
If you've done it manually three times, script it.
· Comfortable with ambiguity, but willing to escalate rather than improvise on anything customer-facing.
