Location: Remote
Duration of project: 9-12 months
Mode of Interview: Video
To clarify, we are looking for someone who understands networking and infrastructure for Azure, as well as DevOps best practices including IaC, Kubernetes, OS administration for Windows/Linux, cloud storage, and Security
Is this greenfield (building out a new platform) or an existing deployment that needs to grow, get more reliable, or get fixed?
We already have a proven MVP in AKS. Working on full production level support with HA. Establishing support in AWS should be pretty straightforward because the majority of the heavy platform lift has been completed. Just polishing needed.
AWS or Azure (we had discussed AWS last week but your last note said AWS or Azure).
Azure will soon be in a legacy support model, with new feature requests being handled in the new AWS offering.
EKS/AKS managed, or self-managed clusters?
EKS/AKS managed with ARGOCD for gitops, OPA to come
What's running on it: microservices, batch/data workloads, ML/AI training?
All of the above, with fewer ETL pipelines, more static endpoints and ML/AI matching.
How many clusters, nodes, and namespaces are we talking about? "At scale" can mean different things to different clients.
AKS 4 current clusters, 2 clusters are old and will be moved into new platform infrastucture.
AWS 2 per region with support for 2 regions to start.
What is the DevOps infrastructure around these containers that will be used to build and deploy to Kubernetes?
ArgoCD, ACR/ECR, Azure git and github
Never miss an opportunity! Create an alert based on the job you applied for.
