Private organisation membership
Jordan
Membership verifiedEstablished private organisation.
Sam
Membership verifiedEstablished private organisation.
Only interview engineers who’ve built what you need.
Send one link. See their real code and proven work from past jobs.
Your engineers keep building instead of screening candidates.
- Projects they builtCode checked for your role
- Work at past companiesProven without sharing code
Both look good on paper.
The work tells a different story.
Same backend role. Two fictional candidates.
| Illustrative role match | Jordan 36% | Sam 88% |
|---|---|---|
| Private company work | Verified work in an Established org14 of 16 contributions in TypeScript. | Verified work in an Established org18 of 24 contributions in Python. |
| Python | not found | found |
| Backend | not found | found |
| Docker | found | found |
| Kubernetes | not found | Ask |
| Next step | Ask for Python work. | Explore production depth. |
“Not found” refers only to this work. Not a hiring recommendation.
Evidence & interview questions
Fictional findings · Jan–Sep 2026 · Two submitted repositories per candidate
Work contributed
Jordan
Frontend contributions14 of 16 verified contributions involved TypeScript. Python was not found in the reviewed work.
Sam
Backend contributions18 of 24 verified contributions involved Python. Backend work spans the reviewed sample.
Submitted projects
Jordan
React / TypeScriptDocker, CI and tests. Python services not established.
Sam
Python / FastAPIDocker, tests and Kubernetes configuration. One security pattern flagged for review.
Public profile
Jordan
Frontend activityActive in 10 of 12 months. Public work also points to frontend development.
Sam
Python & code reviewsActive in 7 of 12 months. Public activity reinforces the private work.
Still to establish
Jordan
Python backend workMissing from this sample, not disproven.
Sam
Production operationsDeployment configuration is visible; operating it in production is unconfirmed.
Interview question
Jordan
Request relevant workCan you share a Python backend service you contributed to and explain your part in it?
Sam
Explore production depthTell me about a failed deployment of a Python service. How did you diagnose it and recover?
Membership and contributions are separate checks. Membership alone does not prove ability; neither check proves employment or code ownership. Illustrative scores and findings.
How it works
- You
Your role sets the bar.
Paste the job description. It becomes the requirements every check is measured against.
16signalsJob descriptionExampleData engineerExampleBuild Python data pipelines with PostgreSQL and Docker. Handle failures and retries.
Role requirementsExampleStackWhat the work must show - Candidate
Their code gets a technical review.
They pick the projects they built. Each gets a deep review against your stack: code practices, testing, security, architecture.
Invitation for Backend engineerExampleProjects they builtCandidate’s viewThey choose what to share.Code reviewExamplepayments-service · Python backend
PracticesTyped API boundariesTestingRetry cases coveredSecurity1 flag to reviewArchitectureSeparate service layersEach project reviewed against the role. Findings, including gaps, stay visible.
- Candidate
Their past-company work, verified.
They confirm their work in a company's GitHub. You get proof it's real; the code stays private.
Work at past companiesAcme Engineering@acme-engineeringSelected by the candidateVerified company workExampleAfter candidate review and submission
GitHub accountConfirmedContributionsVerifiedMembershipVerifiedGitHub account, contributions and membership checked separately.Code stays private. You receive the proof. - You
Your decision: who to interview.
Keep your technical assignment for candidates whose work fits, or skip it when their work already shows enough.
Backend engineerFictional candidatesIllustrative candidate shortlist for the same backend role. Code review shows requirements found. Proven means contributions verified. Candidate Role matchMatch Code reviewReview Past-company workCompany Status Sam 88% 3 of 4 requirements3/4 Contributions provenProven Shortlisted Priya 71% 2 of 4 requirements2/4 Member onlyMember only Shortlisted Jordan 36% 1 of 4 requirements1/4 Contributions provenProven Hold Alex — —— —— Waiting Code review: requirements found.
Proven: contributions verified.
Your first 3 candidates are free.
Inviting costs nothing. A report counts only when a candidate submits.
Loading plans…
Common questions.
Does it replace interviews?
No. The report helps you decide whom to interview and what to ask.
Can it replace a technical assignment?
Sometimes. A relevant personal project may show what your team needs without another assignment. Your team decides whether that’s enough.
What does the candidate have to do?
Open your link, sign in with GitHub, and tick what to share. About 5 minutes, mostly waiting while it runs. Far quicker than a technical assignment.
Can it show work at past companies?
Yes. If they worked in their company's GitHub organisation, the report shows they were a member and the work they did there, checked in their own GitHub session without exposing the company's code.
What if they don't have much public work?
Missing evidence isn't missing ability. The report turns gaps into questions to ask, not reasons to reject.
Does it work with our ATS?
Not yet. Paste the job description, then invite candidates by email or GitHub username, or import a list. Integrations are planned.
What happens to candidate data?
It's used only for the reports you ask for, and never sold. Delete your account any time; it's all erased after 30 days. GDPR rights apply.
Make your next
interview count.
See how it fits your next hire before you spend another hour interviewing.