Our client is looking to accelerate their “splitting up the monolith” when it comes to CI/CD pipelines. They are a huge enterprise with many teams, projects, and moving parts.
They are looking for someone who has been there, done that, when it comes to creating scalable, modular, and reusable CI/CD pipelines and patterns.
You’ll be working across hundreds to thousands of pipelines, so this is not a one off migration. The focus is on reusable patterns, templated workflows, and scripted migrations that can be applied consistently across teams and services.
About the role
The organization is in a transition period, both for their approach to CI/CD (Splitting up the Mono Repo), and the underlying technologies (Bitbucket to Github).
This contract will have you migrating CI/CD, breaking up those huge “one size fits all” pipelines into smaller ones where appropriate, and even identifying where code re-use could be of help. It’s YAML, it’s Python ETL scripts, it’s Terraform, it’s Kubernetes, it’s Helm charts. All the good stuff! They just need someone who has been there, done that!
The contract is for an initial 3 months but very much could be extended as the work progresses. You certainly won’t be showing up on your first day with nothing to do!
What you will bring
You could have that “Senior Devops” line already on your CV, or you might be coming from a more traditional cloud engineer/software developer background. The specific role title doesn’t matter, what does matter is that you’ve been there and done that.
The core role will revolve around setting up a bulletproof CI/CD pipeline system, so being an expert at code isn’t necessarily needed. But the chosen “scripting” language is Python, so any experience with Python is highly advantageous.
The ideal candidate will have a great attitude and never say “that’s not my job”.
You will need all/most/able-to-fake-it of :