Senior Azure Platform​/DevOps Engineer

Senior Azure Platform / Dev Ops Engineer
About Makai

Makai uses best-in-class AI and data to solve real-world operational and strategic challenges  help businesses with enterprise automation, human-machine teaming, product design and development, and market intelligence. Until now, people have had to learn and adapt to software. Makai creates solutions that adapt to people because technology will never be 100% accurate. People are essential for all of our human-machine teaming solutions.

We build and run cloud platforms for our clients. A lot of the time that means standing up a reusable Terraform foundation and adapting it for each client and environment. You'd own these platforms: design them, build them from an empty subscription, keep them running, and act as the person who actually knows how the whole thing fits together.

This is a senior role with a lot of trust attached. The clients differ, the topologies differ, the pipelines differ. What stays constant is Azure and the expectation that you can size up an unfamiliar setup, make the right calls, and own the result.

• Stand up new platforms from scratch: network, compute, data, and the pipeline to ship to them.
• Make the architecture calls and live with them. That includes knowing when a Terraform change is a safe in-place update and when it's a destroy-and-replace you should never run blind against production.
• Run migrations that carry real risk. Move a live platform onto a new foundation, read the plan correctly, write the runbook, and have a rollback ready before you start.
• Keep platforms healthy over time: provider upgrades, drift, security, and not letting a shared foundation rot as more clients land on it.
• Work directly with the client's own Dev Ops engineers. Often they're the ones running the apply and you're advising, so you need to explain a plan, unblock a failure quickly, and be someone the engineer holding the keys trusts.

Azure experience is the hard requirement. You've built and run production Azure yourself, not just used modules someone else wrote. Specifically:

• Azure networking is where most of the work lives: VNets and subnets, private endpoints and private DNS zones, NSGs and UDRs, NAT, Application Gateway and WAF, load balancers, and hub-and-spoke / Virtual WAN.
• Terraform on Azure, with state treated as something you respect: work spaces, migrations, imports, remote backends, and the discipline not to force an apply through a lifecycle guard.
• The delivery path:
  Azure Container Registry, VM Scale Sets and cloud-init, and CI/CD with Azure Dev Ops or Git Hub.
• Azure data services:
  Postgres Flexible Server, managed Redis, Blob storage, and a real sense of their sizing, failover, and cutover risks.
• Entra  RBAC: app registrations, service principals, role assignments scoped properly across subscriptions.
• Clear writing and a level head on a live call. You can hand someone a runbook they can follow without you in the room.

• Azure certs (AZ-104, AZ-305).
• Temporal or similar workflow runtimes, and scripting (Bash, Python) for the glue.
• Past consulting or client-embedded work. You've been the outside expert before.

Small senior teams, real ownership. We'd rather have one engineer who understands a platform top to bottom than several who each own a slice.