For Hiring Teams

Anyone can write code that works. Not everyone does more than that.

No agency, no middleman - just proof of who did more than the minimum, and who stopped once it worked.

3 free credits to start - no credit card required

This actually happened

...A junior was hired after a solid CV, a good interview, and a coding test he passed. Nobody checked how the code came to exist. Months later, the truth came out: mostly tutorials and outside help, stitched together. He could reproduce solutions, not build on his own. A surface-level test validated him...

Passing a test is not the same as being able to build.

For Hiring Teams - Sample Test Results

What Juniob Catches

This is what companies receive when they unlock a developer's test results. This candidate passed resume screening and had a solid GitHub - here's what Juniob analysis found.

Marcus Chen

Interview with Caution

Technical gaps and authenticity concerns require careful probing - based on all 3 submitted projects.

This analysis is based on code and project history alone. It does not assess communication, teamwork, or culture fit - those still require a human interview.
52/100Tech Score
Below ExpectedLevel
InconclusiveAuthenticity

Marcus has a solid handle on backend development basics, and his most recent project shows real improvement - cleaner code and more careful error handling. But his earliest project has a serious security weakness: the way it builds database queries could let someone view or change data they shouldn't, and a real database password was left exposed in the code. These need to be fixed before he works with real user data.

What You Need to Know
Key Insights
Clear growth trajectoryQuality score rose from 38 to 70 across three projects, with each one fixing patterns flagged in the previous one
Security weakness in earliest projectTwo endpoints let users influence database queries directly (a SQL injection risk) - a common gap early in a career, and one that's straightforward to fix
Solid grasp of core backend patternsCorrectly handles async operations, request middleware, and secure login (JWT) across all three projects
No automated testsNone of the three projects include a test suite, despite manual endpoint testing
Red Flags
1
  • Exposed database credentialsA real database password was committed in plain text to the public user-api repository on GitHub, where anyone could see it - worth asking Marcus directly whether it's since been changed
Points to Discuss
  • SQL injection risk - getUserById and searchPosts in user-api don't safely handle user input in database queries. This is the most urgent fix.
  • Internal errors exposed - some of user-api's error responses include raw database error messages, which could give an attacker clues about the system
  • No automated tests - none of the three projects include a test suite to catch bugs before they reach users
  • No pagination - the task list in task-manager loads everything at once, which would slow down once there's a lot of data
Interview Prep
Questions Based on Their Code
  • "Walk us through how you'd rewrite the getUserById query in user-api to remove the SQL injection risk - what would you change and why?"Tests: Security awareness • His answer reveals if he understands the fix, not just the symptom
  • "In blog-api you introduced Sequelize and centralized error handling. What problems were you trying to solve compared to user-api?"Tests: Whether he can explain his own growth and reasoning, not just recite fixes
  • "If a request to one of your endpoints failed in production, how would you go about debugging it without local access to the database?"Tests: Defensive thinking and production debugging skills
Estimated time until contributing independently6-8 weeks with code review on security-sensitive areas
Authenticity Deep Dive
Inconclusive

Commit history is available for all three projects and shows a consistent single-author pattern with debugging commits. But a burst-commit pattern in task-manager (34 commits across 12 days) makes the overall verdict inconclusive rather than fully verified. We recommend verifying through live coding during interview.

Why This Matters for Hiring
Is it their work?Real developers commit regularly. Bulk commits suggest copied or AI code.
Did they learn by doing?Authentic projects show debugging, refactoring, and incremental progress.
Can they debug it?If they didn't write it, they can't fix it when it breaks in production.
Code origin riskPerfect-looking code with no iteration history is a red flag.
Project-by-Project Analysis
user-api
Discipline: LowRaises Concerns
  • Only 3 commits total across the project's history
  • Two commits each add over 1,000 lines - large local batches of work committed at once
  • No incremental history showing how the SQL queries evolved
task-manager
Discipline: AdequateNeutral Impact
  • 34 commits over 12 working days
  • Burst pattern - several days with 5+ commits followed by gaps
  • Debugging commit messages present (e.g. "fix validation bug", "fix status transition edge case")
blog-api
Discipline: HighSupports Authenticity
  • Regular commits over 3 weeks, roughly every 1-2 days
  • Commit messages show iterative debugging (e.g. "fix Sequelize association", "handle null author in comment serializer")
  • Consistent single-author pattern matching the developer's other repositories
How to Verify in Interview

Ask Marcus to share his screen and walk through the user-api authentication flow, then ask him to fix the SQL injection in getUserById live. If he wrote the code, this takes a few minutes. If not, he'll struggle to navigate his own project.

Technical Skills Breakdown
Technology Proficiency (relative to their experience on stack)
Onboarding & Growth Plan
Project Evidence (3)

What You Get

Clear Hire/No-Hire Signal

"Safe to Interview", "Interview with Caution", or "Not Ready" - with specific reasoning you can trust

Authenticity Verification

Detect copied code, generated projects, and tutorial followers before you waste interview time

Code-Specific Interview Questions

Questions targeting their actual code - impossible to fake if they didn't write it

Bugs & Security Issues

Memory leaks, exposed API keys, injection vulnerabilities - found before they're your problem

Time to Get Up to Speed

Know how long until they're contributing on their own - plan your mentoring time realistically

Onboarding Roadmap

Week-by-week plan for what they need to learn - start training day one if you hire

This is a preview. The full results have 7 expandable sections - technical skills, proficiency by stack, project-by-project evidence, and a complete onboarding plan.

Not a mass-screening tool

This is for your final 3-8 candidates - not your first 50

Do your usual CV screen first, like you always do. Juniob comes in after that - on the handful of finalists you're actually deciding between, right before the interview. At €25 per report, you're paying to get one hire right, not to screen a stack of applicants.

How It Works

Ready within fifteen minutes, no setup needed

Add a candidate's email, they submit their projects, results land in your dashboard.

01

Add Their Email

Drop their email in your dashboard. If they're already on Juniob, results appear straight away.

Takes a few clicks
02

They Submit Their Projects

If they're new, they get an invite to connect their GitHub and submit a few projects.

Minutes, on their side
03

Review & Decide

A clear recommendation with reasoning, red flags to probe, and interview questions built from their actual code.

A decision, not just data
How it works

Structured hiring signals. Not just a feeling.

Here is what you get from first contact to hiring decision.

1Company side

Adding a candidate

1
Create a company account
Free to create. You get a few free credits to start.
2
Enter a candidate email
Send them an invite. They get a link to create their account and submit their projects for analysis.
3
Track from your pipeline
See when they have registered, when their analysis is complete, and when results are ready to unlock.
You can add candidates manually or invite them by email. You only need to spend a credit when you want to unlock full results.
juniob.io/company/pipeline
Pipeline
12
Credits
3
Tracked
2
Assessed
SM
Sophie Martin
Frontend Dev · Invitation sent - not yet registered
Invited
MC
Marcus Chen
Backend Dev · Results ready to unlock
Assessed47 /100
AR
Alex Rodriguez
Backend Dev · Full results available
Unlocked72 /100
2Company side

The test results

Hiring decision
Recommend / interview with caution / do not hire
Skill breakdown
Per technology, calibrated to their experience time
Security & risk
Critical issues flagged and explained
Authenticity check
Flags code that was copied or does not appear to be genuinely their own work
Interview questions
Tailored to the gaps found in their code
Growth potential
How quickly they are likely to improve with mentoring
Scores are calibrated within the 0-3 year experience range, not benchmarked against seniors. A high score means strong command for their level.
juniob.io/company/report
MC
Marcus Chen
Backend Developer Antwerp, Belgium18 months experience
Node.jsExpressPostgreSQL
Interview with caution
Hiring decision-Proceed with caution
47/100
Average Junior
Calibrated within 0-3 years experience range - not compared to senior standards
Ready in approx. 6-8 weeks with code review
Growth trajectoryScore improved 38 to 70 across 3 projects
SQL injectionFound in earliest project - common gap
Authenticity - suspiciousTwo projects committed in bulk batches with no development history
No automated testsAcross all 3 projects
Code origin unclear - verify before proceeding
Bulk commits and code patterns suggest parts of the codebase may have been assembled from external sources rather than built independently.
3Company side

Going further

Compare candidates side by side
Select two or more candidates from your pipeline and compare their scores, skill breakdown, and hiring recommendations in a single view.
Talent PoolNew
Search across developers who've turned on visibility. Filter by stack, experience level, and location. Browse anonymously - initials only until you invite them or unlock their report.
Partner API
Integrate Juniob directly into your ATS or hiring tool. Trigger an assessment for a shortlisted candidate, pull their results, and surface hiring signals inside the tools your team already uses.
juniob.io/company
MC
Marcus Chen
Backend Dev
Interview with caution
47
/100
Node.js
6/10
Express
6/10
PostgreSQL
4/10
Git
5/10
AR
Alex Rodriguez
Backend Dev
Recommend for interview
72
/100
Node.js
8/10
Express
7/10
PostgreSQL
6/10
Git
7/10

"I used Juniob to evaluate a candidate, and it's really great. On top of being simple to use, the quality, usefulness, and efficiency are all there.

The free view alone already gives you a first read, without having to unlock a report right away. On pricing, compared to recruitment agencies or the big assessment platforms, I find it very reasonable."

A
AntoineCTO at
Clear Expectations

What Juniob Is & Isn't

Juniob provides recommendations, not judgments. We help you decide - we don't decide for you.

Juniob Is

  • A second opinion on a junior's code
  • A way to lower the risk of a bad junior hire
  • Something that helps you decide, not decides for you
  • A bridge between code and non-technical stakeholders
  • A tool you run yourself, on your terms

Juniob Is Not

  • A recruitment agency, middleman, or outsourced service
  • An ATS or applicant tracking system
  • A coding test or exam
  • A judge of communication, teamwork, or culture fit

Every assessment uses the same evaluation methodology, so when you compare two candidates side by side, that comparison is fair and consistent - not two different opinions stitched together.

Pricing

Simple, transparent pricing

Free for developers, always. Companies pay only when they unlock results.

For junior developers
Freeforever

Juniob is and will always be completely free for developers. No trial, no expiry, no catch.

  • Submit your GitHub projects for analysis
  • Honest, project-level code feedback
  • Personalized growth plan and learning roadmap
  • Shareable verified results link
  • Go fully visible or invisible, anytime
For hiring teams
3 freecredits to start

Start with 3 free credits, no credit card required. Then €25 per candidate - no subscriptions, credits never expire.

Costs less than one hour of a senior developer's time - and saves you from spending it manually reviewing the code yourself.

  • Add a candidate by email - no setup needed
  • Full test results per developer
  • Interview questions tailored to their code
  • Risk flags and authenticity signals
  • How long until they're up to speed
See full pricing

Stop guessing.

Already got a shortlist? Add their email and see exactly where they stand - in a few clicks, whatever your technical background.

3 free credits - no credit card required

Find out your real level.

Get a verified results link that shows companies your real level - plus honest feedback and a growth plan just for you. You're always in control of who sees it.

Completely free to use