Technology recruitment. Vetted by Engineers.
Software, cloud, data and AI, cybersecurity, product and IT. Every candidate we introduce has been assessed against your role before you meet them.
- Software Engineering
- Cloud, Platform & DevOps
- Data & AI
- Cybersecurity
- Quality Engineering
- Product & Delivery
- IT & Service Operations
- Leadership & Architecture
Every part of the technology function.
Eight disciplines, permanent and contract, from first hires to technology leadership.
Engineers who build and maintain the products a business runs on, from a first backend hire to the lead who sets technical direction.
- Software Engineers
- Backend Engineers
- Frontend Engineers
- Full Stack Developers
- Mobile Developers
- Technical Leads
- Software Architects
The people who keep systems running, deployable and affordable: infrastructure as code, pipelines, reliability, and the platforms other engineers build on.
- Cloud Engineers
- Platform Engineers
- DevOps Engineers
- Site Reliability Engineers
- Infrastructure Engineers
- Systems Engineers
- Network Engineers
- Cloud Architects
From pipelines and warehouses to models in production. We separate people who have shipped data products from people who have only experimented with them.
- Data Engineers
- Data Analysts
- Data Scientists
- Analytics Engineers
- Machine Learning Engineers
- AI Engineers
- BI Developers
- Data Architects
Defensive, engineering and governance roles. Assessment is matched to the job: a SOC analyst and a GRC specialist need very different things.
- Cybersecurity Engineers
- Security Analysts
- SOC Analysts
- Cloud Security Engineers
- Application Security Engineers
- Security Architects
- GRC Specialists
Where Boolean began, and where our own hands-on experience runs deepest: automation frameworks, test strategy, and quality built into delivery rather than bolted on.
- SDETs
- QA Automation Engineers
- Quality Engineers
- Software Test Engineers
- Performance Engineers
- Test Architects
- QA Leads
- Heads of Quality Engineering
The roles that decide what gets built and make sure it ships. We assess judgement and how they work with engineers, not familiarity with a particular framework.
- Product Managers
- Product Owners
- Business Analysts
- Technical Business Analysts
- Delivery Managers
- Technical Project Managers
- Scrum Masters
- Engineering Programme Managers
The people who keep an organisation’s technology working day to day, and the managers who run those services.
- IT Support Engineers
- Systems Administrators
- IT Operations Specialists
- Application Support Engineers
- Service Delivery Managers
- IT Managers
Senior hires shape teams and systems for years. We look at the decisions they have made, the teams they have built, and how they handled what went wrong.
- Engineering Managers
- Heads of Engineering
- Directors of Engineering
- Technical Architects
- Solution Architects
- Enterprise Architects
- CTOs and technology leaders
Why Boolean
Fewer CVs. Better evidence.
- 01
We understand the work.
Founded by technology professionals from software delivery and test automation, so we read your brief the way your team does.
- 02
Assessed before you meet them.
Every candidate is assessed against your role first. You see fewer CVs, and more of the right ones.
- 03
Evidence, not adjectives.
Each introduction comes with a Technical Audit Record: what we tested, what we found, and what to probe at interview.
The Technical Audit Record
The evidence behind every introduction.
A structured record, written by the assessor, for every shortlisted candidate. The format stays the same; the assessment changes with the role.
Illustrative samples. Candidates, briefs and findings are fictional.
Technical Audit RecordBoolean Group
TAR-SAMPLE-PE
Illustrative sample
1Summary
Hands-on platform engineer who could explain the structure and trade-offs of infrastructure they had built, not just the tools involved. Recommended for interview.
2Relevant experience
Two platform roles, most recently in a team of six supporting around forty product engineers. Led a move from hand-built environments to Terraform modules. Shared an on-call rota.
3Capability assessment
| Area | Finding | Evidence noted |
|---|---|---|
| Infrastructure as code | Demonstrated | Walked through their module structure and state management. Described a drift problem and how it was resolved. |
| Kubernetes operations | Demonstrated | Comfortable with cluster upgrades, resource limits and debugging failed deployments. |
| CI/CD and release | Partly demonstrated | Solid pipeline design. Less exposure to progressive delivery such as canary releases and feature flags. |
| Incidents and observability | Demonstrated | Gave a clear account of a production incident, their part in it, and what changed afterwards. |
| Cloud cost management | Not assessed | Not covered. Worth exploring at interview. |
4Working style
Methodical and clear. Prefers a short written design note before large changes. Asked useful questions about where the team’s ownership starts and stops.
5Alignment to the role
Close match on stack and scale. On-call expectations were discussed and accepted.
6Logistics
Notice: One month
Location: Hybrid, London
Salary: Shared with client separately
7Risks and limitations
Limited multi-region experience, which the brief lists as desirable. Has not managed people.
Assessor sign-offVetted by Engineers.
Illustrative sample. The candidate, brief and findings are fictional and show the format only.
Technical Audit RecordBoolean Group
TAR-SAMPLE-BE
Illustrative sample
1Summary
Capable backend engineer with good habits and clear reasoning, strongest on API and data design. Recommended for interview at mid to senior level.
2Relevant experience
Four years across two product companies, mainly Python services on PostgreSQL. Built and owned a billing service end to end.
3Capability assessment
| Area | Finding | Evidence noted |
|---|---|---|
| API design | Demonstrated | Designed a versioned API during the exercise and justified their choices on pagination and error handling. |
| Data modelling | Demonstrated | Produced a sensible schema and explained where they would denormalise for read performance. |
| Testing practice | Demonstrated | Writes tests by default. Clear on where unit and integration tests each earn their keep. |
| Messaging and concurrency | Partly demonstrated | Has used queues in production. Reasoning about ordering and idempotency was partly complete. |
| System design at scale | Not assessed | Not assessed at senior depth. Flagged for the client’s own design interview. |
4Working style
Collaborative, thinks aloud, and is comfortable saying when they do not know something. Prefers small, frequent releases.
5Alignment to the role
Strong on language, database and remote working. Event-driven experience is lighter than the brief describes.
6Logistics
Notice: Three months, negotiable
Location: Remote, UK
Salary: Shared with client separately
7Risks and limitations
Notice period runs past the client’s preferred start date. Event-driven work would be a step up.
Assessor sign-offVetted by Engineers.
Illustrative sample. The candidate, brief and findings are fictional and show the format only.
Technical Audit RecordBoolean Group
TAR-SAMPLE-SA
Illustrative sample
1Summary
Analyst with a careful, evidence-led approach to investigation. Ready for a level-two role with support on leading incidents.
2Relevant experience
Two years in a managed security provider’s SOC on a shift rota, triaging alerts across several client environments. Some threat-hunting work.
3Capability assessment
| Area | Finding | Evidence noted |
|---|---|---|
| Alert triage | Demonstrated | Worked through sample alerts in a sensible order and separated noise from likely incidents. |
| Log analysis | Demonstrated | Wrote reasonable queries to answer an investigation question and explained what each one was for. |
| Incident handling | Partly demonstrated | Understands the incident lifecycle. Has supported containment but not led it. |
| Threat knowledge | Demonstrated | Mapped observed activity to common attacker techniques without prompting. |
| Cloud security | Not assessed | Outside the core requirements of this role, so not assessed. |
4Working style
Calm under pressure, careful with evidence, writes clear notes. Would do well in a team with structured mentoring.
5Alignment to the role
Matches the SIEM, the rota and the level. Has worked shifts before and understands the commitment.
6Logistics
Notice: One month
Location: On-site, Manchester
Salary: Shared with client separately
7Risks and limitations
Has not yet led an incident from detection to closure. Would need support to step into that role.
Assessor sign-offVetted by Engineers.
Illustrative sample. The candidate, brief and findings are fictional and show the format only.
Technical Audit RecordBoolean Group
TAR-SAMPLE-PM
Illustrative sample
1Summary
Product manager with a strong working relationship with engineers and a disciplined approach to prioritisation. Recommended for interview.
2Relevant experience
Three years as product manager for internal developer tools, previously a business analyst. At ease with technical stakeholders.
3Capability assessment
| Area | Finding | Evidence noted |
|---|---|---|
| Problem framing | Demonstrated | Narrowed an ambiguous case study to a testable problem before proposing any solution. |
| Prioritisation | Demonstrated | Made trade-offs explicit and said what they would deliberately not build, and why. |
| Working with engineering | Demonstrated | Gave specific examples of negotiating scope. Treats technical debt as a product decision. |
| Metrics and outcomes | Partly demonstrated | Clear on outcome measures. Less experience setting up measurement from scratch. |
| Pricing and commercials | Not assessed | Not part of this brief, so not assessed. |
4Working style
Structured and direct. Writes concise product briefs and listens before proposing.
5Alignment to the role
A good fit for a platform team whose users are engineers. Less exposure to external customer research.
6Logistics
Notice: Two months
Location: Hybrid, Bristol
Salary: Shared with client separately
7Risks and limitations
Limited external customer discovery. The client should test this if it is central to the role.
Assessor sign-offVetted by Engineers.
Illustrative sample. The candidate, brief and findings are fictional and show the format only.
How we work.
Our approach in detailBrief
The role, the team, and what good looks like.
Search
People with directly relevant experience.
Assess
Structured and specific to your role.
Record
A Technical Audit Record for each candidate.
Introduce
A short shortlist, ready for interview.
Tell us what you’re hiring for.
A few lines is enough to start. We reply within two working days.
Prefer email? team@booleangroup.co.uk
Looking for a role? Register with us