What we test for
Typical work
- Infrastructure as code, for new accounts and for ones built by hand
- Migrations into AWS, and off consoles nobody can reproduce
- Account, network and IAM structure that passes a security review
- Getting the bill down without taking the service down
The coding test
Build the AWS side of a small service: network, compute, database, and the IAM that lets exactly those three talk and nothing else. All in code, with a cost estimate. Then we ask what you would change if traffic went up ten times, and what that would cost.
Five interview questions you can reuse
We use questions like these in our soft-skills and technical rounds. Steal them for your own interviews.
How do you give a service least-privilege access on AWS?
A strong answer covers: A role per service, assumed by the workload rather than long-lived keys, with a policy scoped to the resources it actually touches and short-lived credentials. Then read CloudTrail for what it really calls instead of guessing from the docs.
ECS, EKS or Lambda for a new service?
A strong answer covers: Lambda for spiky, event-driven work with short requests. ECS when you want containers without operating a cluster. EKS when Kubernetes is already in the building or you need what it gives. Who will operate it matters more than the benchmark.
The bill doubled this month. How do you find out why?
A strong answer covers: Cost Explorer grouped by tag and service, then the usage type underneath. It is usually data transfer, idle non-production, oversized instances, or logs nobody set a retention on. Tagging has to exist before the surprise, not after it.
What never goes in a public subnet?
A strong answer covers: Databases, internal services, anything holding state. The public subnet gets the load balancer and the NAT; everything else sits private with egress through the NAT, and security groups reference each other instead of CIDR ranges.
How do you make an account recoverable after someone deletes the wrong thing?
A strong answer covers: Everything in code so it can be rebuilt, backups proven by restoring them rather than by existing, deletion protection on what cannot be rebuilt, and separate accounts so a mistake in one does not reach production.
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 AWS engineers?
Six or more years, with production accounts they owned rather than consoles they clicked through. We ask about the incident and about the invoice, because both tell you more than a certificate does.
Do they hold AWS certifications?
Some do, and we do not select on it. The coding test is a real account build scored by a reviewer, which tells us more than an exam.
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.