DevOps Engineer (CI/CD, Automation, Cloud Migration)

Every engineering team has a route from a commit to production. The difference between a good one and a bad one is whether anybody owns it. This role owns it.

You will build the pipelines and the automation that make a release a routine, unremarkable event, and you will keep what ships monitored, patched and defensible afterwards. The work reaches further than tooling: there is real server and network infrastructure underneath, and a cloud migration ahead that you will help sequence rather than simply execute.

What you’ll do

• Build and maintain the infrastructure and software that carry code through a CI/CD pipeline.
• Define how development, test, release, update and support actually run — the processes DevOps operations depend on, not just the scripts.
• Automate the repeatable work out of daily operations.
• Monitor and troubleshoot performance, availability and security, and dig into what the dashboards are not telling you.
• Work alongside the security team to identify and deploy cybersecurity measures, with vulnerability assessment and risk management as a standing habit rather than an annual exercise.
• Run incident management and root cause analysis properly — restore the service, then remove the cause.
• Write up the technical detail of the CI/CD solutions you implement, so whoever inherits them can work on them.
• Design systems with cross-functional teams so that what gets built answers a real business requirement.
• Keep a hand on the server layer as well: installing, configuring, validating, maintaining, monitoring and tuning server hardware and operational software with the rest of the infrastructure group.
• Pick up network and server problems that pass the first line, including planned upgrade windows and the occasional call that will not wait for morning.
• Help plan the roadmap for infrastructure renewal and the move to cloud.
• Mentor the engineers around you, and hold DevOps practice to something applied rather than quoted.
• Keep track of where the tooling is going, and pull in what will make the systems more capable, more efficient or harder to knock over.

What you’ll need

• You have built and run CI/CD pipelines yourself, along with the infrastructure they sit on.
• Automation is your default answer to repetition — you would rather spend a day scripting a task than keep doing it by hand.
• You are at home on servers and networks: standing them up, keeping them healthy, and finding the fault when they are not.
• You treat security as part of how something is built, not a review at the end, and you have done real vulnerability and risk work.
• You can run an incident calmly and then do the root cause analysis honestly.
• You document as you go, in a way somebody else can pick up.
• You can hold a technical conversation with developers, security and infrastructure people in the same week, and you want to bring newer engineers on.
• You are willing to take planned upgrade windows and genuine emergencies outside office hours as part of the job.

Nice to have

• You have moved workloads to cloud before, and have a view on what should move first and what should not move at all.
• You have helped shape an infrastructure renewal plan, not only delivered one somebody else drew up.
• A track record of growing other engineers.

What’s on offer

• The delivery pipeline end to end, as your responsibility rather than one stage of somebody else’s.
• Both halves of modern DevOps — pipelines and automation, and the servers and networks they actually run on.
• A real say in the cloud migration and the infrastructure roadmap, at the point where the decisions are still open.
• Mentoring counted as part of the job rather than something you fit around it.

This is a permanent, full-time position, worked on site in Cape Town.