Skills-Based Hiring for Small Businesses: A Practical Guide
Skills-based hiring helps small businesses hire for ability, not degrees. How to implement it without an ATS, a recruiter, or assessment software.
Skills-Based Hiring
How to hire for ability instead of degrees at a small business, without an ATS or recruiter on staff
A bachelor's degree in business administration does not teach someone how to manage your inventory, respond to your customers, or use your POS system. But "bachelor's degree required" is still the default filter on most job posts, and it eliminates candidates who could do the job perfectly well. Skills-based hiring removes that filter and replaces it with a better one: can the person actually do the work?
Every guide about skills-based hiring is written for enterprise HR teams with assessment platforms, competency frameworks, and dedicated talent acquisition departments. If you run a small business and the "HR department" is you, those guides are not useful. You do not need a skills taxonomy or an AI-powered assessment tool. You need a practical way to write job posts that attract capable people regardless of their degree, a set of interview questions that test real skills, and a scoring method that removes gut-feel from hiring decisions.
This guide covers how to implement skills-based hiring at a small business, without an ATS, without assessment software, and without a dedicated recruiter. It also covers the step that every skills-based hiring guide ignores: what happens after you hire someone based on skills instead of credentials, and how to structure their first 90 days to close whatever gaps exist.
What Is Skills-Based Hiring?
Skills-based hiring is the practice of evaluating job candidates based on their demonstrated abilities rather than traditional credentials like degrees, years of experience, or previous job titles. Instead of requiring "bachelor's degree in marketing," a skills-based job post says "can write clear copy, analyze campaign data, and manage a content calendar." Instead of filtering resumes by school name, you filter by whether the candidate can demonstrate the 3 to 5 skills the role actually requires.
The concept is not new, but the adoption has accelerated. According to Bureau of Labor Statistics employment projections (2025 to 2035), close to 70% of US employment sits in occupations whose typical entry-level education is less than a bachelor's degree. Employers still list one anyway, out of convention rather than necessity.
The professional bodies have caught up with the practice. SHRM now publishes a skills-first hiring toolkit aimed at transforming talent acquisition. The label matters less than the method, but it does mean the job-post language you are about to write now has an accepted name behind it.
Competency-Based, Skills-First, and Merit-Based Hiring
Four labels circle the same idea, and the differences are worth thirty seconds. Skills-based hiring tests specific abilities. Competency-based hiring adds the behaviors around them, such as how someone handles conflict or an unclear brief. Skills-first is the label the professional bodies now use for the same practice. Merit-based hiring is the principle underneath all three: choose on ability rather than on connections or pedigree.
| Term | What it evaluates | What it looks like at a small business |
|---|---|---|
| Skills-based hiring | Specific testable abilities: reconcile a ledger, write the brief, use the CRM | A 15-minute task plus a 1 to 5 rubric on the 3 to 5 skills you named |
| Competency-based hiring | Those skills plus the behaviors around them: judgment, ownership, adaptability | Two behavioral questions added to the same scorecard, scored on the same scale |
| Skills-first hiring | The same practice under a newer label | Nothing different to do. Expect the phrase in job post templates and vendor decks |
| Merit-based hiring | The principle: ability over connections, appearance, or where someone studied | The rubric is the enforcement mechanism, because it makes ability the record of the decision |
Merit is where the argument usually turns political, and the practical answer is dull. A written rubric applied identically to every candidate is what makes a claim of merit checkable rather than asserted, and it is the same instrument that widens the pool: someone who never had a degree to lose still gets scored on what they can actually do.
Why Skills-Based Hiring Works Better for Small Businesses Than Enterprises
Enterprise companies adopted skills-based hiring after the big consultancies packaged it as a transformation program. Small businesses have been doing it intuitively for decades because they never had the luxury of requiring credentials they did not need. When you need someone who can manage your books, you hire the person who demonstrates they can manage books, regardless of whether they have a CPA or a degree in accounting.
The advantage small businesses have: you do not need to dismantle a 20-year-old HR infrastructure to implement skills-based hiring. You do not have an applicant tracking system that auto-rejects candidates without degrees. You do not have a corporate policy manual that requires "bachelor's degree minimum" for every salaried role. You can simply rewrite your next job post to list skills instead of credentials and start interviewing differently. The entire implementation takes one hiring cycle, not a multi-year transformation program.
| Factor | Enterprise Adoption | Small Business Adoption |
|---|---|---|
| Implementation time | 12-24 months (policy changes, ATS reconfiguration, manager training) | 1 hiring cycle (rewrite the JD, change the interview) |
| Software required | A skills assessment platform subscription, plus ATS reconfiguration | None (spreadsheet scoring rubric is enough) |
| Stakeholder buy-in needed | CHRO, legal, hiring managers across divisions | The founder decides and it is done |
| Biggest obstacle | Institutional inertia and risk aversion | Writing the JD differently (a 30-minute task) |
| Competitive advantage | Moderate (competitors are doing it too) | High (most small business competitors still require degrees by default) |
6 Benefits Skills-Based Hiring Delivers for a Small Business
| Benefit | What It Looks Like at a Small Business | Supporting Evidence |
|---|---|---|
| Wider talent pool | Your customer service role gets 40 applicants instead of 12 because you removed the degree requirement | Census Bureau: 40.1% of women and 37.1% of men age 25 and over hold a bachelor's degree or higher |
| Better job-skill match | You hire someone who can actually use your CRM, not someone who studied marketing theory in college | Gallup: most people need 12 months or more to get up to speed in a new job, so a head start on the core task compounds |
| Lower cost per hire | Fewer days to fill means fewer days of lost productivity. Referrals from non-traditional networks cost less than premium job boards. | SHRM: average cost per hire is close to $4,700 in recruiting spend alone |
| Higher retention | Candidates hired for skills they actually have are less likely to discover a mismatch in month 2 | Work Institute: over a third of new hires quit within the first year, most often because the job did not match expectations |
| Improved diversity | Removing degree requirements brings in candidates from non-traditional backgrounds who were filtered out by credential gates | EEOC: a screen that rejects one protected group at a higher rate has to be job related and consistent with business necessity, a standard a degree line kept out of habit struggles to meet |
| Faster hiring process | One 15-minute skills task replaces three rounds of resume screening. You know who can do the job before the interview. | Gallup (2023): 25% of employees named turnaround time as the biggest influence on accepting an offer, aside from pay |
How to Implement Skills-Based Hiring Without an ATS or Recruiter
You do not need assessment software, a competency framework, or a skills taxonomy. You need 7 changes to your existing hiring process, and most of them take less than 30 minutes.
Designing the 15-Minute Skills Task
Step 4 is one sentence, and almost everything that goes wrong with skills-based hiring goes wrong inside it. A badly designed task tells you who is good at taking tests. A well designed one tells you what the person will actually produce in week 2. Three rules separate the two.
Rule 1: use a sample, not a proxy. A sample is a shrunken version of real work, using your tools and your kind of data. A proxy is anything that correlates with the work in theory: logic puzzles, brainteasers, personality quizzes, timed typing tests for a role that is not time-pressured. Proxies are easier to write and they are the reason candidates complain that assessments are pointless. If you cannot point at a line in the job description that the task is testing, cut it.
Rule 2: write the rubric before you send the task. Decide what a 1, a 3 and a 5 look like while you still have no submissions in front of you, because after the first submission arrives your rubric will quietly reshape itself around it. For a ledger reconciliation with three planted mismatches: 5 means they find all three and flag the ambiguous one as a question rather than deciding it themselves; 3 means they find two; 1 means the sheet balances because they plugged a number.
Rule 3: send it to a shortlist, not the funnel. Forty applicants at eight minutes of review each is more than five hours of your time, and it burns goodwill with 32 people you were never going to hire. Six to eight candidates is about an hour of review and is honest about where they stand: everyone who receives the task is genuinely in contention.
| Role | 15-Minute Task | What You Are Scoring | What a 1 Looks Like |
|---|---|---|---|
| Bookkeeper | Reconcile a 30-line sample ledger against a bank statement. Three entries do not match. | Accuracy, and whether they flag ambiguity instead of resolving it silently | The sheet balances because they entered an adjusting figure with no note |
| Customer support | Reply to two customer emails. One is a refund request that falls outside your stated policy. | Tone, whether they can say no clearly, whether they know when to escalate | They paste the policy language back at the customer with no alternative offered |
| Marketing coordinator | Here is last month's campaign data. Five sentences on what you would change and why. | Whether they read the numbers before recommending anything | Generic advice ('post more often') that would fit any dataset |
| Operations / admin | Eight tasks, three of which conflict. Give today's order and say what slips. | Prioritization and willingness to name a trade-off | An ordered list with nothing dropped and no acknowledgment of the conflict |
| Sales | Draft the voicemail and the follow-up email for this inbound lead (real product, fake company). | Whether they lead with the customer's problem or the product | A feature list with a request for a meeting attached |
The obvious objection now is that a candidate can hand any written prompt to a chatbot. Do not try to detect that; detection tools are unreliable and accusing a good candidate is unrecoverable. Do two things instead. Build the task out of artifacts that are specifically yours (your ledger format, your refund policy, your campaign numbers), which makes a generic answer visibly generic. Then spend the first five minutes of the interview on the submission: "Walk me through why you flagged the third entry," or "What would you have done if that number had been off by $4 instead of $400?" Someone who did the work answers immediately. Someone who did not will describe their submission in the same general terms they would use for anyone else's.
All three rules fit on one page, and that page has to exist before the first task goes out. Fill it in once per role: the task as the candidate will read it, the line tying each part of the task to a duty in the job description, the three rubric anchors, and the wording of the invitation. It takes about twenty minutes and it is the same page you would hand over if anyone later asked why a candidate was screened out at this stage.
Skills-Based Interview Questions for Small Business Hiring Managers
Traditional interview questions ("tell me about yourself," "where do you see yourself in 5 years") do not test skills. Skills-based questions ask the candidate to demonstrate or describe the specific ability you need. Here are examples by skill type.
| Skill Category | Question | What a Good Answer Sounds Like |
|---|---|---|
| Problem-solving | 'Walk me through how you would handle [specific scenario from the role].' | They ask clarifying questions, break the problem into steps, and explain their reasoning. They do not give a generic answer. |
| Technical proficiency | 'Here is [tool/system]. Show me how you would do [specific task].' | They navigate the tool with minimal guidance. Speed matters less than approach. Watch for whether they ask for help vs guess. |
| Communication | 'Write a response to this customer complaint in 5 minutes.' | Clear, empathetic, resolves the issue, appropriate tone. Grammar matters less than clarity and customer orientation. |
| Organization | 'You have these 8 tasks. Walk me through how you would prioritize them for today.' | They distinguish urgent from important, group related tasks, and explain trade-offs. There is no single right answer, but a wrong answer is 'I would just start at the top.' |
| Leadership | 'Tell me about a time you had to get a team member to change their approach to something.' | They describe the situation specifically, explain what they did (not what they 'would' do), and share the result. Vague answers mean vague experience. |
The key principle: every question should test a skill from the 3-5 you identified in Step 1. If a question does not map to a required skill, remove it from the interview. Fewer, better questions produce better signal than 20 generic ones.
Skills Tests Are Selection Procedures: The Legal Guardrails
The moment you add a scored task or a scored interview, you have built what the EEOC calls a selection procedure, and it sits under the same rules as any other employment test. The Uniform Guidelines on Employee Selection Procedures (29 CFR Part 1607) cover any procedure used as a basis for an employment decision, including work samples, structured interviews, and even the resume screen you were already doing. A skills test is not automatically safer than a degree requirement. It is safer only when it is job-related, and only when you can show that it is.
Adverse impact is the mechanism to understand. It does not require that anyone intended to discriminate. It asks whether a neutral-looking screen rejects one group at a meaningfully higher rate than another.
The Uniform Guidelines use the four-fifths rule as the rough flag: a selection rate for any race, sex, or ethnic group that falls below 80% of the rate for the highest-passing group is generally treated as evidence of adverse impact.
Run the arithmetic once: of 20 candidates from one group, 12 clear the bar, a 60% pass rate. Of 15 candidates from another group, 6 clear it, a 40% rate. That is 40 divided by 60, or 67%, under the 80% mark.
At small-business volumes those samples are far too small to mean anything statistically, and no one is running a regression on your six applicants. But your exposure does not scale down with your headcount, and the defense is not a bigger sample.
Documentation is the defense: one written line connecting each element of the task to a duty in the job description, the identical task and rubric for every candidate at that stage, and the scored sheets kept on file.
That file is also a legal obligation. EEOC recordkeeping rules require covered employers to preserve application and selection records for one year from the date of the record or the personnel action, whichever is later (29 CFR 1602.14), and to hold everything until resolution once a charge is filed. Federal contractors keep records longer.
Two thresholds people get wrong. Title VII and the ADA apply at 15 or more employees and the ADEA at 20 or more, so a 9-person company sits outside those three statutes. The Equal Pay Act has no headcount threshold at all and applies from the first employee.
State law is where most small employers are actually reached. Most states run their own fair-employment laws at far lower headcounts, several of them from the first employee, and those state agencies handle the majority of small-employer charges. "We are too small to be covered" is rarely true.
The ADA also applies to the assessment itself. Say in the task invitation that accommodations are available and give a contact, allow alternate formats and extra time on request, and keep the exercise a work sample rather than a personality or psychological instrument, which can drift into medical-examination territory that is prohibited before an offer.
One more reason the spreadsheet rubric is the right tool at this size: it stays outside the fastest-moving area of hiring law. Once a vendor tool scores, ranks or screens candidates for you, a growing set of state and city rules attach.
Four jurisdictions show the shape of it. New York City's Local Law 144 requires a bias audit completed within the past year, publication of a results summary, and notice to candidates at least 10 business days before the tool is used on them.
Illinois's Artificial Intelligence Video Interview Act requires notice, a plain explanation of what the AI evaluates, consent, and destruction of the video within 30 days of a candidate's request. Public Act 103-0804 went further on January 1, 2026, making it a civil rights violation under the Illinois Human Rights Act to use AI that discriminates on a protected basis, or to use zip codes as a proxy for one.
Maryland sits at the narrower end of the same trend. State law bars an employer from running a facial recognition service during an applicant's interview unless the applicant signs a plain-language consent waiver naming the applicant and the interview date.
Colorado shows how fast this moves. Senate Bill 26-189, signed May 14, 2026, repealed the state's 2024 AI Act before it ever took effect and replaced it with a narrower law effective January 1, 2027: notice before a consequential decision, disclosure within 30 days of how the system influenced an adverse one, and a right to human review.
The list changes every legislative session, so confirm what applies in the states you hire in before you buy assessment software. None of it attaches to a human reading a scored sheet.
Skills-Based Hiring vs Traditional Hiring: What Changes?
| Stage | Traditional Hiring | Skills-Based Hiring |
|---|---|---|
| Job post | 'Bachelor's degree required, 3+ years experience' | 'Must be able to [skill 1], [skill 2], [skill 3]. Degree not required.' |
| Resume screening | Filter by degree, school name, company prestige | Filter by application question responses and skills task results |
| Interview | Unstructured conversation, gut-feel evaluation | Structured questions mapped to required skills, scored 1-5 |
| Evaluation | 'I liked candidate A better' (subjective) | 'Candidate A scored 4.2/5 on required skills, B scored 3.6' (objective) |
| Offer decision | Based on credentials and rapport | Based on demonstrated ability and scoring data |
| Onboarding | Same generic process for everyone | Tailored to close specific skill gaps identified during hiring |
The shift is not radical. You are not reinventing hiring. You are replacing one filter (credentials) with a better one (demonstrated skills) and adding one tool (a scoring rubric) that makes decisions more objective. Everything else in the hiring process stays the same: you still post jobs, screen candidates, interview, and make offers.
4 Common Mistakes Small Businesses Make With Skills-Based Hiring
Mistake 3 is the one most companies discover too late. You hired someone who can do the work but has never used your specific tools, your specific processes, or your industry's specific terminology. A degree-holder might have learned those things in school. A skills-based hire needs them delivered through onboarding. This is not a weakness of skills-based hiring. It is a design requirement.
When the Credential Stays
Skills-based hiring replaces one filter with a better one. It does not mean credentials never matter, and the roles where they do are not always the obvious ones. Four categories where the credential is load-bearing and cannot be swapped for a work sample.
| Category | Examples | Why It Cannot Be Dropped |
|---|---|---|
| Occupational licensure | CDL drivers, electricians and plumbers, nurses and allied health, cosmetologists, insurance producers, CPAs signing attest work | State law makes the license a condition of performing the work. Unlicensed practice is the employer's problem too, not only the worker's. |
| Regulator-mandated certification | Powered industrial truck (forklift) operator certification under 29 CFR 1910.178(l), DOT driver qualification files, food-safety manager certification where the local health code requires one on site | The citation lands on the business at inspection, and the training record is the only proof it happened. |
| Contract and insurance terms | Client master service agreements specifying degreed personnel, government contract labor categories, professional liability and E&O underwriting questions, bonding requirements | Dropping the requirement can breach a term you already signed or void coverage you are paying for. Read the contract before you rewrite the JD. |
| Immigration sponsorship | Any role you intend to fill with an H-1B beneficiary | The specialty occupation standard requires a bachelor's or higher in the specific specialty (or its equivalent) as the normal minimum for entry. A job description that says the degree is not required undercuts the petition for that role. |
Two of those rows carry a citation worth keeping to hand. Forklift operators must be trained, evaluated in the workplace, and certified by name and date before they operate independently (29 CFR 1910.178(l)), and an H-1B specialty occupation is one where a US bachelor's or higher degree in a directly related specialty, or its equivalent, is normally the minimum entry requirement.
There is also a payroll consequence that catches people after the hire. Exempt status turns on duties, not diplomas, with one significant exception: the learned professional exemption specifically requires advanced knowledge in a field of science or learning customarily acquired by a prolonged course of specialized intellectual instruction (29 CFR 541.301).
The regulations do allow for equivalence attained through a combination of work experience and intellectual instruction, but the path is narrow and rarely the safe answer. If you hire a non-degreed candidate into a role you had been classifying as an exempt learned professional, re-run the duties test rather than assuming the classification carries over.
The administrative or executive exemption may fit instead, or the role may simply be nonexempt and owed overtime. The federal salary level for the white-collar exemptions is $684 a week ($35,568 a year), and several states set a higher one, including California, New York, and Washington.
Finally, the half-measure most companies land on: "bachelor's degree or equivalent combination of education and experience." It usually keeps the filter fully intact, because nobody has defined what equivalent means and the person screening resumes defaults to the degree. If you keep the phrase, define it in the same sentence ("or three years running a month-end close") so the screener has something to apply. Better still, take the credential out of the requirements list and give it its own line that says which of three things it actually is: required by law, required by a contract you signed, or preferred. Only the first two are non-negotiable, and most job descriptions have never made the distinction.
Run that as an audit on a posting you already have rather than as a rewrite from scratch. Copy the requirements list into the sheet one line per row, name the source you could point to for each, and let the empty source cells show you which requirements were never anything but habit.
| A | B | C | D | E | F | G | H | |
|---|---|---|---|---|---|---|---|---|
| 1 | Requirement as currently written | Category | Source you can point to | What the work actually needs | Rewritten line for the job post | What 'or equivalent' means, spelled out | Decision | Reviewed by and date |
| 2 | Example row, replace it with a line lifted from your current posting | required by law / required by a contract / preferred | Name the license, regulation, or contract clause. An empty cell here means the requirement is preferred. | The task in the role this requirement was standing in for | The line you will actually publish | Three years running a month-end close, for instance | keep / rewrite / remove | [initials, date] |
| 3 | ||||||||
| 4 | ||||||||
| 5 | ||||||||
| 6 | ||||||||
| 7 | ||||||||
| 8 | ||||||||
| 9 | ||||||||
| 10 | ||||||||
| 11 |
What Happens After the Hire: The Step Everyone Skips
Skills-based hiring changes who you hire. It does not change the fact that every new hire needs structured onboarding to become productive. In fact, skills-based hires may need more intentional onboarding because they bring demonstrated ability without the academic baseline that degree-holders have.
The practical fix: before the new hire starts, identify 2 to 3 specific gaps between what they demonstrated in the interview and what the role requires in its first 90 days. Build those into the onboarding plan as structured learning blocks (not "figure it out on your own"). Example: you hired a marketing coordinator who aced the content writing task but has never used your specific analytics tool. Week 2 onboarding includes 2 hours of analytics tool training with a mentor, not a 30-second "here's your login."
I built FirstHR for exactly this handoff. The AI onboarding wizard generates a structured plan based on the role, and you can customize it to address the specific skill gaps you identified during hiring. Training modules deliver the learning. Task workflows ensure nothing is missed.
The result is a skills-based hire who is productive by Day 30 instead of still figuring things out by Day 60. The Work Institute reports that over one third of newly hired employees quit within their first year, and that the reason given most often is what the job turned out to be, not pay.
Frequently Asked Questions
What is skills-based hiring?
Skills-based hiring is the practice of evaluating candidates based on demonstrated abilities and competencies rather than traditional credentials like degrees, certifications, or years of experience at specific companies. Instead of requiring a bachelor's degree, a skills-based job post lists the specific skills the role requires (data analysis, project management, customer communication) and evaluates candidates through work samples, skills assessments, or structured interviews that test those abilities directly.
Is skills-based hiring effective?
Yes, when it is run as a process change rather than a job-post edit. The case for it starts with arithmetic. Census Bureau figures for 2024 put bachelor's attainment at 40.1% for women and 37.1% for men age 25 and over, so a degree line removes most American adults from consideration before anyone reads a resume. Matching people to the duties they will actually perform also cuts the mismatch that drives early exits, which the Work Institute identifies as the reason new hires most often give for leaving in year one. For a small business competing against larger employers for the same candidates, dropping an unnecessary credential gate is the cheapest way to widen the field.
How do I evaluate skills without a degree to verify?
Three practical methods: (1) A short work sample or task that simulates real job activities (15-20 minutes, not a full project). (2) Structured interview questions that ask candidates to describe how they have used specific skills in past work. (3) A simple skills rubric where you score each candidate 1-5 on each required skill during the interview. You do not need assessment software for this. A Google Sheet with 5 skills and a 1-5 scale works for most small businesses.
Does skills-based hiring mean I cannot require any credentials?
No. Skills-based hiring means removing unnecessary credential requirements, not all requirements. If a role legally requires a license (nursing, electrical work, CDL driving), that credential stays. If a role requires 'bachelor's degree in business administration' but the actual work is managing schedules and responding to customer emails, that degree requirement is the filter you remove. The test: does this credential directly predict job performance, or is it a proxy for skills you could test directly?
What jobs are best suited for skills-based hiring?
Skills-based hiring works best for roles where performance depends on demonstrable abilities rather than theoretical knowledge: customer service, sales, marketing, operations, administrative support, IT support, project coordination, bookkeeping, and most entry-to-mid-level positions. It works less well for roles that legally require credentials (licensed trades, healthcare, legal, finance) or roles where domain-specific academic knowledge is genuinely necessary (research science, engineering design).
Do I need special software for skills-based hiring?
No. Enterprise companies buy dedicated skills assessment platforms, and small businesses do not need one. You need three things: a job description that lists skills instead of degrees, 3-5 structured interview questions that test those skills, and a simple scoring rubric in a spreadsheet to compare candidates objectively. The total cost of implementing skills-based hiring at a small business is zero dollars in software. What it does cost is attention. Someone has to write the task, write the rubric before the first submission arrives, and score every candidate against the same sheet. That is the work a platform would otherwise structure for you, and at small-business volumes it runs to about an hour per role rather than a subscription.
How does skills-based hiring affect diversity?
It widens the field, and the legal framing matters more than the label. A degree requirement is a neutral-looking screen, and under EEOC guidance any screen that rejects one protected group at a higher rate has to be job related and consistent with business necessity. A degree line kept out of habit rather than need struggles to meet that standard. Removing it brings in career changers, self-taught professionals, community college graduates, and veterans who were filtered out before anyone looked at what they could do. For a small business, that is a practical expansion of the candidate pool in a tight labor market.
Can I still require years of experience?
Years of experience is the same kind of proxy as a degree: it measures exposure, not ability. '5+ years required' filters out fast learners and career changers while admitting people who repeated year one five times. It also carries age-discrimination risk when it runs in the other direction, since caps like 'no more than 3 years' or calls for 'recent graduates' signal an age preference under the ADEA. Use experience as a rough floor only where the work genuinely depends on pattern recognition you cannot build quickly, such as a controller who has closed the books through an audit. State it as a range rather than a hard gate, and let the skills task override it: a candidate with two years who scores 5 on the task is a better hire than one with eight years who scores 3.
Do I have to pay a candidate for a work sample?
It depends on whether the work benefits you. A simulated exercise built on synthetic data, where the output is discarded, is a selection procedure and is not compensable. If the candidate produces something you actually use, such as a real client deliverable, live data entry, or a shift working alongside your staff, that time is arguably compensable under the FLSA and you owe at least minimum wage for it. The practical rule: keep the task fictional, keep it short, and if you want someone to do real work before an offer, pay a stated stipend or run it as a paid trial shift with the payroll paperwork that implies. Some states also have their own rules on reporting-time pay for anyone who shows up on site.
What is the difference between skills-based hiring and competency-based hiring?
The terms are closely related but not identical. Skills-based hiring focuses on specific, testable abilities (can you use Excel, can you write SQL, can you manage a project timeline). Competency-based hiring is broader and includes behavioral traits and organizational fit (leadership, adaptability, collaboration). In practice, most companies use both: they test for specific skills and evaluate competencies through behavioral interview questions. For small businesses, the distinction is academic. Focus on identifying the 3-5 things the person needs to do well and test for those directly.