Screening hourly and trades candidates who aren't resume-literate

Somewhere in your candidate list right now is a message that says something like “I’m a plumber looking for a job, call me,” with no resume attached and no attempt to format one. Somewhere else is a candidate who typed “what’s the resum?” into your application chat because the word itself didn’t register. Neither one is telling you they can’t do the work. They’re telling you they’ve never needed a document to prove they could.

If you post hourly or trades roles, you’ve seen some version of this. A candidate asks how to apply “on linkin” when your listing lives on LinkedIn. Someone writes back “you mean a CV in a PDF?” like it’s the first time anyone’s asked. One person just says “wow you make this hard” and you don’t know if they finished applying or gave up.

The instinct is to read all of that as a signal about the candidate: disorganized, not serious, maybe not up to the job. That instinct is usually wrong, and it’s an expensive place to be wrong. The candidates most likely to trip on resume vocabulary aren’t the weak end of your pool. They’re often the ones who learned the trade on a job site instead of in an application form, which is exactly who you posted the role for.

The application you built is grading a vocabulary, not a skill

A resume-shaped intake asks a candidate to translate their own work history into a specific dialect: bullet points, action verbs, a summary at the top, a PDF at the end. Office and admin candidates pick that dialect up early, often before their first job, because school and career services teach it directly. A lot of hourly and trades candidates never got that class. They learned the work by doing it, one shift or one job site to the next, and nobody ever asked them to write it down.

So when your application opens with “upload your resume” or a screening question uses the word “CV,” it’s testing whether someone already taught this candidate the paperwork, not whether they can do the job. Those two things get treated as the same test, and for a huge share of hourly and trades candidates, they were never the same skill at all.

There’s a device problem sitting underneath the formatting one, too. 16% of US adults are smartphone-only internet users with no home broadband, according to Pew Research Center’s mobile fact sheet, and that number climbs to 34% for households earning under $30,000 a year, against 4% for households over $100,000. Building a formatted PDF resume assumes a keyboard, a document editor, and time at a desk. A lot of your candidates are doing this on a phone between shifts, which is a real reason “how do I attach my resume” and “how do I apply on linkin” show up as often as they do. That’s a tooling mismatch between what the process assumes and what a candidate is actually holding, and it has little to do with how comfortable they feel.

Who actually shows up looking rough

Picture the candidate list for an HVAC tech, a carpenter, or a maintenance role: people who learned on a crew, held a state license for years, and never once needed a formatted document to prove it. None of that is a weak background. It’s the exact background you’re trying to hire. But it doesn’t produce a document that looks like what your application template expects, and it doesn’t come with fluency in the word “resume” as a genre, only as a vague thing other jobs asked for once.

The dispatcher who schedules those same crews often comes from the same non-resume-literate applicant pool, even though the role is built entirely around phone and schedule work rather than a trade skill.

What “wow you make this hard” is actually telling you

Read that message again without the frustration baked in. It’s a candidate telling you, in real time, that your front door is harder to walk through than the work itself will be, not a complaint about the job.

That matters because the cost doesn’t show up as a rejection you can see and reconsider. It shows up as someone who never finishes the application, or finishes it with one flat line of text that scores low on your usual read, next to a five-paragraph application from someone who ran it through an AI polishing tool first. If you’re scoring on polish, the AI-assisted answer wins every time, and the person who’s actually done the job for six years loses to someone who’s never touched a wrench but knows how to prompt a chatbot. That’s the opposite of what screening is supposed to protect you from.

The quieter cost is what you never see at all. Some candidates read “resume required” or hit a confusing apply flow and just leave. You don’t get a bad application from them. You get no application, and you never find out you lost them, because a drop-off doesn’t look like anything on your dashboard. If you’ve ever handled a flood of job applications and still felt short-staffed at the end of it, some of that gap is candidates your own front door turned away before they ever became a name in your pile.

Redesign the front door candidates walk through

The instinct to fix this is usually “make the resume optional” or “add a note explaining what a resume is.” Both help a little. Neither addresses the actual problem, which is that the whole intake is still built around a document a lot of your best candidates were never taught to produce.

The better fix is smaller and more direct: stop asking for the document, and ask the questions the document was supposed to answer, in plain language. Instead of “upload your resume,” ask “how many years have you worked as a plumber or in a related trade?” Instead of “attach your CV,” ask “do you have a valid HVAC certification, yes or no?” You’re not lowering the bar. You’re asking the same question in a dialect everyone in your candidate pool actually speaks, which is closer to what resume screening was always trying to accomplish, just without the document acting as a toll booth in front of it.

This is where a resume stops being the price of admission and becomes one optional layer among a few. A candidate who has a resume and wants to attach one still can. A candidate who’s never made one isn’t stuck at the front door because of it.

You still get consistency, just not from a document

The honest objection here is fair: “I still need something to compare candidates on, or I’m just guessing.” That’s true, and it’s not actually in tension with any of this. What you’re changing is the instrument, not the standard.

A resume tries to answer two different questions at once: does this person meet the basics, and can they actually do the work. It answers both badly for hands-on roles, which is a big part of why hourly and trades hiring works better without one as the gate at all. Split the two questions apart and you get more consistency, not less.

Plain-language questions handle the basics

Structured qualification questions, phrased in plain language, handle certifications, availability, location, and years on the job. Everyone answers the same short list, so you’re comparing like against like, and none of it requires a formatted document to do it.

A conversation handles the rest

A short one-way interview handles what the resume was never good at anyway. One or two real-situation questions, spoken instead of written, ask a candidate to walk through a callback that went wrong, a customer complaint, or how they’d handle a schedule change mid-shift. Someone who’s spent years on the job answers that easily out loud, even if they’d never know where to start writing it down. That’s the fluency you actually want to measure. It was never really about the document.

Building the intake that doesn’t require anyone to translate themselves

Say you’re hiring an HVAC technician for a growing service business, and the role pulls forty candidates in the first week. In the old process, maybe eighteen submit something that reads like a real resume, another dozen send a phone number and a sentence, and the rest never finish the form. You’d be screening eighteen applications and quietly missing the other twenty-two.

Rebuild the same role in Truffle and the front door changes shape. Qualification questions open the intake in plain language: certification held, years of hands-on experience, service area, availability for on-call rotations. Every candidate answers the same short list in under a minute, resume or not. From there, a one-way interview asks two or three real-scenario questions, spoken on camera or audio, and every response gets a match percentage scored against the criteria you actually defined for the role, not against how well the answer reads on a page. A resume upload stays available for anyone who has one, but it’s context now, not a gate.

By the time you open the candidate list, all forty candidates have something comparable next to their name, whether they showed up with a formatted PDF or a one-line text message. You’re not choosing between a rough application and a polished one anymore. You’re choosing between candidates, on the same evidence, which is what screening was supposed to give you in the first place.

The read you’re practicing here won’t stay optional

None of this is really about hourly and trades roles specifically. It’s about noticing when your process is measuring fluency in a format instead of fitness for a job, and that gap is about to widen everywhere, not just at the front door for skilled trades.

The same AI tools making it easy to polish a five-paragraph application from a one-line reality are getting used on office and admin roles too. As that spreads, “reads well” and “does the job well” keep drifting further apart across your whole funnel. Trades and hourly roles are just where the gap shows up first. The operators who get good at reading past format now, on the applications that make it obvious, are the ones who’ll still be reading accurately once every candidate’s writing sounds the same.

Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, so you decide which layer carries the weight for each role instead of inheriting a resume requirement nobody chose on purpose. Plans start at $49 a month on a shared credit pool across all three, and there’s a 7-day free trial with 30 credits and no card required if you want to rebuild one role’s intake before you touch the rest.

Frequently asked questions about screening candidates who aren’t resume-literate

Should I reject a candidate whose application is confusing or badly written?

Not on that alone. A confusing application from an hourly or trades candidate is often a vocabulary gap, not a competence gap. Screen on qualification questions and conversation first, and let a rough written answer carry the least weight of anything you look at.

How do I write qualification questions that candidates without resume experience will understand?

Ask the question you actually want answered, not the document you’d normally request. Replace “submit your resume” with “how many years have you done this kind of work?” Replace “attach your CV” with a specific yes/no about a certification or license. Plain, direct phrasing works for every candidate, not just the ones unfamiliar with resume terms.

Is it fair to require a one-way interview from candidates who don’t have a resume?

Yes, and it’s usually easier for them than the alternative. Talking through a real work scenario on camera or audio doesn’t require any document or format knowledge. It’s a more level field for someone who’s never built a resume than a written application ever was. Be honest about the trade-off too: on a thin-pool role where you want to meet almost everyone, a required video step can cost you a candidate who’d rather not record one, so use the parts that fit the role rather than requiring all three by default.

Should hourly and trades roles require a resume at all?

Make it optional rather than required. Anyone who has a resume can still attach one for extra context. Anyone who doesn’t isn’t blocked from applying because of it. The qualification questions and the interview carry the actual screening weight either way, so the resume becomes one more data point instead of the ticket to get in the door.

For a role where this shows up constantly, our CNC machine operator hiring guide builds the interview questions and screening workflow around exactly this: candidates who can run a great part but never learned to write about it.

What if a candidate asks what a resume even is during the application?

Answer it plainly and keep moving. “It’s a summary of your work history. If you don’t have one, that’s fine, just answer the questions below.” That single line clears up more confusion than any amount of redesigning your job post copy, and it tells the candidate the process isn’t designed to filter them out for not knowing the term.