01
The re-screening tax
Kotlin on a CV could mean years of native Android or a few months of tutorials. Telling them apart takes a mobile engineer, so every CV comes to you for a second read, and the gaps show up in your interview.
Kotlin developer recruitmentClients in the UK, Europe and USA
The CV says Kotlin. Does their app survive a dropped device?
Android depth doesn’t show on a CV. A mobile developer reads every one before you do, so you only interview candidates who understand the platform and the devices your app talks to.
Where your hiring time goes
02
The CV stopped being evidence
- The CV saysKotlin, Android
- It can’t tell youWhether they can reason through lifecycle recreation, coroutines, state and memory behaviour.
- The CV saysBluetooth, IoT, MQTT
- It can’t tell youWhat their app does when a device disappears or sends incomplete data.
- The CV saysAppium, Sentry
- It can’t tell youWhether they can diagnose a production-only crash from logs, traces and reproducible state.
If you run hiring for engineering
You need CVs that pass engineering’s interview, so you can send a shortlist it trusts. An engineer reads every CV before it reaches you. Fewer CVs, but better ones.
58%
of HR and recruitment leads who use agencies say the main reason engineering rejects agency candidates is that the CV looked good, but the person couldn’t do the job.
What the CV can’t tell you, and our interview does
A developer or CTO who works in the stack interviews every candidate. Each of these is a question you would otherwise only answer in your own interview.
Android fundamentals
Whether they can reason through lifecycle recreation, coroutines, state and memory behaviour, and keep platform concerns testable.
Connected products
How they handle scanning, pairing, permissions, reconnect logic and protocol state when devices disappear or send incomplete data.
Quality and diagnosis
How they divide coverage across unit, integration and device tests, and diagnose a production-only crash using logs, traces and reproducible state.
What every shortlisted candidate has to show
Knows what Android is doing
They can explain what the platform does for them and how they would investigate a device-specific failure without copying fixes from an AI assistant.
Uses AI with engineering discipline
They can show how they check generated code and tests against real devices, and stay accountable for each release.
Honest about platform gaps
They say which devices, integrations and Android versions they have shipped against, and where they would need support.
How we take the screening off your desk
We recruit Kotlin developers for Android applications, including roles involving Bluetooth and connected products. A mobile developer screens every candidate on platform fundamentals, architecture, networking, testing, release quality and device integration.
Either way you get about 3 to 5 screened CVs a week, per role.
Route 1: we screen, you run the deep interview
We do
- Source candidates for the role
- A technical screen of every candidate, run by a developer or CTO who works in your stack
- A CTO approves every CV before it reaches you
You do
- Run the deep technical interview with the shortlist
- Make the offer
Route 2: we run the deep interview too
We do
- Everything in Route 1, including the technical screen of every candidate
- A 1.5 to 2 hour live-coding, architecture and implementation interview with your final candidates
- A written assessment of each candidate after the interview
You do
- Meet the candidates who passed
- Make the offer
Teams we have hired for
What clients say
“Metamindz helped us recruit our now CTO, reviewing CVs as they came in and then putting the CTO through a thorough 90-minute live 360 technical test. Feedback from our now CTO of the test was glowing and comms from Metamindz throughout the entire process were excellent. Highly recommend!”
Rupert Boddington
Co-Founder, Pockla
“Worked with Lev and Max. We worked with MetaMindz to help us interview and assess software engineering candidates. They were professional and great from the outset and throughout, great speed too. Would 100% recommend and we will be working with them again.”
Alexander Bushe
CEO, Fuller Focus
“We found it really easy working with Lev and the team to hire for our lead developer role and despite it still being early days, our new hire is making an impact already!” source
Billy Whiffen
Google review
What it costs
£5,000
Fixed fee for your first role
15% to 17%
Commission on each further hire
Included
- Sourcing and screening
- A technical screen of every candidate by a developer or CTO
- A CTO approves every CV before you see it
- About 3 to 5 screened CVs a week, per role
- No exclusivity required
- A 3 to 6 month guarantee, depending on seniority
Optional extra
Deep technical interview (Route 2)£300 an hour
A 1.5 to 2 hour live-coding and technical grilling session per final candidate.
All fees exclude VAT.
Tell us about the roleFrequently Asked Questions
Yes. We recruit Kotlin developers for native Android roles and assess the platform knowledge required by the application.
Yes. Our recruitment experience includes mobile roles involving Bluetooth and connected-product integrations.
The assessment can cover Android lifecycle, application architecture, networking, testing, performance and device integration.
Looking to hire?
Give us a few details about the role and your hiring plans. We'll assess your needs and get back to you with a practical next step.
Related technical recruitment
View all technical recruitment expertiseTechnologies in briefs we have recruited for
Listed for reference. We use these to scope the brief with you. A keyword on a CV is where screening starts, and the interview decides whether the candidate can do the work.
Android development
- Kotlin
- Android
- Mobile application architecture
Connected products
- Bluetooth (BLE)
- IoT
- MQTT
Quality and integration
- RESTful APIs
- Unit testing
- Appium
- Sentry
Soft skills and working style
- Product empathy
- Patient debugging
- Release discipline
- Cross-platform thinking
- Calm communication
Teams usually bring us in for: A native Android application team. A connected-device mobile product. A team moving from cross-platform to deeper native capability.