44% of job seekers say they won't apply to a posting without a pay range listed. In the HVAC market — where the industry is short more than 110,000 qualified technicians and experienced techs have multiple offers competing for their attention — that number is closer to a guarantee. Write a posting without a salary, and a significant portion of your potential applicant pool never clicks apply.
The shortage changes the math for employers. Five years ago, you could post "competitive pay, great team" and get 30 applications. That doesn't work anymore. Experienced technicians are fielding calls from recruiters, getting poached by competitors, and comparing your listing to three others on the same board. If your posting looks like every other mediocre listing, you'll get what every other mediocre listing gets: applications from people who couldn't get hired anywhere else.
This guide covers what qualified HVAC technicians actually look for when they read a job posting — and the specific changes that move listings from ignored to applied.
What Technicians Actually Look for First
The order in which information appears in a job posting is not decorative. It determines whether a tech reads past the first two sentences.
Here's the sequence experienced techs follow when they scan a listing:
- Pay rate — If it's not there, many stop reading
- Job type — Residential, light commercial, commercial, refrigeration, or a mix
- Location — Specific city or service area, not just the company HQ
- Schedule and on-call expectations
- Benefits — Company vehicle, tool allowance, health insurance
- Requirements — Certifications and experience
Most employers write postings in the opposite order: company overview, long list of duties, requirements, qualifications, and then maybe a vague mention of compensation at the end. That structure made sense when employers held all the leverage. It doesn't reflect the current market.
A tech scanning your listing on a phone while sitting in his truck between calls will spend about eight seconds on it before moving to the next one. Salary in the first three lines keeps him reading. Salary buried after a paragraph of corporate mission statement means he's already on to the next listing.
Salary Transparency: The Non-Negotiable
The research here is consistent and, at this point, not particularly surprising.
72% of job seekers say they're less likely to apply when a posting doesn't list salary. 44% say they flat-out won't apply. And 84% believe companies that hide compensation are doing so specifically to reduce the candidate's negotiating power — which, fair or not, is what experienced technicians think when they see "compensation based on experience" with no number attached.
The phrase "competitive pay" is now understood by most working technicians to mean one of two things: the pay is average at best, or the employer doesn't want to commit. Neither interpretation makes a tech more likely to apply.
Beyond applicant behavior, job boards have moved in the same direction. Indeed now prioritizes listings with visible pay ranges in search results. A posting with a salary range gets more impressions than an identical posting without one. The algorithm and the job seeker are aligned on this.
What to do instead: Post a specific range. If you pay $28–$34/hr depending on experience, write "$28–$34/hr DOE." If you offer flat-rate or a draw-against-commission structure, explain the floor and what a mid-level tech realistically earns. A number — any specific number — is more credible than adjectives.
If you're worried about applicants anchoring to the top of the range: post the range anyway. The alternative is losing qualified applicants who assume the worst and move on.
Job Titles: What Technicians Search For
Your job title determines whether your posting shows up when a tech searches for work. It also signals immediately whether you know the industry or you're an HR department that copy-pasted a template.
Technicians search for specific things. "HVAC Technician," "HVAC Service Tech," "HVAC Install Tech," and "Refrigeration Technician" are how people look for work. "Field Service Associate — Climate Control Systems" is not.
A few specific rules:
Use standard titles. "HVAC Technician" and "HVAC Service Technician" are the two most searched terms. "Heating and Cooling Specialist" is not how anyone searches for a job, and it may get filtered out of job board algorithms as non-standard.
Specify the work type when relevant. "Commercial HVAC Technician" and "Residential HVAC Technician" signal to applicants that you know what you're hiring for and help filter for the right experience level. A technician who has spent ten years doing rooftop units on commercial buildings may not want a residential position, and vice versa. Clarity reduces mismatched applications.
Don't put salary, benefits, or urgency in the job title. "HVAC Tech Needed ASAP — Great Pay!" gets flagged as spam by job boards and reads as desperate to applicants. Keep the title clean. The description is where those details go.
Avoid internal company titles in the external posting. If you call the role "Level 2 Field Ops Tech" internally, the external title should still say "HVAC Service Technician." Your internal naming conventions are not searchable.
Benefits Worth Highlighting — And How to Write About Them
Benefits in HVAC are not soft perks. They have real dollar values, and experienced techs know what they're worth.
Company vehicle / take-home van This is frequently the first thing a tech asks about. A take-home van means no personal vehicle wear, no fuel costs for commuting, and the ability to start the first call from home rather than from the shop. Depending on commute length, that's worth $3,000–$8,000 per year in saved vehicle expense. Write it as: "Take-home company van — fully stocked and fueled." Not just "company vehicle provided."
Tool allowance The standard range is $500–$2,000 per year. A tech buying their own tools spends real money each year on replacements, upgrades, and specialty equipment. Specify the amount and whether it's an annual allowance or company-owned tools. "$1,500 annual tool allowance" means something. "Tool support available" means nothing.
Paid training and certification reimbursement NATE certification costs several hundred dollars to prepare for and sit. EPA 608 is cheaper but still requires study materials and a testing fee. Offering paid training time and reimbursement for certification exams is a concrete benefit — write the dollar value if you can. "We pay for NATE prep and testing" is stronger than "advancement opportunities."
Health insurance State the employer contribution percentage, not just "health insurance offered." "Company pays 80% of individual health premiums" gives a tech something to evaluate. "Competitive benefits package" does not.
401(k) matching The standard in the industry is 3–5% match. If you match at or above that level, say so. "4% 401(k) match" is a concrete differentiator. "Retirement benefits" is not.
PTO and holiday schedule How many days from day one, and how many paid holidays. Technicians working in busy seasons want to know when they can take time off without penalty.
The goal is to translate benefits into their economic value. You're not selling perks — you're communicating total compensation. A $26/hr base with a take-home van, $1,500 tool allowance, and 80% health premium coverage is a better offer than a $28/hr base with no vehicle and self-paid insurance. Write the posting in a way that makes that math visible.
Red Flags That Make Techs Skip Your Listing
Experienced technicians have read thousands of job postings. They've learned to read between the lines, and certain phrases function as filters — not filters that attract candidates, but filters that tell them to move on.
"Competitive pay" with no number This is the most common and most damaging phrase in HVAC job postings. It has become industry shorthand for "we don't want to tell you." Techs who see this assume the pay is at or below market, because employers who pay above market generally want you to know that.
"Fast-paced environment" In residential HVAC, this often means they're running techs on six or seven calls per day with inadequate time at each job. Techs who have burned out at high-volume shops recognize this phrase and avoid it. If your shop runs efficiently and expects reasonable productivity, describe that instead.
"Must be a team player" Meaningless in any job listing. It signals that the posting was written by someone who copied phrases from a generic template. Specific descriptions of how the team actually works are more useful and more credible.
An enormous requirements list A posting that requires 10 years of experience, EPA 608, NATE certification, a clean MVR, commercial refrigeration experience, VRF system experience, and a specific equipment brand certification will get fewer applications than one that lists the actual baseline for the job. Requirements inflation happens when multiple positions get merged into one posting, or when someone lists every possible skill without considering which ones are actually needed to start. Separate the required skills from the preferred ones, and keep the required list short.
No location specifics "Greater Phoenix area" tells a tech almost nothing about whether the job involves a reasonable commute or driving 90 minutes to a job site. Name the service area, the primary shop address, or the territory. Technicians have lives outside of work and will skip a listing if they can't assess whether the geography works.
On-call without specifics Every tech knows that on-call is part of residential and commercial service work. What they want to know is how often, how it rotates, and whether it pays. "On-call required" with no additional context is a red flag. "Rotating on-call schedule, one week every six weeks, with a $X on-call premium" is information they can evaluate.
How to Structure a Posting That Converts
Here's the structure that works — tested against what technicians say they look for and what employers report getting the best response rates on.
1. Job title — Standard and searchable. "HVAC Service Technician — Residential."
2. Pay rate — in the first three lines. This is non-negotiable. "$28–$34/hr depending on experience" or "Flat-rate with guarantee floor of $XX,XXX/yr."
3. Key benefits — bulleted, in the second paragraph. Company van, tool allowance, health insurance contribution, 401(k) match. Four to six lines maximum. Don't bury these.
4. What the job actually involves. Type of work (residential service, light commercial maintenance, installs), the approximate call volume or project load, whether there's commercial work mixed in. Be specific. "Approximately 4–6 service calls per day, primarily residential repair with some light commercial maintenance" is infinitely better than "perform HVAC maintenance, repair, and installation as needed."
5. Schedule and on-call. Hours, start time, whether weekends are required, how on-call rotates.
6. Requirements — short and honest. EPA 608 if required. State license if required by law. Experience in years. Keep this to the actual baseline, not the wish list.
7. How to apply. Clear instructions. If you want a resume, say so. If you want them to call, give the number. A vague "apply online" with a broken link is more common than it should be.
The whole thing should be readable in two to three minutes. A posting that requires ten minutes to parse is a posting that doesn't get read.
The Difference Between a Good and Bad Posting
Here's the same job written two ways.
Poor version:
XYZ HVAC Services is a locally owned heating and cooling company serving the greater metro area for over 25 years. We are currently seeking a motivated self-starter to join our growing team. The ideal candidate will be a team player with strong communication skills and the ability to work in a fast-paced environment. Compensation is competitive and commensurate with experience. Benefits available after 90 days.
Better version:
$28–$34/hr | Take-home van | $1,200 tool allowance | 80% health premium
We're a residential and light commercial shop with 12 techs covering the north Phoenix metro. You'll run 4–5 service calls per day, primarily cooling repairs and maintenance with some installs in spring. Take-home van is fully stocked — you start the first call from home. EPA 608 required. NATE preferred but we'll pay for it. On-call rotates one week in six with a $200 weekly premium.
The second version is shorter. It leads with everything the tech wants to know. It gives specific details that signal you run an organized operation. It treats the applicant as someone whose time has value.
Common Mistakes to Fix Before You Post
A quick checklist before submitting any HVAC job posting:
- Salary is visible in the first three lines — not at the bottom, not "see application"
- Job title is a standard searchable term — no internal jargon, no creative naming
- Service area is named specifically — city, territory, or shop address
- Benefits have dollar values where possible — not "great benefits"
- Requirements list is realistic — required vs. preferred are separated
- On-call is described — frequency, rotation, and whether it pays a premium
- Company van policy is explicit — take-home or shop vehicle, who pays for fuel
- Application process is clear — one specific action, not three ambiguous options
Fix these before you post and you'll be ahead of the majority of HVAC job listings on any board.
Frequently Asked Questions
Should I post a salary range or a flat rate in my HVAC job posting? Either works, but post a specific number. A range ($28–$34/hr) signals flexibility while giving techs something to evaluate. A flat rate ($31/hr) is clean and transparent. "Competitive pay" without a number is the option that gets the fewest qualified applications.
How long should an HVAC job posting be? Three to five paragraphs is the target. Enough to cover pay, benefits, the actual job, schedule, and requirements — not so long that a tech scanning it on a phone gives up. If you need more than 600 words to describe the position, you're probably including information that belongs in the interview, not the posting.
What job title should I use to get the most applications? "HVAC Service Technician" and "HVAC Technician" are the two highest-search-volume titles. Add a qualifier if the work type matters: "Residential HVAC Technician" or "Commercial HVAC Technician." Avoid internal company titles and creative naming.
Do I need to list all required certifications in the job posting? List the ones that are genuinely required on day one. EPA 608 certification is legally required for handling refrigerants, so that's a hard requirement worth stating. NATE is a preference for most shops — if you'll hire without it and train toward it, say that. Long certification lists discourage otherwise qualified applicants who assume they won't qualify.
Does a company vehicle make a meaningful difference in applications? Yes, consistently. A take-home van is one of the most-cited benefits by HVAC technicians evaluating job offers. It has a real dollar value ($3,000–$8,000+ per year in saved vehicle costs depending on commute distance) and signals that you run a professional operation. If you offer it, lead with it.
What does "fast-paced environment" signal to experienced technicians? Usually that the shop runs too many calls per day or has high turnover. Techs who have worked in those environments recognize the phrase and often pass. If your pace is reasonable, describe it specifically — "4–5 calls per day" tells them more than any descriptor.
Should I require NATE certification for entry-level positions? Probably not. NATE is meaningful but not universal at entry level. Requiring it for technicians who are otherwise qualified will reduce your applicant pool without improving the quality of your hires. A better approach: list it as preferred, and offer paid training and exam reimbursement as a benefit.
What's the best way to describe on-call requirements without scaring off applicants? Specificity is your friend here. "Rotating on-call, one week in every six, with a $200/week on-call premium" is something a tech can plan around. "On-call as needed" is open-ended in a way that suggests it could be frequent and unpredictable. Most techs accept reasonable on-call; what they resist is ambiguity.
The technician shortage means experienced techs are reading your posting with at least two or three competing offers in mind. The listings that get responses are the ones that answer the three questions a tech asks in the first eight seconds: How much does it pay? What kind of work is it? Is this shop worth my time?
Put the salary in the first line. List the van and tool allowance in the second paragraph. Keep the requirements honest. That's the whole formula. You can post a job on HVACJobs.IO in under ten minutes — the structure above is built into the posting form so you're not starting from a blank page.