Salary vs Hourly for a Senior Technician: Decision Tree
Why this matters
Your best tech has been hourly for years, and either you or they are starting to ask whether it is time to move them to salary. Get this call right and you keep a senior person engaged, predictable, and paid in a way that matches what they actually do now. Get it wrong and you either hand out a raise disguised as a title change that quietly costs the tech money in a busy season, or you create a legal exposure by calling someone "salaried" who does not actually meet the standard for it. This is a structural decision, not a reward you hand out for tenure. Work through it in order.
Start here: is this role even eligible to be salaried?
This gates everything, before you get to whether it is a good idea.
- If the role is genuinely hands-on field work, diagnosing, repairing, installing, with no supervisory authority over other employees and no independent management-level discretion, the role is very likely non-exempt under wage and hour law regardless of what you call the pay. A "senior" title does not create an exemption. Calling this person salaried while still owing them overtime for hours over the standard workweek threshold is a common and expensive mistake.
- If the tech now supervises other techs, has real hire or fire input, or exercises independent judgment on business matters (running crews, managing a route, setting schedules for others), an exemption may genuinely apply. Confirm the specific test with an employment attorney or your state labor office before changing anything. This varies by jurisdiction and by the actual duties performed, not the job title.
- If you are unsure which bucket this is, do not guess. Misclassifying a non-exempt worker as exempt is one of the more commonly enforced wage violations in trade businesses, and it is retroactive once caught.
If the role is not exempt: salary can still work, structured correctly
Many shops want the predictability of a salary for a senior tech without the legal risk of treating them as exempt. This is possible.
- A salary for non-exempt employees is legal as long as overtime is still calculated and paid separately on hours over the standard threshold. The salary simply becomes the base the regular rate is calculated from, it does not replace the overtime obligation.
- If your senior techs' hours are fairly predictable week to week, a non-exempt salary with tracked overtime gives them the steady paycheck they want and you the compliance you need. This is often the actual answer people are looking for when they ask "should we salary our senior tech."
- If you cannot commit to tracking their hours accurately every week, do not move to salary yet. A salaried non-exempt arrangement without real time tracking is the exact setup that generates back-wage claims, because the assumption becomes "salary covers everything" and overtime quietly goes unpaid.
If exemption genuinely applies: weigh what you are trading
Assuming the legal test is met, salary and hourly trade different things.
| Factor | Hourly | Salary |
|---|---|---|
| Predictability for the tech | Varies with hours worked | Stable regardless of week-to-week swings |
| Predictability for the shop | Labor cost scales with hours | Labor cost is fixed per pay period |
| Incentive during a slow week | Tech's pay drops with them | Tech is protected, shop absorbs the cost |
| Incentive during a heavy week | Tech is compensated for the extra hours | Tech works the extra hours for no additional pay |
| Fit for the role | Straightforward field execution | Roles carrying real management or discretion |
If the senior tech is being asked to take on real responsibility, running a crew, training others, being the point person when you are unavailable, salary reflects that shift and rewards judgment, not just hours logged. If the role is still primarily "does the hardest jobs personally" with no management layer added, hourly plus a higher rate or a flat-rate structure usually serves both sides better, because the tech is still paid for the volume and difficulty of work they actually produce.
Watch for this specific trap: salary that quietly cuts pay
Run the math before you offer it, not after. Take the tech's actual recent hourly earnings, including any overtime they typically work, and compare it honestly to the proposed salary divided across the same period. If the salary comes out lower than what they have actually been earning hourly in a normal busy stretch, the tech will notice within a season, and it will read as a bait-and-switch even if that was never the intent. If the salary is a clear step up from their typical hourly earnings, including overtime, it lands as the promotion it is meant to be.
Making the change without losing them
However you land, walk through the actual numbers with the tech directly rather than presenting a flat offer.
- Confirm exemption status is correct for the role, in writing, before you announce anything.
- Show them a real comparison: their trailing average pay under the current structure against the new one, across a normal week and a busy week.
- Name what changed in the role, not just the pay, so the shift reads as recognition of added responsibility rather than an arbitrary switch.
- Put the new terms in writing and revisit them at a set point, since a role that grows further may need the structure to grow with it.
The bottom line
Do not let a title or a request start this decision. Start with whether the role legally qualifies as exempt. If it does not, either keep hourly or use a properly tracked non-exempt salary, never an untracked one. If it does qualify, salary makes the most sense once real management responsibility has been added, and only when the numbers show the tech coming out ahead in a normal working season, not just on a quiet week.
References
- U.S. Department of Labor, Wage and Hour Division, exemption tests under the Fair Labor Standards Act
- 29 CFR 541 (defining exemptions for executive, administrative, and professional employees)
- See related: FLSA Overtime Rules for Trade Businesses