What we test for
Typical work
- Dockerfiles that build fast, build small, and build the same every time
- Local environments that match what production actually runs
- Image pipelines with scanning, signing and tags that mean something
- Containerising applications that were never designed for it
The coding test
Take an application with a slow, bloated Dockerfile and fix it: multi-stage, cached layers, non-root, a fraction of the size. Then make the build reproducible, so two runs produce the same image. Scored on size, on build time, and on whether it still runs.
Five interview questions you can reuse
We use questions like these in our soft-skills and technical rounds. Steal them for your own interviews.
What makes a Docker build slow, and how do you fix it?
A strong answer covers: Layer order that invalidates the cache on every code change, dependencies installed after the source is copied, a missing .dockerignore, and no cache in CI. Copy the lockfile and install before copying the rest.
Why is running as root inside a container a problem?
A strong answer covers: A container is not isolation, it is a process on a shared kernel. A root process plus a kernel escape or a mounted socket is the host. Use a non-root user, a read-only filesystem, and drop the capabilities you do not need.
How do you keep images small without breaking them?
A strong answer covers: Multi-stage builds so the toolchain never ships, a slim or distroless base, no package manager caches in the final layer, and only the artifact copied across. Then check it still runs, because distroless has no shell to debug in.
What is wrong with tagging everything latest?
A strong answer covers: You cannot tell what is running and you cannot roll back. Tag by commit SHA, pull by digest in production, and keep latest as a convenience that nothing deploys from.
How do you keep local development and production the same?
A strong answer covers: The same image, with configuration from the environment rather than from a second Dockerfile, and Compose only for the dependencies around it. Two Dockerfiles that drift apart is the bug that shows up after deploy.
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 container engineers?
Six or more years, with images they ship and maintain rather than copied from a tutorial. We ask about a build they made ten times faster and about what they took out of 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.