Free 1-week POC — we build a working prototype for your use case, no commitment. Limited slots this month.Claim a slot →
Our Work
//case_study
AI ProductArtinoid Product

AI-Powered Candidate Fit Scoring, Directly Inside LinkedIn

Hirenoid is an AI recruitment product we built end-to-end. It scores LinkedIn profiles against a job description in real time, breaks the result down by weighted parameter, and gives recruiters a structured read on every candidate without leaving their browser.

PythonPythonFastAPIFastAPIReactReactTypeScriptTypeScriptChrome ExtensionGPT-4oGPT-4oWeighted ScoringAWS LambdaAWS LambdaServerlessREST API

Recruiting teams rarely struggle to find candidates. LinkedIn has over a billion profiles. The problem is figuring out, quickly, whether the person in front of you actually fits the role you're hiring for.

The way most teams handle this: open a profile, glance at the JD in another tab, form a gut feeling, move on. Repeat that sixty times and you've burned a workday on something that should take a fraction of that. Worse, you've done it inconsistently — the criteria in your head on Monday are not quite the same as they are on Friday afternoon after your fourth back-to-back call.

Hirenoid is the product we built to solve this. A Chrome extension and web platform that scores LinkedIn profiles against a specific job description, breaks the result down by parameter, and hands the recruiter a structured read in seconds.

The Outcome

~60%
Faster candidate evaluation
3
LinkedIn platforms supported
Dual
Outbound sourcing & resume screening
Unlimited
Profile evaluations per JD

The Problem We Set Out to Solve

The tools recruiters use today were built around different problems.

LinkedIn search is good at finding people who match keywords. It can't tell you whether someone's three years in fintech makes them a fit for your SaaS sales role, or whether their stated Python skills are actually relevant to what you need. Every profile still has to be manually evaluated.

ATS platforms help teams manage candidates after they apply. They're not designed for outbound sourcing, which is where most of the real work happens. When a recruiter is working through 40 profiles on a Tuesday afternoon, their ATS is basically idle.

There's also the inconsistency problem, especially in teams. When four recruiters are working the same pipeline, each has a slightly different idea of what a good candidate looks like. One weights certifications; another cares mostly about domain experience. The shortlist ends up reflecting individual preferences as much as the actual requirements.

And the time adds up fast. Reading a profile carefully, checking it against the JD, noting what fits and what doesn't — that's three to five minutes per candidate on a good day. At the volume a busy recruiter handles, a significant chunk of the day is gone before they've made a single decision that required actual judgment.

What We Built

We built Hirenoid as two connected surfaces: a Chrome extension that works inside LinkedIn, and a web platform for pipeline management and inbound screening.

1. Chrome Extension Across All LinkedIn Surfaces

The extension runs on Standard LinkedIn, Sales Navigator, and LinkedIn Recruiter. All three, because sourcing happens across all three and limiting it to one would have made it a niche tool.

The recruiter uploads their job description once. After that, every LinkedIn profile they open is automatically evaluated against it. A proprietary extraction layer pulls the candidate's work history, skills, and experience in real time. Results show up inside the extension panel within seconds — no tab switching, no manual work.

2. Weighted Compatibility Scoring Engine

The scoring engine is where most of the engineering effort went. A single match percentage tells a recruiter almost nothing useful — they need to know which parts of a candidate's profile match and how much each one matters for that specific role.

The engine scores candidates across five parameters, each weighted differently:

  • Required Skills — the highest-weighted category; a hard gap here changes the overall read significantly
  • Industry Experience — how relevant the candidate's domain background is to the role
  • Education — qualification match against what the JD specifies
  • Certifications — supporting credentials
  • Soft Skills — lower-weighted, contextual signals

The output is an overall compatibility percentage plus a breakdown by parameter. The engine also generates a pros and cons analysis tied to the specific JD: what this candidate brings to the role and where they fall short, in plain terms.

3. Resume Screening Mode

For inbound candidates — people who've applied rather than been sourced — recruiters can upload a resume directly into the platform and run it through the same scoring engine against any active JD.

Same parameters, same weighting, same output format. Whether a recruiter is hunting or reviewing applicants, every evaluation comes out structured and comparable.

4. Web Dashboard and Pipeline Management

The web platform is where shortlisted candidates get organised. Each one is stored with their full compatibility report: scores by parameter, matched and missing skills, and the pros and cons breakdown.

Recruiters can manage candidates by JD, track evaluation status, and share pipeline visibility with the rest of the team. For agencies running multiple roles across different clients, this matters — spreadsheets and scattered notes get replaced by one place with a consistent structure across every active pipeline.

Why This Matters

The most obvious change Hirenoid makes is to where a recruiter spends their time during sourcing.

Reading a profile, cross-referencing it against the JD, noting what aligns and what doesn't — that process gets compressed. The structured output handles the mechanical part. The recruiter reads it in under a minute and decides whether to act, rather than spending several minutes assembling the same picture manually.

The consistency side is less visible but probably matters more. When every candidate goes through the same weighted rubric against the same JD, shortlisting stops depending on who happens to be reviewing that day. Teams align faster on who should move forward, and the reasoning is on record.

The scoring also catches things that a quick read tends to miss. A strong-looking profile with a gap in a core required skill can look fine on first pass. A less polished profile that actually hits every requirement can get skipped. The engine reads against the JD, not against a general impression of what a capable person looks like.

See It in Action

Want Us to Build Your AI Product?

From concept to production, we build AI-powered products, intelligent automation, and custom software that solves real problems.

Get in Touch