How to Verify a Candidate Actually Knows Go or TypeScript Before You Hire

Published: November 5, 2026
Tags: Hiring, Skills-Based Hiring, Technical Screening, Go, TypeScript

---

The CV Says Go. The Offer Letter Is a Bet.

Somewhere on your desk is a resume that says "Go" — or "TypeScript," or "distributed systems," or all three in a tasteful sidebar of coloured skill bars. The interview went well. The references checked out. And now you're about to convert that document into a salary line, a laptop, and a seat on your team.

It's worth pausing on what that conversion actually costs. SHRM cites estimates that recruiting, hiring and onboarding a single employee can run as high as $240,000 in total investment — salary, fees, ramp time, the whole lifecycle. And if the person turns out wrong, you don't get a refund; you start the meter again. When Robert Half surveyed CFOs about the worst consequence of a bad hire, it wasn't the money that topped the list: degraded team morale came first at 39%, followed by lost productivity at 34%. Supervisors, meanwhile, lose around 17% of their working week to managing underperformance — nearly a full day, every week, redirected from everyone else.

So the bet is real. The question is what evidence you're betting on — because the one line item that matters most, can this person actually write Go at the level we're hiring for, is the one your current process is least equipped to confirm.

---

Resumes Can't Verify Skill — Employers Already Know It

This isn't a controversial claim anymore; it's a settled one. A 2025 TestGorilla survey of more than 2,000 employers and job seekers across the US and UK found that 89% of UK and 86% of US employers are having problems with resumes. The pain points are specific: 1 in 3 employers can't tell from a resume whether an applicant has the skills they need, 39% find it hard to rank candidates using resumes, 36% say they don't know when a resume is even accurate, and 27% report that applicants' resumes have become too similar to differentiate.

The candidates agree with you. CoderPad's State of Tech Hiring 2025, which surveyed more than 5,000 developers and recruiters, found that 72% of candidates believe resumes don't showcase their actual skills. And yet — here's the dysfunction — 71% of recruiters still rely on resumes to identify technical skills. Both sides of the table know the instrument is broken. Both sides keep using it.

And the signal is getting worse, not better. In the same TestGorilla survey, 73% of employers reported a rise in AI-generated resumes. The document that was already a poor proxy for skill is now partially written by a machine optimised to produce a plausible document. Polished prose about goroutines and generics has never been cheaper to manufacture — which means it has never carried less information.

A resume can tell you someone claims to know Go. It cannot tell you whether they do. That distinction is the whole problem.

---

Interviews Sample Confidence, Not Competence

The standard fallback is the interview loop: technical chat, maybe some live coding, a whiteboard session if your team still believes in them. Interviews are valuable — but they're valuable at measuring a different thing. An unstructured technical conversation rewards fluency of speech, composure under observation, and the ability to sound senior. Those correlate with competence sometimes. They are not the same variable.

Employers feel the gap. In TestGorilla's survey, 55% of US employers named "determining if candidates have the right technical skills" as the single hardest step in recruitment — ahead of resume filtering itself, which only 39% flagged. And CoderPad's State of Tech Hiring 2026 report is blunt about the cause: many hiring processes are "still optimizing for outdated signals." A confident chat about architectural trade-offs is an outdated signal. It's measuring how well someone talks about code in a room, not whether they can produce it on a deadline.

To be clear: interviews aren't useless. They're where you assess judgment, communication, how a candidate reasons about ambiguity — things no exam will measure for you. The mistake is asking the interview to also be your evidence of code fluency. It's the wrong instrument for that job, and the result is that the most important claim in the hire goes unverified until week six, when the first real pull request lands.

---

What Actually Verifies a Go or TypeScript Claim

If your requisition is a mid-level Go hire, the instrument already exists: the Golang 1.27 Professional exam. But the principle matters more than the product. The fix is not more interviewing, and it's not a take-home project your team will argue about in the debrief — it's a standardized, timed, externally-set skills examination placed between the shortlist and the offer. The same instrument, the same conditions, the same pass mark, for every candidate.

This is not a radical position. You'd be joining the majority: the TestGorilla survey found that 85% of companies are already using skills-based hiring, that 71% of employers say skills tests are more predictive of job success than resumes, that 2 in 3 reduced their mis-hires after adopting skills tests, and 3 in 5 cut their time-to-hire. Meanwhile CoderPad's 2026 platform data shows global technical assessments have grown 48% since mid-2023 — employers everywhere are paying to verify, not to believe.

Here's what the verification step looks like in practice. A candidate sits a timed exam — 30 questions in 60 minutes, drawn from a larger question pool and covering defined domains for the language in question — scored against a fixed pass mark. There's no interviewer to charm, no scope to negotiate, no partial credit for a good explanation. The result is a number that means the same thing for every candidate who sits it.

Take the Golang 1.27 Professional exam as the working example: 30 questions, 60 minutes, £19.99, a defined pass mark — covering the language, the standard library, and what changed in 1.27. Send it to your shortlist before the final round. A pass means the claim on the CV just became evidence. A fail means you spent twenty pounds learning what the $240,000 process would have taught you in month three.

---

Match the Exam to the Requisition

One reason teams resist "tests" is the memory of bad ones — senior engineers asked trivia questions, juniors asked to whiteboard compiler internals. The fix is matching the instrument to the level you're hiring for. ProvedExpert exams come in tiers — Foundation, Professional, Expert — so a junior hire gets screened for foundations while a senior hire is checked against the depth the role actually requires. The Professional tier is the canonical mid-level hire; if you're unsure of your own bar, benchmark a few of your existing team through the same exam first and you'll know exactly what a pass is worth.

There's also a wider point here for the manager running the process. Verifying the technical claim is one step; the rest of hiring — writing the req, running the loop, giving feedback to the candidates you reject, onboarding the one you accept — is management craft. If hiring responsibility just landed on your desk, CourseThread's Team Performance and Feedback email course covers that ground, including a dedicated lesson on hiring and onboarding basics. Learn the process there; verify the technicals here.

---

The Cheapest Check in Your Process

Step back and look at the asymmetry. On one side: a resume signal that 86–89% of employers admit is broken, an interview format that most say makes technical skill the hardest thing to determine, and a downside that SHRM prices at up to $240,000 — before you count the quarter of roadmap, the 17% of your week, and the morale damage CFOs rank above money.

On the other side: £19.99 and one hour of the candidate's time, spent before you sign.

You already verify everything else in the stack — references, right-to-work, budget approval. The only claim you're taking on faith is the one the whole hire depends on. Stop believing the CV. Start checking the skill.

Hiring TypeScript instead? Send your shortlisted candidate the TypeScript 7 Professional exam — 30 questions, 60 minutes, £19.99 →

Hiring for a different stack or seniority tier? The full exam catalogue covers Foundation through Expert across the languages you're actually hiring for — same fixed standard, same hour, same answer: evidence instead of impressions.