Engineers in the room
Not sure where to start?
Tell us about the role, the team or the capability you need. We will talk it through and suggest the right approach.
Hire for the work, not the keywords.
Recruitment, technical assessment and training, each shaped around your team.
01 · Recruitment
Recruitment across technology.
Permanent
People who will grow with your team
From a first junior hire to senior specialists and technical leaders.
Discuss a permanent hireContract
Capacity for projects and teams
For a project, a delivery peak or a specialist gap. Terms are agreed with you for each engagement.
Discuss a contract hire
A global network
CoderCo-trained engineers and experienced professionals from the wider market.
Disciplines
- Software engineering
- Platform and DevOps
- Cloud and infrastructure
- Site reliability
- Data engineering
- Machine learning
- Security
- Quality and test
- Engineering leadership
Every level
- Junior
- Mid-level
- Senior
- Lead and Principal
- Head of and Director
02 · Technical assessments
Interviews led by engineers.
Our lead and Principal Engineers interview against the real role, alongside our recruitment or for candidates you have found. Topics are shaped with you.
Discuss an assessment Hiring workspace
Illustrative example Role brief
Platform Engineer
Requirements
- Kubernetes in production Core
- Terraform and IaC Core
- AWS networking Core
- CI/CD design Useful
- Observability Useful
Hiring stages
- Brief
- Search
- Technical interview
- Introductions
- Offer
Technical assessment areas
Led by a Principal Engineer- Running Kubernetes “Talk us through a rollout that went wrong.”
- Infrastructure as code “How did you structure state across environments?”
- Reliability “Which alert would you delete first, and why?”
Evidence we look for
- Project discussion A platform they built or ran
- Technical decisions Trade-offs in cluster and IaC design
- Problem-solving How they diagnose an incident
Role brief
Backend Engineer
Requirements
- API design Core
- Relational databases Core
- Automated testing Core
- Event-driven systems Useful
- Cloud deployment Useful
Hiring stages
- Brief
- Search
- Technical interview
- Introductions
- Offer
Technical assessment areas
Led by a Principal Engineer- API design “How did you change an API others depended on?”
- Data “Walk us through a slow query you fixed.”
- Testing “What do you test at the boundaries?”
Evidence we look for
- Project discussion A service they designed and shipped
- Technical decisions Interface and data-model choices
- Problem-solving Debugging under real constraints
Role brief
ML Engineer
Requirements
- Python Core
- Model deployment Core
- ML pipelines Core
- Model monitoring Useful
- Kubernetes Useful
Hiring stages
- Brief
- Search
- Technical interview
- Introductions
- Offer
Technical assessment areas
Led by a Principal Engineer- Into production “How did a model get from notebook to production?”
- Monitoring “How would you know a model has drifted?”
- Reproducibility “Apart from code, what did you version?”
Evidence we look for
- Project discussion A model they took to production
- Technical decisions Pipeline and tooling choices
- Problem-solving Handling drift or bad data
Role brief
Engineering Lead
Requirements
- System design Core
- Delivery leadership Core
- Mentoring engineers Core
- Stakeholder communication Useful
- Hiring experience Useful
Hiring stages
- Brief
- Search
- Technical interview
- Introductions
- Offer
Technical assessment areas
Led by a Principal Engineer- Decisions “Tell us about a design you took through review.”
- Delivery “When did you flag a delivery risk early?”
- Leadership “Line manager, technical lead or both?”
Evidence we look for
- Project discussion A system they led end to end
- Technical decisions Architecture and prioritisation
- Problem-solving Unblocking a team under pressure
03 · Training
Your stack. Your training.
Bespoke company training
Practical training for your engineers, shaped around your tools, gaps and goals.
Training aligned to hiring
Where a capability is hard to hire, we can discuss developing engineers against your stack.
Training programme
Illustrative example Example focus
Your stack
- Kubernetes
- Terraform
- Helm
- GitHub Actions
Built around the tools your team already uses.
Modules
- 01 Containers and Kubernetes fundamentals
- 02 Infrastructure as code with Terraform
- 03 Delivery pipelines and GitOps
- 04 Running services in production
Practical labs
- Deploy a service with Helm Rollout, rollback and config
- Build a reusable Terraform module Inputs, state and review
Programme progression
Scoped with you: content, depth and format
- Foundations
- Build
- Operate
- Capstone
Your stack
- AWS
- ECS
- Terraform
- CloudWatch
Built around the tools your team already uses.
Modules
- 01 Core AWS services and networking
- 02 Identity and access done properly
- 03 Containers on ECS
- 04 Monitoring and cost awareness
Practical labs
- Ship a container to ECS Networking, IAM and logs
- Set up useful alarms Signals that help teams act
Programme progression
Scoped with you: content, depth and format
- Foundations
- Build
- Operate
- Capstone
Your stack
- Python
- Docker
- MLflow
- Kubernetes
Built around the tools your team already uses.
Modules
- 01 Reproducible ML environments
- 02 Packaging and serving models
- 03 ML pipelines and experiment tracking
- 04 Monitoring models in production
Practical labs
- Serve a model behind an API Package, deploy and test
- Detect drift on live data Metrics and alerting
Programme progression
Scoped with you: content, depth and format
- Foundations
- Build
- Operate
- Capstone
04 · Process
From brief to follow-through.
Timings depend on the role. We agree them with you at the start.
-
Step 1 of 6
Understand the brief
The business, the team and why the hire matters now.
-
Step 2 of 6
Define success
With our engineers, we agree the technical requirements and what good looks like.
-
Step 3 of 6
Search and assess
Across our network and the wider market, against those requirements.
-
Step 4 of 6
Considered introductions
A focused set of candidates, each with a note on why they fit.
-
Step 5 of 6
Interviews and offer
We coordinate, gather feedback and keep everyone informed.
-
Step 6 of 6
Follow-through
We stay in touch after the start date to pick up issues early.
05 · Why Deployd
Traditional recruitment, and us.
Traditional recruitment starts with a CV. We start with the work, and we can test for it.
| Capability | Traditional recruitment | Deployd |
|---|---|---|
| Both deliver | ||
| Permanent and contract hiring | Yes | Yes |
| Sourcing and shortlisting candidates | Yes | Yes |
| Coordinating interviews and managing offers | Yes | Yes |
| Guidance on the market and the shape of the role | Yes | Yes |
| Only Deployd delivers | ||
| Technical interviews led by Principal Engineers | No | Yes |
| The brief written with an engineer in the room | No | Yes |
| Candidates assessed against the technical requirement, not the keywords on a CV | No | Yes |
| Technical assessment of candidates you have sourced yourself | No | Yes |
| Access to the CoderCo community alongside the wider market | No | Yes |
| Training to build the capability in your team instead of hiring for it | No | Yes |
06 · Questions
Frequently asked.
If what you need is not here, ask us directly.
-
What roles do you recruit for?
Technology roles across engineering, platform and DevOps, cloud and infrastructure, site reliability, data, machine learning, security, quality and engineering leadership, from junior through to Head of and Director level.
-
Do you work on permanent or contract roles?
Both. Permanent for people who will grow with your team, contract for a project, a delivery peak or a specialist gap. Contract terms are agreed with you for each engagement.
-
Who runs the technical interviews?
Our Principal Engineers, not recruiters working from a script. They agree the technical requirements with you first, then interview against them and tell you what they found.
-
Can you assess candidates we have already sourced?
Yes. You can bring us candidates from your own pipeline and we will run the technical interview, whether or not we introduced them.
-
Where do your candidates come from?
Engineers trained through the CoderCo community, and experienced professionals from the wider market. We search both rather than relying on one pool.
-
Which locations do you cover?
The UK, Europe and the GCC.
-
How long does a search take?
It depends on the role, the market and how quickly feedback comes back. We agree expected timings with you at the start rather than promising a number up front.
-
We would rather develop our own team than hire. Can you help?
Yes. We build training around your stack and the capability you want in the team. It is often the better answer when the gap is a skill rather than a headcount.