Recruitr.
Proof of skill, not proof of resume

Hire developers who actually wrote the code.

Recruitr reads a candidate's real repositories, checks they understand their own code, and hands you a ranked shortlist, with the file and line behind every skill.

See how it works

Free for candidates · Free for recruiters during our pilot

Recruitr · sample profile
AR
Open to work
642
Recruitr score
Elite

Asha Rao

Backend engineer, Node.js and PostgreSQL

B.Tech Computer Engineering · Year 3 · Pune, Maharashtra

GitHub verifiedLeetCode verified
Skill report

From verified code and coding accounts. Recruiters see this.

Dev score
712
DSA score
418
Archetype
Backend
Code review

Well-structured REST services with consistent error handling and integration tests. Queue workers lack retry limits, and CI runs only the unit tests.

Verified skills
  • Express Framework
    shop-api/src/server.ts · line 12
  • PostgreSQL Database
    shop-api/src/db.ts · line 4
Code walkthrough
82/ 100Strong

Answered 4 timed questions about their own code. No integrity concerns.

Profile strength
88%
  • Headline and bio
  • GitHub and LeetCode verified
  • Code walkthrough completed
What Recruitr is

Verified proof that a developer wrote, and understands, their code.

The problem

Resumes and GitHub profiles are easy to inflate. Recruiters can't tell who wrote the code, and engineers lose weeks screening applicants.

What we do

We read a candidate's real repositories, ask them to explain specific lines of their own code, and score the evidence. Every skill points to the file and line behind it.

The result

A ranked shortlist a recruiter can defend, a score candidates can understand, and a fairer way in for people without a famous name or degree.

How it works

From a GitHub link to a shortlist.

  1. 01

    Prove the accounts are yours

    Candidates sign in with GitHub and verify LeetCode with a one-time token. One GitHub account can back only one profile.

  2. 02

    We read the work

    Up to eight significant repositories are read in depth: structure, tests, who wrote the commits, and real source files. Every skill keeps the file and line it came from.

  3. 03

    They explain their own code

    Timed questions about specific lines in their repos, with pasting disabled. Odd patterns are flagged for a person to review, never auto-rejected.

  4. 04

    You hire from evidence

    Search in plain English, open any skill to see the code behind it, and run the interview with a kit of questions about their own work.

The product

Every skill links to a line of code.

Skills come from imports and real API usage, not from a bio. Open one and you land on the exact file in the candidate's repository.

1   import express from 'express';
2   import { Pool } from 'pg';
3    
4   app.get('/api/orders', async (req, res) => {
5     const rows = await pool.query(SELECT_ORDERS);
6     res.json(rows);
7   });
  • Expressline 1
  • PostgreSQLline 2
  • REST API designline 4
  • SQLline 5
Plain-English search
Describe the person you need. Results say why each one matched.
Interview kits
Questions from the candidate's own code, with what a good answer sounds like.
Private notes
Your notes help your team and never lower a candidate's score.
Whole batches
Colleges and clubs onboard a cohort with one invite link.
Scoring

A score you can audit.

Candidates see the same breakdown recruiters do, with the reasoning for every point. Copied code, tutorial clones and starred empty repos score low, and thin evidence caps the result.

Competitive programming counts too, but only from a verified LeetCode account.

DevScoreout of 1000
  • Project substance250
  • Engineering practice200
  • Code quality200
  • Sustained activity150
  • Breadth and depth150
  • Community impact50

Rookie · Rising · Advanced · Elite · Legendary

Who it's for

Built for the people on both sides of the hire.

Candidates

Let your work speak.

Connect once and your score updates itself. See why you scored what you did and what to build next. Free, with export and delete in Settings.

Recruiters

A shortlist you can defend.

Search by what people can do, open the code behind each skill, and run a credible technical screen even if you don't code.

Colleges and clubs

Onboard a batch.

One invite link, students join with consent. See who has verified, who hasn't started, and which skills the batch is missing.

Free for candidates, and free for recruiters during our pilot. Colleges and agencies, talk to us.

Trust

Hiring data is about real people. We act like it.

You stay in control
Hide your profile any time, keep the public badge off, and download or delete everything from Settings.
Scores can't be edited
Only our servers write scores and verification flags. Login tokens never reach the browser.
Flags are signals, not verdicts
AI-writing estimates are unreliable, so they only ask a human to look closer.

Short code excerpts are reviewed by Google Gemini. We keep derived skills and scores, not copies of your repositories. Privacy policy

Roadmap

What works today, and where it is going.

Live today
  • GitHub and LeetCode scoring
  • Code walkthrough verification
  • Plain-English candidate search
  • Interview kits and summaries
  • College and club dashboards
  • Chrome extension and public badge
Building next
  • Opt-in, read-only access to private repositories
  • Scoring for more platforms such as CodeChef
  • Deeper review of larger codebases
Exploring
  • Connections to applicant tracking systems
  • Ranking that learns from real hiring outcomes
  • Team-level skill gap reports

Items under “building next” and “exploring” are plans, not commitments or promised dates.

FAQ

Questions, answered plainly.

How do you know a candidate owns the GitHub account?

They sign in with GitHub OAuth, so GitHub itself confirms it. LeetCode is verified with a one-time token in the bio. An account links to one profile only.

What about people whose best work is private?

Today we analyse public repositories. Opt-in, read-only access to private ones is on our roadmap. Meanwhile the code walkthrough lets a candidate show they understand their own work.

Can candidates cheat the walkthrough with AI?

Pasting is blocked and answers are timed. Typing behaviour and an AI-writing estimate flag answers for review. No tool can prove AI use, so a flag is a reason to talk, never an automatic rejection.

Which platforms are supported?

GitHub and LeetCode are scored today. CodeChef and HackerRank are shown but not scored. GitLab and Bitbucket are not supported yet.

Should a score decide who gets hired?

No. Scores are evidence to help a person decide faster and more fairly. The decision stays with people.

Stop reading resumes. Start reading code.

See how it works

Hiring for a team or onboarding a batch? Talk to us