Hire Kubernetes engineers
Our senior Kubernetes engineers design, operate and recover clusters they didn't build. Each one is tested on live infrastructure reasoning, without scaffolding: reading unfamiliar manifests, diagnosing degraded nodes and making safe rollout decisions under pressure.
01
Engineers now check AI-written manifests
AI tools now generate YAML quickly, and engineers who ship it without reading it carefully push misconfigurations into production. Most of the work has moved to checking AI output against cluster state rather than writing manifests from scratch.
02
Observability tooling moved faster than skills did
eBPF-based observability, OpenTelemetry pipelines and policy engines like Kyverno have all matured in the last two years, so engineers need to reason about signals they didn't set up. Engineers who can read an unfamiliar Grafana dashboard and correlate it with control-plane logs are more useful than those who can't.
03
Platform engineering raised the ownership bar
Kubernetes is increasingly the base for internal developer platforms, so engineers are expected to own the full lifecycle: cluster upgrades, node autoscaling, cost attribution and the on-call runbooks. That scope is wider than cluster administration used to be.
How we assess Kubernetes engineers
Every engineer works through a fundamentals assessment with AI tools switched off and a second assessment with their own agents running. For Kubernetes engineers, these criteria carry the most weight.
- Debugging
In the first assessment the engineer reads logs and events from an unfamiliar cluster with a degraded workload and must identify the root cause without being told where to look.
- AI output verification
In the second assessment the engineer uses their own agents to generate Helm values or RBAC policies and is expected to catch any misconfiguration before it would reach a real cluster.
- Judgement by risk
Across both assessments, the assessor checks whether the engineer treats a production rollout and a dev namespace change with appropriately different levels of caution.
Hiring with Miyagami
- One senior engineer, full-time, at a fixed monthly fee
- Employment, payroll and compliance included, no recruitment fee
Timeline
- Three-month minimum
- Wrong fit: we replace at our cost
What is Supabase?
Supabase is an open-source backend-as-a-service built on PostgreSQL, offering auth, storage, APIs, and real-time data without vendor lock-in.
What is Backend as a Service (BaaS)?
BaaS provides pre-built cloud infrastructure (databases, auth, storage, APIs) so teams ship apps without building or managing servers from scratch.
How to review AI-generated code
Reviewing AI-generated code changes some of what reviewers look for and keeps the rest. This entry covers both, plus the specific failure modes to check for.
Questions about hiring Kubernetes engineers
How senior are these Kubernetes engineers?
These Kubernetes engineers average 6+ years' experience, and they've shipped and maintained production systems in Kubernetes. Every one has passed both assessments, and you see both scorecards before you meet them.
How do you test Kubernetes skills?
Every engineer completes two sixty-minute assessments in a real codebase. The first assessment covers fundamentals with AI tools off: reading unfamiliar manifests, diagnosing a degraded workload and reasoning about rollout risk. In the second assessment the engineer uses their own agents, so you can see how they verify the output before it would touch a cluster.
How quickly can a Kubernetes engineer start?
You'll have a shortlist within five working days, and engineers typically reach their first commit within three weeks of that. Engagements are full-time with a three-month minimum, and everyone you meet is available on that basis.
What does a Kubernetes engineer cost?
You pay a fixed monthly fee of €5,600 to €8,000 per full-time engineer, with employment, payroll and compliance included and no recruitment fee. The pricing page compares it with the all-in cost of a senior local hire in your country. Engagements are full-time with a three-month minimum, and if a placement doesn't work out, we replace them at our cost.
Do they work in our tools or theirs?
They work in your tools. They join your incident channels, monitoring stack and CI pipelines from day one. If you don't have tooling in place yet, they can help you choose it and then run it as part of your team.
Get a shortlist within five working days
You share the roles and the stack in a short form or a thirty-minute call. Within five working days you get named senior engineers to review, each with both scorecards.
ISO 27001Certified