Platform Engineer / Architect — Kubernetes & OpenShift Virtualization
Tele2 Sweden AB · Kista ·
- Category
- Devops
Tele2 Sweden AB · Kista ·
Teledyne · US - Huntsville, AL
First Citizens Bank · NCSDAC-Data Center
FactFinder · Berlin, Germany
innovaccer-analytics · Noida, Uttar Pradesh, India
Platform Engineer / Architect — Kubernetes and OpenShift Virtualization
Where a workload runs should be a decision about the workload. Nothing else. We've just moved our container workloads off VMware onto upstream Kubernetes, and OpenShift Virtualization is next. We're hiring two platform engineers/architects — one for each platform — to build what developers actually touch, and to set the technical direction while doing it.
DCT
Are you ready to be at the forefront of digital innovation? Join our dynamic team at Tele2, where Digital Capabilities & Technology (DCT) is the engine behind our products and services. As the essential enabler of our commercial
ambitions, DCT brings automation and simplicity to the telecommunications industry, revolutionizing the way we connect and communicate.
Within our organization, you’ll find everything from the backbone infrastructure of technology and IT systems, serving both our external & internal customers, to advanced analytics, AI creation, and frontend development. Our team plays a vital role in ensuring reliable and premium services through delivering exceptional experiences to our end customers, both Consumer and Enterprises, all the while supporting our colleagues within Tele2.
ABOUT THE ROLE
We run workloads on-premises and in Azure and AWS, and we treat all of it as one ecosystem — somewhere a team can put a workload wherever it genuinely fits. We're not there yet; that's the work. On-premises we're building two platforms the same way — one for containers, one for VMs — sharing a GitOps approach and a single self-service front door in Backstage. The managed parts of the wider estate join the same road as we go.
We've just moved our container workloads off VMware onto upstream Kubernetes, built from open-source components we choose and integrate ourselves. Moving our virtualisation estate onto OpenShift Virtualization is the next phase, built the same way, behind the same front door.
We're hiring one person for each platform. They're two jobs rather than two versions of the same job — but they're built alongside each other, on a shared design, by people who sit together.
We treat our platforms as products: users we talk to, feedback that changes what we build, and a hand in shaping what using them feels like.
The title has both words on purpose: you set the technical direction, then you implement it. Call yourself whichever you like — how you approach the problem tells us more than the word on your CV does.
The two roles
Container platform - Kubernetes
Upstream Kubernetes and open-source components we choose and integrate ourselves, from how a cluster comes into existence to what a developer sees when they want one. At the bottom, declarative cluster lifecycle - clusters provisioned, upgraded and replaced as code. In the middle, the platform layer we assemble and run ourselves. At the top, the part developers actually touch: golden paths in Backstage and a self-service API where committing a claim to Git gets you working infrastructure, with policy gates in CI keeping it safe as it scales.
VM platform - OpenShift Virtualization
We already run OpenShift Virtualization - the work now is everything around it. A multi-cluster platform, with hub clusters managing workload clusters across sites, and a self-service API on top that turns a developer's request for a machine into a provisioned, networked, registered, backed-up VM without a ticket. Behind that API sits a Crossplane composition layer and a Go operator we wrote ourselves.
Both roles
One application covers both roles. Tell us which platform interests you more, or say you're open to either - both are useful answers.
What we're looking for
We don't count years in this stack. Much of it is new enough that everyone here is still learning it, including us. So we're looking for real depth somewhere in infrastructure, and the drive to build that same depth again in the parts you haven't met yet.
What you'll need:
What we're hoping for:
Our stack
Recognising some of this is useful. Recognising all of it isn't expected. If you've contributed to open-source infrastructure projects, we'd like to hear about it.
A few words from the manager
Hi, I'm Joel Lundgren, Manager for the Infrastructure Architecture & Design team.
We're defining what our on-premises platforms look like for the coming years — designed to live alongside public cloud, not to compete with it. Because we build them from open-source components rather than inheriting them from a vendor, their shape is genuinely ours to decide, and that's a rare thing to get your hands on.
We already run OpenShift Virtualization. The work now is everything around it — self-service a developer can actually use, integration with the systems the rest of the company depends on and moving the existing estate across without disrupting it. We have the mandate, the timing, and a container platform already running the same way to build on.
I'd much rather hire someone curious and determined who grows into this than someone who matches a list of years.
Why Tele2
Interest and application
Would you like to be a part of the Tele2s value-driven and including culture? Then hit the “apply now” button and let’s find out if we’re a match!
To ensure an inclusive and fair recruitment process, we focus on your experiences and skills. Therefore, Tele2 has chosen not to consider cover letters. Instead, we kindly ask you to answer the screening questions included in the application form.
As a step in the recruitment process, Tele2 performs a background check on final candidates.
Socket.dev · Mississauga, Canada