How to hire a maintenance technician (job description, interview questions, screening workflow)

Most maintenance technician postings ask for "3-5 years of experience" and a list of trade certifications. At a small operation, that's screening for the wrong thing. You're not hiring someone to join a maintenance department with a supervisor signing off on every repair. You're hiring the person who decides, alone, whether a strange noise from a piece of equipment is worth stopping the line for or safe to note and revisit later, often with no one else around to double-check the call. The thing that sinks this hire is almost never a missing certification. It's a habit of acting before diagnosing, replacing a part or forcing a fix without first figuring out what's actually broken. This guide is built to screen for diagnostic judgment and safety discipline, because those are what actually predict whether this hire prevents costly downtime or quietly causes it, and a resume listing "general maintenance" doesn't show either one.

What a maintenance technician actually does at a small business

At a large plant, maintenance is a department with specialists, a supervisor, and a parts room stocked and managed by someone else. At a small manufacturing shop, property management company, or standalone facility, one maintenance technician is often the entire department, covering everything from a jammed conveyor to a leaking pipe to a broken door closer.

The core responsibilities, in practice:

• Diagnosing and repairing mechanical, electrical, and plumbing issues across equipment and facilities
• Performing scheduled preventive maintenance so small issues don't become expensive breakdowns
• Responding to urgent equipment failures and deciding what can be fixed on the spot versus what needs a part, a specialist, or a shutdown
• Following lockout-tagout and other safety procedures, especially when working on live equipment
• Keeping basic maintenance logs and parts inventory so recurring issues and past fixes aren't reinvented from scratch
• Knowing when a repair is beyond their scope and needs a licensed electrician, an HVAC contractor, or a manufacturer's technician
• Communicating clearly with non-technical managers or tenants about what's wrong and what it'll take to fix it

The technical bar for individual repairs isn't usually the hardest part; most technicians who've worked the trade can fix a jammed conveyor or a leaking valve. The hard part is judgment under time pressure: diagnosing correctly before acting, knowing when a safety shortcut isn't worth the risk, and knowing when to call in outside help instead of pushing past their own expertise. At a small operation, this person is often the only line of defense between a minor issue and real downtime or real injury.

Job description you can post today

Copy this, then adjust the specifics (your equipment, your facility, your on-call expectations) to match your company.

Maintenance technician
[Company name] is looking for a maintenance technician to keep our equipment and facility running. You'll troubleshoot and repair mechanical, electrical, and plumbing issues, perform preventive maintenance, and know when to call in outside help.

What you'll do
Diagnose and repair issues with equipment, plumbing, and general facility systems. Perform scheduled preventive maintenance to catch small problems before they become breakdowns. Follow lockout-tagout and other safety procedures on every job. Keep maintenance logs and track parts inventory. Escalate work that needs a licensed electrician, HVAC contractor, or manufacturer's technician. Communicate clearly with the team about what's wrong and what a repair will take.

What we're looking for
Hands-on troubleshooting experience with mechanical, electrical, and plumbing systems. A habit of diagnosing before acting, not just replacing parts until something works. Real discipline around safety procedures, even when no one's watching. Good judgment about when to escalate to a specialist. Certifications are a plus but not required if you can demonstrate the skill.

Schedule
[Insert hours, e.g. Monday-Friday with on-call rotation for urgent equipment failures]

[Insert pay range, per your company's policy and any applicable state salary transparency requirements]

10 interview questions, and what a good answer sounds like

1. Walk me through how you'd diagnose a piece of equipment that suddenly stopped running, with no obvious cause.

You're checking for a real diagnostic process, not a guess. A strong answer moves in order: confirm what actually happened (power loss, jam, safety trip), check the simplest explanations first, then work systematically toward less likely causes. A weak answer jumps straight to disassembling or replacing a component without first isolating what's wrong.

2. Tell me about a time you had to decide between a quick fix and doing the job right. What did you choose, and why?

This tests judgment under real pressure to get equipment back online fast. Listen for a candidate who explains the tradeoff honestly: when a quick fix was safe and reasonable to buy time, and when it wasn't worth the risk of a repeat failure or a safety issue. A candidate who always claims they do it "right" with no nuance may not be telling you the whole story.

3. Describe a lockout-tagout procedure you've followed. Walk me through it step by step.

You want specific, procedural knowledge, not a general statement that they "follow safety rules." A strong answer names the actual steps: identifying energy sources, isolating them, applying locks and tags, verifying zero energy state before starting work. A vague or generic answer here is a real flag for a role where a shortcut can seriously injure someone.

4. Tell me about a repair you attempted that you couldn't finish yourself. What did you do?

At a small operation, this happens regularly. You want a real story: what the limit was (needed a part, needed a license, needed expertise they didn't have), and how they handled the handoff, not whether they eventually muscled through it anyway. A candidate who can't produce a real example, or who describes pushing past their own expertise on something that needed a specialist, is a risk.

5. A machine is making a new noise but still running. Do you shut it down, or keep it running and monitor it? How do you decide?

Good answers describe real triage logic: what the noise suggests, what the consequence of a failure would be (safety risk, expensive damage, minor inconvenience), and whether there's a safe way to monitor it closely versus needing to stop immediately. Watch for candidates who give a blanket rule ("always shut it down" or "never stop production") instead of reasoning through the specific risk.

6. Walk me through your preventive maintenance routine for a piece of equipment you're responsible for.

This should come out as a real, ordered routine: what gets checked, how often, what triggers a closer look. A candidate who's vague here, or who describes maintenance as purely reactive ("I fix things when they break"), may not have owned a preventive maintenance program independently before, which costs you in unplanned downtime later.

7. Tell me about a time you found a problem that wasn't the one you were called in to fix.

This tests observation and initiative. A strong answer describes noticing something (a worn belt, a loose fitting, an early warning sign) while working on something else, and flagging or addressing it before it became its own failure. A candidate who's never noticed anything beyond the specific task in front of them may miss the small signals that prevent bigger breakdowns.

8. How do you keep track of what's been fixed, what parts you've used, and what's coming up for maintenance?

Good answers mention some kind of system, even an informal one: a logbook, a shared spreadsheet, a maintenance app. This matters more at a small operation than it sounds, because there's no team to absorb the knowledge if this person leaves or is out sick. A candidate who says they just remember it all, with no logging system, is a continuity risk.

9. Tell me about a time you had to explain a repair or a piece of bad news to someone non-technical, like a manager or a tenant.

This tests plain-language communication, which matters more than it sounds for a role that often reports up to someone without a technical background. Listen for clear, honest explanations without jargon, and for how they handled delivering unwelcome news (a repair will take longer, cost more, or require a shutdown). A candidate who gets defensive or evasive describing this may create friction with the people they report to.

10. Why are you interested in being the only maintenance person here, instead of joining a bigger team with more backup?

This surfaces whether they understand what they're signing up for. A strong answer names something real: more ownership, more variety, direct visibility into how the whole operation runs. A candidate who can't articulate a reason beyond "it was the job that was open" may be less prepared for the isolation and range of responsibility this role actually requires.

A scorecard you can score candidates against

Ten questions are only useful if everyone on your side is listening for the same thing. Score every candidate on the same six signals, so you're comparing evidence instead of comparing gut feelings from separate conversations. Copy this into a doc and fill in a row per candidate.

How to screen maintenance technician candidates without losing a week to it

Truffle is a candidate screening platform that combines one-way video interviews, talent assessments, and resume screening, so you can build a screening workflow around what actually matters for a role where resumes are often a weaker signal than the conversation itself.

Small-shop and facility maintenance hiring runs into a real pattern: strong candidates often learned the trade hands-on rather than in a classroom, and they don't always write a resume that reflects what they can actually do. Candidates in this world are also more likely to call, walk in, or follow up in person rather than navigate a long online application. Building a screening process that works for both, without losing good candidates to a clunky application flow, matters as much as the questions you ask.

A workflow that fits a small shop or facility hiring without a dedicated recruiter:

• Resume and application screening first, but don't over-weight polish. Cut the obvious mismatches on experience and licensing, but don't penalize a thin or plainly written resume from someone who's spent their career doing the work instead of writing about it.
• A short one-way video interview, not a live panel round, for your first real look. Ask 2-3 of the scenario questions above, like the diagnostic-process question or the lockout-tagout question, so you can hear how someone actually reasons through a problem, before you commit any live interview time.
• A short, practical skills check instead of a long take-home. Our mechanical ability assessment is built to be short and job-relevant: mechanical reasoning across levers, gears, hydraulics, and basic electricity, the kind of foundational skill this role needs on day one, without asking someone to burn an evening on a project.
• A real, live or in-person conversation only for the candidates who clear the first three steps. By the time you're talking live, you already know they can diagnose, communicate clearly, and clear a basic skills bar. The live conversation is for fit and judgment, not for finding out for the first time whether they can do the job.

Our resume screening and one-way video interview tools handle the first two steps in one place, with AI that surfaces your strongest matches against the criteria you set. You review the evidence and decide. It doesn't pick for you.

3 questions from the skills check we'd actually run for this role

A skills check only helps if it tests real mechanical reasoning, not memorized trivia. These three are pulled straight from Truffle's mechanical ability assessment, the assessment we'd point you to for this role. Try them yourself before you decide what "job-ready" means for your opening.

The point isn't these three questions. It's that a short, job-relevant skills check like this tells you in twenty minutes what a resume and a friendly interview can hide: whether someone actually understands the mechanical principles behind the repairs they claim to have made. Truffle's AI scores and surfaces the results against the bar you set. You still make the call on who clears it.

Common hiring mistakes for this role

Over-weighting resume polish for a trade where it's a weak signal. Strong maintenance candidates often learned hands-on and don't always translate that experience into a well-written resume. A thin or plainly written resume from someone who's genuinely done the work shouldn't be filtered out ahead of a real conversation and a skills check.

Not testing diagnostic process directly. A list of past repairs on a resume doesn't tell you whether someone diagnoses before acting or jumps straight to replacing parts. Ask the diagnostic-process questions directly, and listen for the order of operations, not just the eventual fix.

Treating safety procedure as a checkbox instead of testing real knowledge. Asking "do you follow safety procedures?" gets a yes from everyone. Asking someone to walk through an actual lockout-tagout procedure step by step separates real discipline from a rehearsed answer.

Building an online-only application process for a candidate pool that often applies differently. Skilled trades and manufacturing candidates commonly call, walk in, or follow up in person rather than navigating a long online form. A process with no path for that filters out strong candidates for reasons that have nothing to do with their ability to do the job.

Hiring someone who's only ever had backup and calling it "self-sufficient." A candidate who's only worked on a bigger maintenance team, with specialists to hand off anything hard, may struggle when they're the only technician and the next call is an outside contractor. Probe directly for how someone handles being stuck with no one to ask.