What we test for
Typical work
- Infrastructure that already exists, imported into code without a rebuild
- Reusable modules other teams can consume safely
- Plan and apply through CI, with the review on the plan
- New environments built from the same code as production
The coding test
Import a small piece of hand-built infrastructure until a plan comes back clean, then turn it into a module another team could use with three inputs. Then we corrupt the state and ask how you would recover. Scored on the import and the recovery, not on writing resources from scratch.
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 belongs in Terraform state, and what never does?
A strong answer covers: Infrastructure yes, secrets never, because state is plaintext. Remote state with locking and encryption, access restricted the way a credential would be, and no console changes on the side to cause drift.
Someone changed something in the console. What now?
A strong answer covers: A plan shows the drift. Decide whether the change was right and codify it, or wrong and let the apply revert it. Then fix the reason: the permission that allowed it, or the missing way to do it properly.
How do you structure Terraform across several environments?
A strong answer covers: The same modules with different inputs, state separated per environment, nothing copy-pasted between folders. If staging and production are two directories that drifted apart, staging has stopped testing anything.
A plan wants to destroy and recreate a database. What do you do?
A strong answer covers: Stop. Read which attribute forces replacement, and whether a lifecycle rule, a moved block or an import is the right answer. Never apply a destroy you did not intend: in production that plan output is the last warning you get.
How do you review an infrastructure pull request?
A strong answer covers: Review the plan, not only the diff, because the diff understates the blast radius. Check what is being replaced, what is public, what has no backup, and whether the apply can be reversed.
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 Terraform engineers?
Six or more years, with state they inherited rather than only greenfield code. We ask about an import and about a recovery, which is where the experience actually shows.
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.