Professional Services Engineer Job Description Templates
6 templates for the people who turn a signed contract into a working deployment: core delivery, senior, integrations, on-site, managed retainer, and contract. Download as DOCX.
The first professional services engineer I ever hired spent his first month doing a job nobody had written down. We had signed four customers who could not get to production on their own, and somebody had to sit between the sales promise and the product reality. The job description I posted was two paragraphs long and described almost none of it.
That posting is why we hired slowly and why the first candidate we liked took a different offer. A services engineer reads a job description for signal about how the company runs: how many accounts, how much travel, whether scope is defended, whether time gets logged. Vagueness on those four points reads as a company that has not decided, and experienced delivery people have been burned by that before.
At FirstHR we publish hiring templates for small companies without a dedicated HR function. The six below cover the core delivery seat, a senior strategic-account version, an integrations specialist, on-site deployment, managed retainer delivery, and a fixed-term contract engagement, each with the classification note the generic versions leave out.
TL;DR
A professional services engineer takes a signed customer from kickoff to production: scoping, configuration, integrations, data migration, training, and handoff. The role is not automatically exempt, because the computer employee exemption needs qualifying duties on top of a $684 weekly or $27.63 hourly pay test. No BLS occupation matches the title, so benchmark against nearby classifications. Six templates below, downloadable as DOCX.
What the Role Actually Delivers
A professional services engineer converts a signed contract into a working deployment. The scope runs from technical discovery through configuration, integration, data migration, training, and a documented handoff, and it ends when the customer is in production rather than when the software is installed.
What the posting has to communicate is not the task list, which every candidate already knows, but the shape of the engagement. A person delivering three fixed-fee projects at once lives a different life from one carrying a portfolio of retainer accounts, and both differ from an engineer embedded in a single enterprise customer for a year.
Fixed-fee implementation
Scope is the whole game
You quoted a number before you understood the customer environment, so every hour past the estimate comes out of margin. The posting has to hire for scoping discipline and change-order nerve, not just technical skill.
Time and materials
Hours are the product
Revenue tracks logged hours, so time recording stops being an administrative chore and becomes the invoice. Say that in the job description, because engineers who hate timesheets will self-select out early.
Managed services retainer
Portfolio, not project
The engineer carries several accounts at once against a monthly hour allowance. The skill is context switching and consumption tracking rather than deep single-project ownership.
Embedded or dedicated
Living in one account
The customer effectively rents a person. Write the engagement boundaries into the posting, because an embedded engineer who takes direction only from the customer starts to look like the customer’s employee.
Write the Delivery Model Into the First Paragraph
The single most useful sentence in a services job description is the one that says how the work is sold. Fixed-fee delivery hires for scoping discipline. Time and materials hires for time-logging discipline. Retainer delivery hires for context switching across a portfolio. Embedded delivery hires for stamina inside one account. Candidates who have done this work read that sentence and immediately know whether they want the job, which is exactly what a posting is for.
The role also has neighbors that get confused with it constantly. Presales sits before the signature and carries variable pay tied to bookings, which our sales engineer templates cover. Steady-state troubleshooting after go-live belongs to technical support engineers, not to delivery.
What Belongs in the Posting
A services job description does four jobs at once: it explains the product, it filters on real technical surface, it fixes your classification and travel expectations in writing, and it closes a candidate who almost certainly has another process running. Most postings do only the first.
The parts candidates read first
What your product does, in one sentence a stranger understands
How many accounts they carry at once
The delivery model: project, retainer, or embedded
Who else is on the delivery team, if anyone
The parts that filter applicants
The actual technical surface: SQL, APIs, scripting, named systems
Travel percentage, stated as a number
Whether time gets logged daily and against what
On-call or go-live weekend expectations
The parts that protect you
FLSA classification decided on duties and stated on the posting
Essential functions written plainly, including travel and lifting
Equal opportunity statement
Any customer site access, background, or clearance requirement
The parts that win the hire
Base pay or a good-faith range
How any utilization or delivery bonus actually pays out
Escalation path when a customer goes sideways
A named person and a real deadline to apply
The most common omission at small companies is account load. Candidates want a number: three concurrent implementations is a job, seven is a warning. Leaving it out does not make the number better, it just moves the conversation to the offer stage where it costs you more. Our general guide to writing a job description covers the underlying structure, and every variant here lives in the hiring templates library.
6 Professional Services Engineer Templates to Download
Download all six as one file or copy them individually. Each follows the same structure: company overview, position summary, key responsibilities, required qualifications, a classification note, an equal opportunity statement, and how to apply. The bracketed fields are the only parts you need to change.
Download All 6 Professional Services Engineer Templates
Core delivery, senior, integrations, on-site deployment, managed retainer, and fixed-term contract. All in one download.
Professional Services Engineer
The core delivery seat
Kickoff to go-live on several concurrent accounts: scoping, configuration, integration, migration, training, and handoff.
Senior Services Engineer
Strategic accounts
Owns solution design and the statement of work, leads discovery with customer architects, and reviews other engineers’ work.
Integrations Engineer
The code-heavy variant
Designs and builds the data flows between your platform and customer systems, then documents each one for support.
On-Site Deployment
Field commissioning
Installs and commissions at customer facilities, with the travel percentage, per diem, and travel-time treatment stated plainly.
Managed Delivery
Retainer portfolio
Carries a book of retainer accounts against monthly hour allowances, with change requests, health checks, and quarterly reviews.
Contract Services Engineer
Fixed-term capacity
A defined-term engagement for a delivery crunch, with the contractor versus employee question answered before you sign.
Template 1: Professional Services Engineer
The core delivery seat: concurrent implementations from kickoff to go-live, covering scoping, configuration, integration, migration, training, and handoff documentation.
Professional Services Engineer Job Description
PROFESSIONAL SERVICES ENGINEER JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Director of Professional Services / VP Customer Experience]
Employment type: Full-time
Work model: [On-site / Hybrid / Remote], travel [0-25%]
FLSA status: [Exempt / Non-exempt] (see classification note)
Compensation: $_ per year
ABOUT [COMPANY NAME]
[Company Name] sells [product] to [customer type]. Our customers buy the
platform and then need it configured, integrated, and running against their real
data before they see any value. That handoff is what this role owns.
POSITION SUMMARY
The Professional Services Engineer takes a signed customer from kickoff to
production. You scope the work, configure the product, build integrations,
migrate data, train the customer team, and hand off a working deployment to
[account management / support] with documentation that survives you.
KEY RESPONSIBILITIES
•Run [number] concurrent customer implementations from kickoff to go-live
•Gather technical requirements and translate them into a written scope
•Configure the product to the customer environment: [SSO, roles, workflows,
branding, reporting]
•Build and test integrations against [REST API / webhooks / SFTP / named
systems]
•Plan and execute data migration, including mapping, cleanup, and validation
•Deliver admin and end-user training sessions [live / recorded]
•Write runbooks and handoff documents for support and the customer team
•Log billable time against the engagement [daily / weekly]
•Escalate product gaps to engineering with reproducible detail
•Support presales on technical scoping calls when asked
REQUIRED QUALIFICATIONS
•[Number] years implementing, integrating, or deploying software for external
customers
•Working command of [SQL / REST APIs / scripting in Python or JavaScript]
•Comfortable owning a customer conversation without a manager in the room
•Written communication strong enough that a scope document holds up in a
dispute
•[Bachelor's degree in a technical field or equivalent practical experience]
•Willing to travel [percentage] for kickoffs and go-lives
CLASSIFICATION NOTE (read before posting)
Classification is a duties test, not a title test. The computer employee
exemption requires both a pay floor ($684 per week on salary, or $27.63 per hour)
and qualifying duties in systems analysis, design, or programming. A services
engineer whose week is configuration, training, and project coordination may not
meet the duties test even at a high salary. Decide honestly, write the answer on
the posting, and track hours for anyone non-exempt. This is general information,
not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per year, [bonus or utilization incentive], [benefits]
To apply, email __ with your resume and one paragraph on a
deployment you rescued.
Template 2: Senior Professional Services Engineer
For strategic accounts: solution design, statement of work authorship, discovery with customer architects and security teams, and review of other engineers on the project.
Senior Professional Services Engineer Job Description
SENIOR PROFESSIONAL SERVICES ENGINEER JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Head of Professional Services / VP Delivery]
Employment type: Full-time
Work model: [Hybrid / Remote], travel [25-40%]
FLSA status: Exempt (see classification note)
Compensation: $_ per year
ABOUT THIS ROLE
[Company Name] is hiring a senior engineer to lead our largest and most
technically difficult deployments: the accounts where the integration surface is
wide, the data is messy, and the customer has an architecture review board.
POSITION SUMMARY
The Senior Professional Services Engineer owns delivery for strategic accounts,
sets the technical approach for an engagement, reviews the work of other
engineers on the project, and is the person the customer's technical leadership
trusts when a plan has to change.
KEY RESPONSIBILITIES
•Own end-to-end delivery for [number] strategic accounts at a time
•Write the solution design and the statement of work with [sales / delivery
leadership] before the engagement starts
•Lead technical discovery sessions with customer architects and security teams
•Build the hard parts: [custom integrations, migration tooling, performance
tuning]
•Review configurations and integration code produced by other engineers
•Mentor [number] engineers and run internal enablement on new product areas
•Drive change orders when scope moves, rather than absorbing them quietly
•Feed recurring delivery problems back to product with data, not anecdotes
•Represent delivery in executive steering meetings and go-live decisions
REQUIRED QUALIFICATIONS
•[5+] years delivering customer-facing implementations, including [2+] years on
enterprise accounts
•Deep command of [SQL, API design, authentication, cloud infrastructure]
•Track record writing scope documents that held up through a contentious
project
•Experience saying no to a customer request and keeping the relationship
•[Bachelor's degree in a technical field or equivalent practical experience]
CLASSIFICATION NOTE
A senior engineer with genuine design and systems analysis duties will usually
meet the computer employee exemption duties test, and the pay level at this
grade clears the salary floor easily. That does not make the exemption automatic:
it still turns on what the person actually does most weeks. Document the duties
in the job description itself, because that description is the first thing
examined if the classification is ever challenged. This is general information,
not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per year, [bonus], [equity], [benefits]
To apply, email __ with your resume and a short description
of the most complex deployment you have owned.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Template 3: Professional Services Engineer, Integrations
The code-heavy variant, covering integration architecture, transformation logic, and validation records. If the work is closer to design authority than to build, use the solution architect templates instead.
Professional Services Engineer, Integrations Job Description
PROFESSIONAL SERVICES ENGINEER, INTEGRATIONS JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Manager of Professional Services / Integrations Lead]
Employment type: Full-time
Work model: [Remote / Hybrid], travel [0-15%]
FLSA status: [Exempt / Non-exempt] (see classification note)
Compensation: $_ per year
ABOUT THIS ROLE
Most of our customers need [product] talking to [their CRM / their ERP / their
identity provider / their data warehouse] before go-live. This role builds those
connections, and it is the most code-heavy seat on the delivery team.
POSITION SUMMARY
The Integrations Engineer designs, builds, tests, and documents the data flows
between our platform and customer systems, then hands each one to support with a
runbook and a monitoring plan.
KEY RESPONSIBILITIES
•Design integration architecture for each engagement and document it before
building
•Build integrations using [our API, webhooks, middleware platform, custom
scripts]
•Write and maintain transformation logic for [field mapping, deduplication,
error handling]
•Test against customer sandbox environments and produce a validation record
•Diagnose failures across authentication, rate limits, schema drift, and
network policy
•Package reusable connectors so the next engagement is faster than this one
•Document every integration in a runbook the support team can act on
•Log billable time and flag scope changes before doing the extra work
REQUIRED QUALIFICATIONS
•[Number] years building customer-facing integrations
•Fluent in [Python / JavaScript / your stack] and comfortable in SQL
•Practical experience with [OAuth, SAML, SSO, webhooks, message queues]
•Experience with at least one of [Salesforce, NetSuite, SAP, Snowflake, Okta]
or the equivalent in your market
•Reads API documentation faster than they ask questions about it
CLASSIFICATION NOTE
This is the services variant most likely to satisfy the computer employee
exemption, because the primary duty really is systems analysis and programming.
Confirm the pay test is met: $684 per week on a salary basis, or $27.63 per hour
if you pay hourly. Note that the exemption does not cover employees whose work is
merely assisted by computers, so a role that mostly configures settings inside a
product interface should be examined more carefully than one that writes and
ships code. This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per year, [bonus], [benefits]
To apply, email __ with your resume and a link to something
you built that moved data between two systems.
Template 4: Professional Services Engineer, On-Site Deployment
For field commissioning at customer facilities, with travel percentage, per diem, acceptance sign-off, and travel-time treatment stated plainly. Compare it with the field engineer templates if the role is service rather than delivery.
Professional Services Engineer, On-Site Deployment Job Description
PROFESSIONAL SERVICES ENGINEER, ON-SITE DEPLOYMENT JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Field Delivery Manager / Director of Services]
Employment type: Full-time
Work model: Field-based, travel [40-70%], home base [City]
FLSA status: [Exempt / Non-exempt] (see classification and travel note)
Compensation: $_ per [year / hour], plus [per diem, mileage]
ABOUT THIS ROLE
Our product runs [on customer hardware / in a plant / across physical sites], so
deployment happens at the customer location. This engineer travels to the site,
installs and commissions the system, trains the people who will operate it, and
leaves it working.
POSITION SUMMARY
The On-Site Deployment Engineer commissions installations at customer facilities,
validates them against an acceptance checklist, trains local staff, and closes
each engagement with a signed acceptance document.
KEY RESPONSIBILITIES
•Travel to customer sites in [region] for installation and commissioning
•Install, configure, and validate [hardware / software / network components]
•Run acceptance testing against a written checklist and capture sign-off
•Train customer operators and administrators on site
•Complete site reports, photos, and time records the same [day / week]
•Coordinate with the customer's facilities, IT, and safety teams before arrival
•Follow all customer site safety rules and our own [PPE / access] policy
REQUIRED QUALIFICATIONS
•[Number] years deploying [systems / equipment] at customer sites
•Hands-on skill with [networking, Linux, industrial protocols, your stack]
•Valid driver's license and ability to travel [percentage] including
[overnight / multi-week] trips
•Ability to lift [weight] and work in [plant / warehouse / outdoor] conditions
where required
•Calm under pressure with a customer standing over your shoulder
CLASSIFICATION AND TRAVEL NOTE
Field deployment roles are the hardest ones to classify, and travel time is the
reason. For a non-exempt employee, travel that cuts across normal working hours
is generally hours worked, including on days that are otherwise non-working, and
time spent driving at the employer's direction counts as well. Decide the
classification on duties, then build a time-recording habit that captures travel
honestly rather than reconstructing it at month end. If you pay hourly, confirm
your overtime math includes shift differentials and non-discretionary bonuses in
the regular rate. This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per [year / hour], [per diem], [mileage or vehicle],
[overtime treatment]
To apply, email __ with your resume and your home base city.
Template 5: Professional Services Engineer, Managed Delivery
For a retainer portfolio: change requests, health checks, quarterly technical reviews, and consumption tracking against a monthly hour allowance. Pair it with the technical account manager templates when the relationship side needs its own owner.
Professional Services Engineer, Managed Delivery Job Description
PROFESSIONAL SERVICES ENGINEER, MANAGED DELIVERY JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Manager of Managed Services / Delivery Lead]
Employment type: Full-time
Work model: [Remote / Hybrid], travel [0-15%]
FLSA status: [Exempt / Non-exempt] (see classification note)
Compensation: $_ per year
ABOUT THIS ROLE
Some customers keep buying our time after go-live on a monthly retainer:
configuration changes, new integrations, quarterly reviews, and a person who
already knows their environment. This role carries that book of accounts.
POSITION SUMMARY
The Managed Delivery Engineer serves a portfolio of retainer customers, running
change requests, ongoing configuration, health checks, and quarterly technical
reviews inside a contracted monthly hour allowance.
KEY RESPONSIBILITIES
•Own a portfolio of [number] retainer accounts and their monthly hour budgets
•Run scheduled health checks and produce a written findings report
•Lead quarterly technical reviews with each customer's admin team
•Track consumption against the retainer and flag overage before it happens
•Keep environment documentation current for every account in the portfolio
•Partner with [customer success / account management] on renewal risk
•Convert recurring manual work into automation or product feedback
REQUIRED QUALIFICATIONS
•[Number] years in a customer-facing technical delivery or administration role
•Comfortable context switching across [number] accounts in a single week
•Command of [SQL, APIs, our product area, your stack]
•Disciplined time logging and the judgment to say when a request is out of
scope
•Written communication that a customer executive can read without translation
CLASSIFICATION NOTE
Retainer work skews toward configuration and administration rather than design
and programming, which makes the computer employee exemption harder to establish
than it looks on an offer letter. Many managed delivery seats are properly
non-exempt. If yours is, pay overtime past forty hours in a week, capture the
hours in a system rather than a spreadsheet nobody updates, and do not let a
monthly retainer cap become an unpaid-hours problem for the engineer. This is
general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per year, [bonus], [benefits]
To apply, email __ with your resume and the number of
accounts you have supported at once.
Template 6: Contract Professional Services Engineer
For a delivery crunch, written so the contractor versus employee question gets answered before you sign rather than during an audit. Entry-level capacity is a different posting: see the junior services engineer templates.
Contract Professional Services Engineer Job Description
CONTRACT PROFESSIONAL SERVICES ENGINEER JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Delivery Manager]
Engagement type: [Fixed-term employee / independent contractor: choose one and
read the classification note first]
Term: [Number] months, [full-time / part-time at ___ hours per week]
Compensation: $_ per [hour / day / project]
ABOUT THIS ROLE
We have [number] signed implementations landing in the same quarter and not
enough delivery capacity to hit the go-live dates. This is a defined-term
engagement to carry [number] of those projects to production.
POSITION SUMMARY
The Contract Services Engineer delivers a named set of customer implementations
within a fixed term, working to our delivery methodology and handing each account
to the permanent team with complete documentation.
KEY RESPONSIBILITIES
•Deliver [number] named implementations from [start] to [end date]
•Follow our delivery methodology, templates, and documentation standards
•Configure, integrate, and validate each deployment to the agreed scope
•Train customer administrators and produce handoff documentation
•Report status weekly against the project plan
•Log hours against each engagement for invoicing and utilization reporting
•Transfer full context to the permanent team before the term ends
REQUIRED QUALIFICATIONS
•[Number] years of hands-on implementation delivery
•Immediate availability for a [length] engagement
•Command of [SQL, APIs, your stack] without a ramp period
•Experience joining a delivery team mid-flight and being productive in week one
•References from two engagements of comparable size
CLASSIFICATION NOTE (the expensive one)
Calling a delivery engineer a contractor does not make them one. If you set the
schedule, assign the accounts, require your methodology, supply the tools, and
direct how the work is done, you are describing an employee under both the
federal economic reality test and stricter state tests such as the ABC test used
in several states. Misclassification exposure includes back overtime, payroll
taxes, penalties, and benefits claims, and it is one of the most common mistakes
small software companies make when a quarter gets tight. If you want a true
contractor, contract for a defined deliverable and let them control the method.
Otherwise hire a fixed-term W-2 employee, which this template also supports.
Verify the current federal and state tests before you sign. This is general
information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_ per [hour / day / project], [invoicing terms or payroll
schedule], [expense policy]
To apply, email __ with your resume, rate, and availability
window.
Exempt or Non-Exempt: Decide Before You Post
A professional services engineer is not automatically exempt from overtime. The general rule for computer employees sets a pay floor of $684 per week on a salary or fee basis, or $27.63 an hour for hourly pay, and that floor is only half the requirement.
The other half is the duties test, and it is narrower than the job title suggests. The Department of Labor’s fact sheet on computer-related occupations states plainly that employees whose work is merely dependent on or facilitated by computers, without being primarily engaged in systems analysis and programming, are not covered. That sentence decides a lot of services seats.
The computer exemption has two tests, not one
The computer employee exemption requires a pay test and a duties test, and both have to hold. The pay test is $684 per week on a salary or fee basis, or $27.63 an hour if you pay hourly, which is the only white-collar exemption with an hourly route. The duties test is narrower than most founders expect: the primary duty has to be systems analysis, program design and development, or work of similar skill. Configuring a product through its own administrative interface, running training sessions, and coordinating a project plan are not those things, however technical they feel on a bad week. An integration-heavy seat that writes and ships code usually clears it. A configuration and enablement seat often does not, and paying that person a large salary does not fix the duties problem. This is general information, not legal advice.
There is a second door: the learned professional exemption
When the computer exemption does not fit, the learned professional exemption is the next thing to examine, and it runs on a different logic. It asks whether the primary duty requires advanced knowledge in a field of science or learning that is customarily acquired by a prolonged course of specialized intellectual instruction. Engineering degrees can support it. A path built entirely from bootcamps and on-the-job learning generally does not, because the regulation cares about the customary route into the work rather than the individual’s résumé. The administrative exemption is sometimes raised for services roles as well, though it fits awkwardly where the work is hands-on delivery rather than business operations. Take one position, document why, and keep the analysis with the job description. This is general information, not legal advice.
Travel time is where field roles go wrong
For a non-exempt engineer, ordinary commuting is not hours worked, but travel to a customer site during normal working hours generally is, and it stays compensable on days the person would not normally work if it falls in those same hours. Time spent driving at the employer’s direction counts, and so does work performed on a plane or in a hotel room. The practical failure mode at small companies is not a legal misreading, it is the absence of a record: the engineer flies out Sunday, works four sites, and reconstructs the week from memory on Friday. Require time entry within twenty-four hours, separate travel from billable delivery in the system, and reconcile per diem and mileage on the same cadence. This is general information, not legal advice.
Contractor capacity is not a free option
Delivery crunches tempt small software companies into contractor arrangements that do not survive scrutiny. If you set the schedule, assign accounts, mandate your methodology, supply the tools, and supervise how the work gets done, the economic reality is employment regardless of what the agreement says, and several states apply an even stricter ABC test where the work being inside your usual course of business is enough to defeat contractor status on its own. Exposure runs to back overtime, unpaid payroll taxes, penalties, and benefits claims, and it typically surfaces at the worst moment, during diligence or after a bad separation. A genuine contractor is engaged for a defined deliverable and controls the method. Anything else should be a fixed-term employee. This is general information, not legal advice.
Anyone outside an exemption needs hours captured and overtime paid past forty in a week. If a seat sits near the line, our breakdown of exempt versus non-exempt classification works through the tests in order. Note also that the 2024 rule raising the white-collar salary threshold was vacated in federal court and formally rescinded in May 2026, so the $684 per week figure is the operative one and the highly compensated employee threshold remains $107,432.
Travel Time and On-Site Hours
For a non-exempt services engineer, travel to a customer site during normal working hours is generally hours worked, and the obligation does not stop on weekends. The federal rule on travel away from home community treats travel that cuts across the regular working hours as work time, including the corresponding hours on days the employee would not normally work.
The practical consequence is that a field deployment role needs a time-recording habit, not a policy document. An engineer who flies Sunday afternoon, commissions three sites, and reconstructs the week on Friday will underreport or overreport, and both are problems. Require entry within twenty-four hours and separate travel from billable delivery.
Situation
Non-exempt treatment
What to write in the posting
Home to usual office
Ordinary commuting, not hours worked
No mention needed
Travel to a customer site during working hours
Generally hours worked
State the travel percentage as a number
Travel on a weekend during corresponding working hours
Generally hours worked
Name weekend go-live expectations up front
Driving at the employer’s direction
Hours worked
State whether a vehicle or mileage is provided
Working on a plane or in a hotel room
Hours worked
Set the expectation on evening availability
Passenger travel outside regular hours
Generally not hours worked
Explain the per diem and expense policy
On-call during a go-live window
Depends on freedom to use the time
State the on-call rotation and any premium
Exempt engineers do not generate overtime from any of this, but they do generate expenses, fatigue, and turnover. Even where the law asks nothing, a travel percentage stated honestly in the posting is the cheapest retention tool available to a small delivery team.
What to Pay a Professional Services Engineer
No Bureau of Labor Statistics occupation carries this title, so pay has to be benchmarked against adjacent classifications rather than looked up. The nearest fits are computer occupations, all other, computer systems analysts, and, for integration-heavy seats, software developers.
Nearest BLS Classifications, National Medians
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), median annual wages were $116,580 for computer occupations, all other, $105,850 for computer systems analysts, $76,220 for computer network support specialists, $135,980 for software developers, and $124,900 for sales engineers. The 25th percentile was $79,370 for computer occupations, all other, and $82,860 for systems analysts (U.S. Bureau of Labor Statistics, OEWS national estimates).
Nearest classification
25th percentile
Median
75th percentile
When to benchmark here
Computer occupations, all other (15-1299)
$79,370
$116,580
$157,500
The closest catch-all for a full services engineer seat
Computer systems analysts (15-1211)
$82,860
$105,850
$134,110
Requirements analysis plus configuration; the common core fit
Computer network support specialists (15-1231)
$58,240
$76,220
$98,750
Deployment and infrastructure work, including on-site variants
Computer user support specialists (15-1232)
$49,000
$61,860
$79,040
Only if the seat is really support with a services title
Software developers (15-1252)
$105,210
$135,980
$171,980
Integration-heavy and senior strategic-account seats
Sales engineers (41-9031)
$92,890
$124,900
$161,230
Presales cousin; different structure with variable pay
Most full services engineer offers land between the 25th percentile of systems analysts and the median of computer occupations, all other, with senior strategic-account engineers pricing against software developers. Publish a good-faith range where pay transparency laws apply, and be explicit about how any utilization or delivery bonus actually pays out, because a vague variable component reads as a discount on the base.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
The failure mode in this role is almost never raw technical ability. It is composure in front of a frustrated customer, willingness to write things down, and the nerve to say that a request is out of scope before doing the work anyway.
Screen for those directly. Give a deliberately messy requirement and ask for a written scope with assumptions and exclusions. Then run a working session where the candidate walks a mock customer through a configuration decision they disagree with. Both exercises take under an hour and predict far more than a whiteboard puzzle.
The Reference Question That Actually Works
Ask a former delivery manager one question: did this person tell you when a project was going wrong, or did you find out at the go-live meeting? Services engineers who escalate early are worth a premium, because the cost of a late escalation on a fixed-fee project falls entirely on your margin. The answer to that single question separates candidates more reliably than any technical reference check, and most managers answer it honestly because it does not feel like a trap.
Hiring This Role Without an HR Department
Small-company services hiring fails in three predictable places: the posting hides the breadth of the job, nobody knows whether delivery is actually profitable, and onboarding stalls on system access. Each one has a fix that costs nothing but decisiveness.
The first services hire is asked to be four people at once
At a company with twenty employees there is no delivery organization, so the first professional services engineer inherits scoping, configuration, integration, migration, training, documentation, escalation triage, and the occasional presales call. That is a real job and it can be a great one, but only if the posting says so. Postings that hide the breadth attract specialists who quit in month five when they realize half the week is customer email. Postings that name it attract the specific person who likes range and autonomy, which is exactly who thrives as the first delivery hire. Write the honest inventory, mark what will be handed off as the team grows, and let candidates opt in with their eyes open.
Nobody knows whether delivery is profitable, including you
Services revenue looks healthy right up to the moment somebody divides it by hours actually spent. Without time logged against engagements you cannot tell a fixed-fee project that earned forty percent margin from one that lost money, and you cannot tell whether the engineer is overloaded or underused. The fix starts at the job description: state that time is logged against engagements, state the cadence, and hire people who accept it as part of the craft rather than as surveillance. Then hold the standard from week one, because a time-tracking habit that is not established during onboarding is almost never established later.
Onboarding a delivery engineer means access to customer systems on day one
A services engineer cannot do anything useful without credentials, and the list is long: your product admin console, the ticketing system, the code repository, the time and expense tool, the customer sandbox environments, and often the customer’s own systems under an access agreement. Alongside that sit the confidentiality agreement, the customer data handling policy, the expense and travel policy, and any background check the customer contractually requires before site access. FirstHR was built for that kind of sequence. The onboarding wizard runs the same checklist for every delivery hire, e-signature handles the agreements and policy acknowledgments, document management stores signed access approvals and background clearances against the employee profile with renewal dates, and training modules cover data handling before the first customer call. Applicant tracking is coming soon to FirstHR.
Once the offer is signed, the work becomes a repeatable onboarding checklist. For a delivery hire that checklist runs longer than usual, because customer system access, confidentiality agreements, and data handling training all gate the first billable hour. Ramp length is a judgment call, but a week lost waiting on credentials is pure cost, and under the Fair Labor Standards Act a non-exempt engineer is owed pay for every one of those idle hours.
Key Takeaways
A professional services engineer converts a signed contract into a working deployment: scoping, configuration, integrations, data migration, training, and a documented handoff.
Write the delivery model into the first paragraph, because fixed-fee, time and materials, retainer, and embedded engagements each hire for a different discipline.
The role is not automatically exempt: the computer employee exemption requires qualifying duties on top of the $684 weekly salary or $27.63 hourly pay test, and configuration-weighted seats often fail the duties test.
Travel to a customer site during normal working hours is generally hours worked for a non-exempt engineer, including the corresponding hours on days they would not normally work.
No BLS occupation matches the title, so benchmark against the nearest classifications: $105,850 for computer systems analysts and $116,580 for computer occupations, all other (BLS OEWS, May 2025).
Screen with a written scope exercise and a mock customer conversation rather than a whiteboard puzzle, and ask references whether the candidate escalated early.
A delivery hire needs agreements signed and system access granted before the first billable hour. FirstHR runs the same onboarding sequence for every services engineer, with e-signature for confidentiality and policy acknowledgments, document storage for access approvals and background clearances, and renewal dates tracked so nothing lapses quietly. Applicant tracking is coming soon to FirstHR.
Frequently Asked Questions
What does a professional services engineer do?
A professional services engineer takes a signed customer from kickoff to production. The work covers technical scoping, configuring the product to the customer environment, building integrations against the customer’s other systems, migrating and validating data, training administrators and end users, and handing a documented deployment to support or account management. The role sits after the sale and before steady-state support, which is why it exists separately from both. At a small software company one person carries several accounts at once and also absorbs escalations and the occasional presales scoping call. Most services engineers log time against engagements because that time either bills directly or measures the margin on a fixed-fee project.
What is the difference between a professional services engineer and a solutions engineer?
Timing and incentive. A solutions or sales engineer works before the contract is signed: demos, technical discovery, proof of concept, and answering security questionnaires, usually carrying a variable compensation component tied to bookings. A professional services engineer works after the signature and is measured on delivery, on utilization, and on whether the customer actually reaches production. The skill overlap is real, which is why people move between the two, but the temperament differs. Presales rewards persuasive breadth under time pressure. Delivery rewards patience, documentation, and the willingness to tell a customer that a request is out of scope. Hire for the second set if the job is delivery, even when a strong presales candidate interviews better.
Is a professional services engineer exempt from overtime?
Not automatically, and the title has nothing to do with it. The computer employee exemption requires both a pay test and a duties test: $684 per week on a salary or fee basis, or $27.63 an hour if paid hourly, plus a primary duty of systems analysis, program design, or work of similar skill. Integration-heavy seats that write and ship code usually meet the duties test. Configuration, training, and project coordination seats often do not, and a high salary does not cure a failed duties test. Where the computer exemption does not fit, the learned professional exemption may, but it turns on advanced knowledge customarily acquired through prolonged specialized instruction. Decide on duties, document the reasoning, and track hours for anyone non-exempt. This is general information, not legal advice.
How much does a professional services engineer make?
There is no Bureau of Labor Statistics occupation with that title, so the honest answer is a benchmark rather than a lookup. In the Occupational Employment and Wage Statistics survey (May 2025), the nearest classifications show a median of $116,580 for computer occupations, all other, $105,850 for computer systems analysts, $76,220 for computer network support specialists, and $135,980 for software developers. Most full professional services engineer offers land between the 25th percentile of systems analysts, around $82,860, and the median of computer occupations, all other, with integration-heavy and enterprise-facing seats at the upper end and configuration-weighted seats lower. Senior delivery engineers on strategic accounts price against software developers. Publish a good-faith range where pay transparency rules require one.
Should the job description mention a utilization target?
State that time is logged and that utilization is measured, but be careful about publishing a hard percentage in the posting. A number in the job description reads as a quota to candidates and sets an expectation you may not hit during ramp, during a quarter with weak bookings, or in a role that also carries escalations and presales support. The better construction is to say that the engineer logs time against engagements daily, that delivery performance is reviewed against a utilization target set with the manager, and what else counts as productive time. That is honest, it filters out people who dislike time tracking, and it does not lock you into a number you will renegotiate in the first review cycle.
Can we hire a professional services engineer as a contractor?
Only if the arrangement is genuinely a contractor arrangement, which most delivery capacity is not. If you set the schedule, assign the accounts, require your delivery methodology, supply the tools, and supervise how the work gets done, the economic reality is employment no matter what the agreement says. Several states apply a stricter ABC test, where the work falling inside your usual course of business is enough on its own to defeat contractor status, and implementation delivery at a software company plainly does. Misclassification exposure includes back overtime, unpaid payroll taxes, penalties, and benefits claims, and it usually surfaces during diligence or after a bad separation. Contract for a defined deliverable with a genuine independent business, or hire a fixed-term employee. Verify current federal and state tests before signing.
How do we hire this role without an HR department?
Run a short, fixed sequence. Post one specific job description with the delivery model, account load, travel percentage, technical surface, and pay range stated up front. Screen with a written scenario rather than a trivia interview: give a realistic messy requirement and ask for a scope in writing. Run a working session where the candidate walks a mock customer through a configuration decision, because customer-facing composure is the thing that fails in this role. Check references from a delivery manager who saw them close an engagement. Then treat onboarding as a checklist: agreements, system access, customer data handling training, and any background clearance the customer requires before site access. FirstHR runs that sequence with e-signature, document management, and renewal tracking. Applicant tracking is coming soon to FirstHR.
