What we test for
Typical work
- Clusters that survive an upgrade and a node failure
- Workloads moved onto Kubernetes without a rewrite
- GitOps delivery with ArgoCD or Flux
- Autoscaling, resource limits, and the cost that follows from them
The coding test
Deploy a two-service application to a cluster: health checks, resource requests and limits, an ingress, and a rollout that can be reverted. Then we break it in a way we do not tell you about and watch how you find it. Scored on the debugging path more than on the manifests.
Five interview questions you can reuse
We use questions like these in our soft-skills and technical rounds. Steal them for your own interviews.
A pod is in CrashLoopBackOff. Walk me through it.
A strong answer covers: Describe the pod for events and the exit code, then the logs of the previous container, then work out whether it is config, a missing secret, a failing probe or an OOMKill. The events usually say it, and people skip them to go straight to the logs.
How do you set resource requests and limits?
A strong answer covers: Requests from observed usage so the scheduler places it honestly, limits above the real peak. CPU limits throttle and often hurt more than they help, and a memory limit set too low is an OOMKill at the worst moment. Measure first, then set.
How do you upgrade a cluster without downtime?
A strong answer covers: Read the deprecation notes for the APIs you use, upgrade the control plane then the nodes, drain with PodDisruptionBudgets that are actually configured, and keep more than one replica of anything that matters. Rehearse on a cluster that resembles production.
When is Kubernetes the wrong choice?
A strong answer covers: A couple of services and a small team: the cluster becomes the product. It earns its complexity with many services, several teams, or a real need for what it gives. Saying that to a client early is worth more than the engagement.
How do you keep a cluster secure?
A strong answer covers: RBAC scoped to the job instead of cluster-admin for convenience, no privileged pods, network policies that default to deny, images scanned and pinned by digest, and secrets from a real secret store rather than base64 in a manifest.
One monthly price per developer. Everything in it.
No deposit, no minimum term, no placement fee. You pay one invoice a month for each developer on your team.
Per developer, all-in. Your quote arrives by email with your exact number after you send the brief.
- Developer pay, local payroll and taxes
- Vetting: coding test, soft skills, English
- Free replacement within 90 days
- A direct line to our CEO
What changes the price
- Seniority and role. Senior engineer, tech lead or architect.
- Stack. Some stacks and niche tools cost more to staff.
- Team size. Larger teams get a better monthly rate per seat.
- White-label. Agencies reselling under their brand get partner pricing.
Terms in plain words
- First 2 weeks risk-free: if it isn't working, you don't pay for them
- Month to month, 30 days' notice to end
- No deposit and no minimum number of seats
- Want to hire the developer full-time? Buyout of 3 months' fee in year one, 2 months' after
Questions tech leads ask us
How senior are your Kubernetes engineers?
Six or more years in infrastructure, with clusters they operated and upgraded in production, not only deployed to. We ask what broke and how they found it.
Can I see the coding test results?
Yes. Every profile card carries the score and the reviewer notes.
What does it cost?
$6,900 per developer per month, all-in, and flat: the same rate whatever the stack. Your exact quote arrives by email after you send the brief.
Skip the sales rep. Talk to the CEO.
Tell us what you're building, your stack and when you need people. Three matched profiles within 48 hours, and a straight answer on whether we're the right fit.