Engineers hiring engineers.
Most recruiters forward CVs that match keywords. We forward engineers and engineering leaders our own engineers have already interviewed, with the report to show for it.
Which of these sounds like your week?
“The résumé was perfect. The first pull request said otherwise.”
What we do
A working engineer interviews every candidate and writes a report before you meet them.
A free 30-minute call about the role. Looking for your next role instead? Send us your profile
I can't tell who's actually goodMost hiring goes wrong at the first technical round.
Recruiters can judge notice periods and salary. Whether someone can design an API, write a test plan or defend a layout is left to your team. That round is the one we take on.
Hiring on your own
- Your engineers lose days to first rounds
- Roles sit open while the roadmap waits
- Founders end up running the search
- Bad hires show up after joining
A typical agency
- CVs matched on keywords
- Nobody technical screens them
- Forty profiles, three worth a call
- Gone once the fee is paid
AlgoSmiths Talent
- A working engineer interviews every candidate
- A written report with every profile
- First profiles within days
- 3–5 people worth meeting
- One free replacement within 90 days
A CV tells you what someone has used. An interview tells you what they can do.
Every candidate comes with an interview report.
Before a profile reaches you, an engineer from our panel runs a 60-minute technical interview against the scorecard we agreed with you, then writes it up on one page.
- What we tested, so you know what was covered and what wasn't.
- Strengths and gaps, in plain words, not a score out of ten.
- A recommended level: mid, senior or lead.
- What to probe in your round, so your interview builds on ours instead of repeating it.
Candidate R.K.
Senior Backend Engineer · 60-minute technical interview
- Tested
- API design for an order service, debugging a failing integration test, and the trade-off between a SQL write and a queue.
- Strong
- Clear data modelling. Wrote tests without being asked. Explained idempotency well.
- Gaps
- Little production experience with message queues. Vague on observability.
- Level
- Senior, with confidence. Not yet staff.
- Probe next
- An incident they owned end to end, and how they would add tracing to this service.
Who we hire, and how we test them.
Engineering roles only, so the person interviewing your candidate understands the job.
Software engineers
Mid-level to principal
What they work on
Node.js, Python, Java, Go, React, Next.js, React Native and Flutter, on AWS, GCP or Azure.
What we test
Code fluency, Design, Architecture, Debugging, Technical strategy.
Site reliability engineers
Mid-level to principal
What they work on
AWS, GCP or Azure; Kubernetes and containers; Terraform; CI/CD; Prometheus, Grafana, Datadog and similar.
What we test
Systems knowledge, Reliability design, Incident response, Automation, Observability.
Machine learning engineers
Mid-level to staff / lead
What they work on
Python, PyTorch, scikit-learn, feature stores, model serving, vector databases, LLM APIs and evaluation tooling.
What we test
ML fluency, Problem framing, Evaluation, Production ML, Software engineering.
Data engineers
Mid-level to staff / lead
What they work on
SQL, Python, Spark, Airflow or Dagster, dbt, Kafka, and warehouses such as BigQuery, Snowflake and Redshift.
What we test
Data modelling, Pipelines, Data quality, Performance and cost, Working with consumers.
Security engineers
Mid-level to principal
What they work on
Application security, cloud security on AWS, GCP or Azure, identity, detection and response, and secure development.
What we test
Threat thinking, Application security, Cloud and infrastructure, Detection and response, Working with engineers.
Technical program managers
Mid-level to principal
What they work on
Multi-team launches, platform migrations, release processes, roadmaps and dependency management.
What we test
Program planning, Technical depth, Alignment, Risk and change, Process design.
Engineering managers
Engineering manager and Senior engineering manager
What they work on
Teams of roughly 5 to 15 engineers, or several teams through other managers at the senior level.
What we test
People, Delivery, Technical judgement, Team health, Partnership.
How we interview covers the qualities we judge in every engineer and how we recommend a level.
From a brief to a hire who stays.
- 01
Brief, on day one
A 30-minute call on the role, the team, the stack and what good looks like. We agree the interview scorecard before we source anyone.
- 02
First profiles within days
We start from engineers already in our pipeline and source fresh ones. A recruiter checks motivation, notice period and salary fit.
- 03
The engineer interview
An engineer from our panel runs a 60-minute technical interview against your scorecard and writes the report.
- 04
Your rounds, about two weeks
You meet 3–5 shortlisted people. We schedule your rounds and collect feedback, so final selection usually takes about two weeks.
- 05
Offer and notice period
We help with the offer and stay in touch with the candidate through the notice period, which is when most hires are lost.
- 06
The 90 days after joining
If the hire leaves or is let go for performance within 90 days, we find a replacement once, at no charge.
Hire through us, or just borrow our interviewers.
Every option uses the same engineer-led interview. Pick how much of the hiring you want us to own.
Permanent hiring
We find, interview and shortlist engineers and engineering managers for your payroll. You pay a percentage of annual CTC only when the hire joins.
- Engineer-led technical interview and written report
- First profiles within days
- No retainer, no fee if nobody joins
- One free replacement within 90 days
Contract hires
Engineers for a fixed project or a gap in the team, interviewed the same way.
- 3–12 month engagements
- Same technical interview
- Option to convert to permanent
Interviews only
You source the candidates. Our panel runs the technical round and writes the report.
- Your scorecard, our engineers
- Written report per candidate
- Frees your team's time
India EOR
We hire engineers in India and legally employ them for you, so you don't need an entity.
- Payroll
- Compliance
- Contracts
- HR administration
Rather not hire at all? The same engineers can build it for you as a dedicated pod with a Tech Lead. See AlgoSmiths development services
Who we hire for, and who we don’t.
We only take roles our own panel can interview properly. Saying no early is better than sending you the wrong people.
Built for
- Product companies and startups hiring mid-level to lead engineers
- Teams whose senior engineers are stretched thin by interviewing
- Founders who can't judge a technical candidate on their own
- Teams hiring SRE, data, ML or security engineers alongside developers
Probably not a fit
- Entry-level, campus or bulk hiring
- CxO and VP searches
- Non-technical roles
- Relocation or visa-led hiring
Straight answers to the questions hiring managers ask.
Guides from our engineers
Practical write-ups on the problems this work solves, from the AlgoSmiths blog.
- Build a Startup Tech Team on a Budget – Smart & Cost-Effective
- Technical Due Diligence for Startups: What Investors Check Before They Fund You
- Offshore Talent: Capability First, Cost Second – Strategic Outsourcing
- How to Launch a Startup Without a Tech Co-Founder (Even If You Can’t Code)
Tell us the role.
Four details and we'll come back within a working day with how we'd approach it.
No retainer. You pay only when someone joins. Or write to talent@algosmiths.com