Hiring filters miss real engineering ability

Signal

Across six pain signals spanning two distinct sources (Product Hunt and Hacker News), hiring managers and recruiters repeatedly say the screening layer is broken. One Product Hunt commenter put it bluntly: "Hiring devs is broken- you can't tell if someone is a 100x engineer just by looking at a resume." (Product Hunt). Another flagged the specific GitHub-gaming problem: "commit authenticity (no more fake green charts)" (Product Hunt), while a Hacker News developer described being screened with "Write this <x> using this <y>" syntax quizzes instead of real problem-solving.

Synthesis

The pain pattern is a credibility gap: every cheap signal recruiters rely on — resume keywords, Excel-expert claims, GitHub green squares, CS degrees — is either gameable or uncorrelated with ability to ship. The moment is now because (a) LLMs have made resume keyword-stuffing and fake commit generation trivially automatable, and (b) recruiters explicitly say current tools fail. The people hurting most are mid-funnel technical recruiters and hiring managers at small/mid companies who lack the engineering bandwidth to do deep technical screens but get burned when "paper-perfect" hires can't ship. Self-taught builders are hurt symmetrically — filtered out before anyone sees their actual work.

Build Idea

Concept: A web tool where a recruiter pastes a GitHub username and instantly gets an "authenticity score" that flags fake commit patterns, trivial commits, and AI-generated padding versus substantive contributions. MVP (≤2 hours): - Input field for GitHub username; pulls public events + repo list via GitHub REST API - Heuristic flags: commits with <5 LOC change ratio, identical-time-of-day patterns, commits only to personal repos with zero stars, README-only repos, force-push churn - Surface top 3 "substantive" PRs/commits by lines changed, language, and external repo contribution - Single-page result: red/yellow/green badge + 5 bullet evidence points the recruiter can paste into a hiring doc - Deploy on Vercel as a free public tool with email gate for the PDF export Validation step: Post on r/recruiting and the Hacker News "Who is hiring" thread comments: "Built this in a weekend to flag fake GitHub profiles — DM me a username, I'll send the report free." Count how many recruiters reply within 48 hours.

Counter-view

The deeper problem isn't detection — it's that recruiters who can't read code also can't judge a "substantive PR" even when you hand it to them, so the report's signals get ignored or misused. Worse, anyone determined to game GitHub will adapt within a release cycle (just like SEO vs. Google), turning this into a perpetual cat-and-mouse with no moat — GitHub itself, or incumbents like LinkedIn/Gitential/Code Climate Velocity, can ship the same heuristics in a sprint. And recruiters historically pay for candidate sourcing, not candidate filtering, so willingness-to-pay may collapse the moment the free tier ends.

Signal

Multiple Product Hunt and Hacker News threads converge on the same complaint: resumes and CVs are unreliable signals for engineering ability, and even GitHub activity is now gameable. One hiring manager put it bluntly: "Hiring devs is broken- you can't tell if someone is a 100x engineer just by looking at a resume." (Product Hunt). The pain extends beyond software — finance hiring managers echo the same frustration with "Excel expert" claims, and self-taught developers on HN report being filtered by syntax-memorization tests instead of problem-solving evaluation.

Search Intent

Searchers fall into two distinct camps. Hiring managers are solution-aware and comparison-stage: they know resume screening is broken and are actively looking for alternatives (work-sample tests, take-home projects, trial tasks, async coding challenges). Job-seeking engineers are problem-aware and searching for ways to demonstrate ability beyond a CV (portfolio formats, how to prove shipping ability). Current content fails them because it's either vendor marketing for legacy platforms (HackerRank, Codility) that reproduce the syntax-test problem, or generic LinkedIn-style "top 10 hiring tips" listicles that don't address keyword-gaming or GitHub authenticity. There's a gap for honest comparison content that names tools and discusses what actually predicts shipping ability.

Keyword Candidates

Phrase	Intent	Rationale
how to screen engineers without resumes	informational	Captures hiring managers in problem-aware stage looking for alternatives
work sample test vs coding interview	commercial	Comparison-stage query from teams choosing an evaluation approach
best take-home assignment platforms for developers	commercial	High commercial intent, mid-funnel; maps to SaaS affiliate or directory monetisation
how to detect fake github commit activity	informational	Long-tail, low-competition; directly cites a signal from the evidence
alternatives to hackerrank for hiring senior engineers	commercial	Captures dissatisfaction with incumbent syntax-test tools
how to prove you can ship without a CS degree	informational	Job-seeker side; long-tail with clear persona
trial project hiring process for software engineers	informational	Maps to a specific tactic hiring managers are evaluating
portfolio for self-taught developers that gets interviews	informational	Job-seeker long-tail, high specificity, low SERP competition

Recommended Content Format

Format: Comparison page + companion blog post hub Outline: - Lead comparison page: "Take-home tests vs live coding vs work-sample trials — which actually predicts shipping ability" - Side-by-side table of 6–10 platforms (CoderPad, HackerRank, CodeSubmit, Otta, Hatchways, etc.) with axes: gameability, candidate experience, signal quality, price - Dedicated section on GitHub authenticity signals (commit cadence, PR depth, issue triage) and how to detect green-chart farming - Embedded scoring rubric template (downloadable) for evaluating shipping ability — drives email capture - Companion posts targeting long-tail terms (self-taught portfolio, alternatives-to-X) that internal-link to the hub - Honest "when work-samples fail" section to differentiate from vendor content

Counter-view

This space is crowded by well-funded vendors (HackerRank, CodeSignal, Karat) whose domains already dominate commercial intent SERPs, and Hacker News threads on "how to hire engineers" rank for many head terms — Google may surface those community discussions over a new site. Informational queries on the job-seeker side are increasingly answered by AI Overviews and LinkedIn posts, compressing click-through. Realistic moat is long-tail specificity (e.g. "alternatives to X for Y team size") plus a genuinely opinionated rubric, not head-term ranking.