What we test for
Typical work
- Infrastructure as code on AWS
- CI/CD pipelines the team actually trusts
- Containers and orchestration with Docker and Kubernetes
- Monitoring, alerting and incident response
The coding test
Take a small service and give it a reproducible deploy: a Dockerfile, infrastructure in Terraform, a pipeline that runs tests and can roll back, and the one alert you would set first. Scored on reproducibility, least privilege and what they choose to monitor.
Inside DevOps
The ones people search for by name get a page of their own, with their own coding test and interview questions.
Platform engineering
Internal platforms, golden paths and self-service environments teams actually use.
See the page →Site reliability engineering
SLOs, on-call people can survive, and postmortems that change something.
See the page →AWS
Accounts, networks and IAM in code, built to pass a security review and a budget.
See the page →Kubernetes
Clusters that survive an upgrade, GitOps delivery, and debugging when it misbehaves.
See the page →Terraform
Infrastructure in code, imports of what already exists, and modules teams reuse.
See the page →Docker and containers
Reproducible builds, small images, and local environments that match production.
See the page →Five interview questions you can reuse
We use questions like these in our soft-skills and technical rounds. Steal them for your own interviews.
You are the only ops person on a team of eight developers. What do you fix first?
A strong answer covers: Whatever is blocking releases or waking people up, which is almost always the deploy path. Make it repeatable and reversible before anything else, then write it down so you stop being the only person who can run it.
A pipeline takes 40 minutes. How do you cut it down?
A strong answer covers: Measure each stage first, cache dependencies, run tests in parallel, and move the slow checks off the critical path.
How do you set up environments for a team that has none?
A strong answer covers: The same code and the same images everywhere, configuration from the environment, data shaped like production without being production, and a way to create one without asking you. A snowflake staging is where the bugs hide.
What do you automate first, and what do you leave manual?
A strong answer covers: Automate what is frequent, error-prone or blocking. Leave manual what is rare and genuinely needs judgement, but write the runbook anyway. Automating something nobody understands yet only makes the outage harder to read.
How do you hand infrastructure over to the team that has to run it?
A strong answer covers: Code they can read, runbooks for the three things that break, alerts that already have owners, and a session where they do a deploy and a rollback while you watch. If the handover is a document, it did not happen.
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 DevOps developers?
6+ years of professional DevOps work, with recent production experience.
Can I see the coding test results?
Yes. Every profile card includes the score and the reviewer's 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.