Last updated: October 15, 2026
A sales engineer job description should state how many account executives the seat supports, the typical deal size and cycle, who owns the demos and proofs of concept, how variable pay is earned, and who the role reports to. Most postings stop at “partner with sales.” Good sales engineers read that line as a warning.
Seven account executives. That was the number nobody wrote down.
A payments software company in Charlotte, about 350 people, hired a sales engineer off a posting that read like most of them do. Partner with account executives to drive technical wins. Deliver compelling demos. Competitive OTE. The man they hired had spent four years at a security vendor in Atlanta supporting two enterprise reps, and he was good at it, the kind of SE who could take a skeptical identity architect through a SAML handshake on a whiteboard and leave the room with the next meeting booked.
By week six he was covering seven reps across mid-market and enterprise. Nine open proofs of concept. A demo tenant he shared with marketing that broke every time someone ran a webinar. His variable was paid on the whole region’s new annual recurring revenue, and by the third quarter the region sat at 61% of plan, which meant his check reflected deals he had never touched and missed the three he had personally carried over the line. He left in month seven for a job supporting three reps. Nobody at the company was surprised. Nobody had written anything false either.
The second posting added four sentences. You’ll support four mid-market AEs. Deals average about $48,000 in annual contract value and close in roughly 70 days. You own the demo environment. Variable is 20% of on-target earnings, paid quarterly on those four reps’ combined bookings. Fewer people applied. Better people applied, and the first-round calls got shorter because candidates arrived having already done the math.
I’ve carried a number for most of my career, and the SEs I’ve worked beside could always tell me, within a minute of reading a posting, whether the company understood the job. Our sales engineer staffing desk invoices you only if a person we introduced signs your offer, so factor that in. Everything below works without us.
Some ground is covered elsewhere and I won’t repeat it. The five kinds of pre-sales seat and how we vet each one live on that staffing page. Base, OTE, and the level-by-level bands belong to the sales engineer salary guide. If the seat leans toward reference architectures and migration plans more than live demos, start from our solutions architect job description instead. This post is about the sentences a sales engineer posting needs that a general technical posting never would. Once applications arrive, our interview guide for sales engineer candidates takes over from there.
What a Sales Engineer Reads For
A sales engineer job description has two readers inside one candidate. The engineer wants to know how deep the product goes and what breaks in a demo. The seller wants to know whose number they’re attached to and how they’ll get paid. Postings written by an engineering manager feed the first and starve the second. Postings written by a sales VP do the opposite.
- The coverage ratio. How many AEs, which segment, and whether the SE is assigned to specific reps or pulled from a pool.
- The deal. Average contract value, cycle length, who sits on the buying committee. “Enterprise” is not a number.
- Demo and POC ownership, including who maintains the environment when it breaks at 8 a.m. before a 9 a.m. call.
- Security reviews and RFPs. How many a quarter, and whether there’s anyone else who answers them.
- What the variable is paid on and how often. This one decides more acceptances than base does, in my experience.
- The reporting line, because it tells a candidate where the next promotion comes from.
- Travel. Give a percentage.
The federal description of the job is broader than any of that. O*NET’s profile for sales engineers lists tasks from responding to requests for proposal to collaborating with sales teams on customer requirements, which is accurate and tells a candidate almost nothing about your Tuesday. Federal pay data is more useful. Sales engineers earned a $124,900 median in May 2025 (the Bureau of Labor Statistics occupational outlook has the figure), and the bureau expects the occupation to add just 3% more jobs over the 2025 to 2035 decade, or roughly 3,800 openings each year. Small occupation. The same page counts roughly 51,600 sales engineer jobs nationally in 2025. The good ones are not reading postings that don’t tell them anything.
How Many Reps, and Which Ones?
Ratio first.
An SE supporting two enterprise reps and an SE supporting eight SMB reps have different jobs that share a title. The first one spends a week building a custom proof of concept for a single bank. The second one runs three demos a day and never builds anything custom at all. Both are real jobs. A candidate who has done one for five years usually knows exactly which of the two they want next, and if the posting doesn’t say, they guess, and about half of them guess wrong.
| Coverage model | What the SE’s week looks like | Sentence for the posting |
|---|---|---|
| Aligned, enterprise | Few accounts, long cycles, custom POCs, security architects on every third call | “You’ll partner with two named enterprise AEs on roughly 15 active opportunities.” |
| Aligned, mid-market | A demo most days, two or three structured trials a month, some light scripting | “You’ll support four mid-market AEs selling deals between $25,000 and $90,000 a year.” |
| Pooled | Requests come through a queue or Slack channel, triage by deal size, little continuity per account | “Three SEs share requests from 14 AEs. Deals over $50,000 get a named SE from discovery onward.” |
| Overlay or specialist | Brought in for one product line or one technical domain across every region | “You’ll be the data-integration specialist for all 22 AEs in North America.” |
Pooled models deserve one extra line about triage. A data observability startup in Austin ran one SE against nine reps for most of a year, and he did what any sensible person would do with that load. Big deals got him. Small deals got a recorded demo link. The SMB reps stopped asking, their win rate dropped, and the company eventually hired two junior demo-focused SEs at a lower band, which was the right call, but it took three quarters and a resignation to get there. If you pool, say how you triage. A candidate who has lived in a pool will ask anyway.
And if you don’t know the ratio yet because the team is growing, write down what it is today and what you expect it to be in two quarters. That’s honest. Candidates respect a moving number far more than a missing one.
Print the Deal, Not the Adjectives
“Complex enterprise sales cycles.” I see that phrase on maybe half the SE requisitions that cross our intake calls, and in all those calls it has never told me a thing. Complex for a $15,000 HR tool and complex for a $1.2 million core banking migration are not the same Thursday.
Four figures do most of the work, namely average annual contract value, cycle length from first technical call to signature, buying-committee titles, and last quarter’s POC count with its conversion rate. Rough is fine. A Phoenix fleet-telematics vendor we recruited for last spring wrote “most deals land between $60,000 and $150,000 a year, take four to six months, and a CISO signs off on nearly every one.” The SE who accepted told us it was the only posting in her eleven-company search that mentioned a CISO.
Security reviews often eat half an SE’s week, so they sit right beside the deal figures. Regional banks tend to send the Shared Assessments SIG questionnaire, a healthcare buyer may send the Cloud Security Alliance’s CAIQ or a homegrown 250-row spreadsheet, and the vendor either hands back a SOC 2 Type II report plus a 400-answer Loopio or Responsive library a GRC analyst keeps current, or it leaves the SE typing encryption-at-rest answers at 10 p.m. Candidates who have lived the 10 p.m. version ask about it in the first call.
RFP volume belongs there too. One cybersecurity client answered 31 RFPs last year, and its two SEs wrote the technical sections of all 31. Their posting said so. The man they hired came from a team with a full-time proposal writer, took the job anyway, and negotiated a contract writer into his first quarter. Nobody felt ambushed.
Who Builds the Demo?
I learned this one sitting in on a demo for a logistics software vendor in Ontario, California, back in 2022. Twelve minutes in, the prospect’s data architect asked why the carrier-performance dashboard read zero. The sample data had expired. The tenant’s fictional shipper, “Acme Test 4,” hadn’t moved a truck since the March release, and the SE spent the next Friday rebuilding seed data in Python instead of preparing for Monday’s two calls. The company’s next SE posting carried one new line, “you’ll own the demo tenant and its sample data, refreshed after each monthly release,” and the two finalists both asked about it in round one.
Demo tooling changes who you’re hiring. Teams on Reprise, Walnut, Consensus, Saleo, or Demostack run captured or overlay demos, and a marketing operations analyst often maintains them. Teams demoing from a shared AWS sandbox that an engineer stood up in 2023 need an SE who can fix a broken Terraform apply or a seed script before 9 a.m. Name the setup. A candidate who wants one of those weeks usually doesn’t want the other.
Proofs of concept deserve their own sentence. When we ask clients about theirs, the answers range from 10-day guided trials to 90-day pilots with a statement of work, and the ones that convert almost always had written success criteria, an end date, and an exit clause signed by the prospect’s sponsor. The rest drift until the buyer’s fiscal year closes in June or December. Two SEs we placed in 2025 took their offers specifically because the posting admitted there was no POC playbook yet and asked them to write it.
Handoff gets skipped most. After signature, a Tampa health-tech client keeps its SE on the account through a 90-day implementation; a Minneapolis HR software client passes a six-page technical design document to an implementation lead on day one and moves the SE to the next deal. An SE from the Minneapolis model would resent losing 30% of the week to onboarding calls in Tampa, and an SE from Tampa would miss the continuity. One sentence in the posting sorts them.
What the Variable Is Actually Paid On
On most SE postings we review, this part is a single word. Competitive.
Sales engineers understand variable pay about as well as the reps do, and they care less about the split than about the measure. Our salary guide’s 2026 bands put a mid-level SE, two to five years in the seat, at $110,000 to $145,000 base and $150,000 to $200,000 on-target earnings. Senior SEs run $145,000 to $185,000 base and $200,000 to $270,000 OTE. The split is usually 80/20 at SaaS companies and nearer 70/30 at security and infrastructure vendors, where cycles run longer. Print the base range and the split. Then print what the variable is earned against, since the four common structures below hire four different people.
| Variable paid on | Behavior it tends to produce | Who it attracts |
|---|---|---|
| The aligned AEs’ combined bookings | Tight partnership with a few reps, effort follows the biggest deals in that patch | SEs who like owning a territory alongside specific people |
| Region or company quota | Helps everyone a little, nobody a lot; pay drifts from personal effort | Pooled-model veterans, people who value stability over upside |
| Technical win rate or MBO targets | Strong POC discipline, sometimes slower to chase commercially stalled deals | Engineers moving into pre-sales who distrust bookings-based pay |
| Discretionary annual bonus | Predictable, weakly tied to deals; reads as “not really a sales role” | Post-sale and solutions architect profiles more than quota-carrying SEs |
Payment frequency matters too, and it costs nothing to print. Monthly, quarterly, or annual. Whether there’s a cap. Whether there’s a guaranteed ramp for the first quarter or two while the new SE learns the product. A $40,000 variable line paid quarterly against four reps you can name is a completely different offer from $40,000 paid annually against a company number, even though a spreadsheet would call them identical.
Then there’s the part that isn’t optional in two big states.
California Labor Code section 2751 says that when an employment contract for work in California involves commissions, the contract has to be in writing, it has to spell out how commissions are computed and paid, and the employer has to hand over a signed copy and get a signed receipt back. You can read the full text of section 2751 in about a minute. The interesting wrinkle for SE plans is the carve-out. Bonus and profit-sharing plans are excluded unless the employer has offered a fixed percentage of sales or profits, which means a discretionary team bonus and a per-deal commission can land on opposite sides of the rule. New York goes further for its “commission salesman” category. Under New York Labor Law section 191, the terms have to be in writing, signed by both sides, kept for at least three years, and they have to describe how commissions are calculated, how any draw is reconciled, and what gets paid if either party ends the employment. Whether a particular SE falls in that category turns on the definition in section 190, which covers an employee whose principal activity is selling and whose earnings are based in whole or in part on commissions. Ask your employment counsel how your plan reads. I’m a sales guy, not a lawyer.
The practical takeaway is simpler than the statutes. If the comp plan has to exist in writing before the SE starts anyway, the posting can describe it in two sentences. An Irvine software company we worked with sent its signed plan to a new SE in week five, after his first deal had already closed, and spent the next month arguing about whether that deal counted. It counted. Write the plan first. Put the summary in the posting. Our free salary benchmark assistant will show where a proposed range lands for your city and level.
Reporting Line, Travel, and the Next Job
Who the SE reports to is the line candidates reread most, after pay.
Under a sales engineering manager, someone who has run a POC personally holds the one-on-ones, guards Friday afternoons for demo builds, and fights sales leadership on ratios. Under a regional sales director, the SE effectively joins that rep team, sits in the Monday forecast call, and gets reviewed by a person who has never rebuilt a demo tenant. Under product or engineering, which shows up mostly at Series A and B companies, the SE gets roadmap influence and loses some commercial pull. I’ve sold alongside SEs in all three setups. Each one worked when the posting said which it was, and two of them went badly when it didn’t.
Next jobs follow from the reporting line. A senior SE reading your posting wants to know whether the path runs to principal SE, SE manager, solutions architect, or across to an account executive quota, and whether anyone has actually walked it. “Two of our SEs moved into SE management in the last 18 months” reads better to a senior SE than any paragraph about growth culture.
Travel takes one line with a percentage in it. “Up to 25%, mostly on-site workshops in Boston and New York” is honest. “Some travel required” lets a parent with two kids under six assume the worst and close the tab.
Where the seat sits in the revenue org matters at the top of the posting as well. A company hiring its first chief revenue officer and its first SE in the same year has very different questions to answer. If that’s you, our CRO job description template covers the numbers that seat expects in writing. And if you’re filling account executive and SDR seats around this hire, our tech sales staffing team runs those searches.
Sales Engineer Job Description Template
Swap out every bracket. A few brackets are notes for you rather than words for the candidate, so delete them before publishing.
Job Title
[Sales Engineer / Senior Sales Engineer / Solutions Engineer, Enterprise] [Use the title your candidates search for. If the role is mostly post-sale, call it something else.]
About the Role
[Company] sells [product, in one plain sentence] to [buyer titles] at [company size or industry]. We’re hiring a sales engineer to own the technical side of the sale for [segment], from first discovery call through security review and signature. You’ll report to [title], and you’ll work most closely with [the named AEs / the mid-market team / product management].
The Reps You’ll Support
[You’ll support [four] [mid-market] account executives, assigned to you by name.] [If pooled, give the pool size and how requests are triaged.] [If the ratio will change soon, give today’s number and the expected one.]
The Deals
[Most deals are $[60,000] to $[150,000] in annual contract value and close in [four to six] months. A typical buying committee includes [IT director, security architect, procurement].] [Add last quarter’s POC count and how many converted, if you track it.]
Demos, POCs, and Security Reviews
[You’ll own the demo environment, including sample data and refreshes after each release.] [Name the demo tool if there is one.] [Proofs of concept run [two] to [four] weeks with written success criteria.] [You’ll answer roughly [12] security questionnaires a quarter, with support from [team or answer library].]
What You’ll Own
- Technical discovery on every assigned opportunity, written up in [Salesforce / HubSpot] so the AE and the next SE can both read it.
- Live product demos tailored to the prospect’s stack, and the recovery when a demo goes sideways.
- Proof-of-concept scoping, from success criteria through the readout to the buying committee.
- The technical sections of RFPs and security reviews, including [SIG / CAIQ] questionnaires.
- [A clean technical handoff to [implementation / customer success] after signature.]
- Feedback to product on the gaps that cost us deals, with the deal names attached.
What You Bring
- [Three]+ years in a customer-facing technical role, at least [two] of them in pre-sales.
- Working knowledge of [the integration patterns your buyers ask about, such as SAML or OIDC single sign-on, REST APIs, webhooks, and SCIM provisioning].
- Enough scripting in [Python / JavaScript / SQL] to build a quick integration or data load for a POC.
- Experience presenting to [technical buyers / security teams / executives] in [your industry, if it matters].
Nice to Have
- [Cloud certification relevant to your stack, such as AWS Certified Solutions Architect.]
- [Experience with a structured sales methodology such as MEDDICC.]
- [Background in your vertical, if buyers expect it.]
How You’re Paid
[Base: $[minimum] to $[maximum] a year.] [Variable: [20]% of on-target earnings, paid [quarterly] on [the combined bookings of your assigned AEs / technical win targets].] [On-target earnings: $[X] to $[Y].] [Ramp: guaranteed variable at [100]% for the first [two] quarters.] [Equity, benefits, and anything else, in one plain sentence.] [The full compensation plan is provided in writing and signed before your start date.]
Travel, Location, and Growth
[Remote / hybrid in [city] / on-site in [city].] [Travel up to [25]%, mostly for [customer workshops / trade shows].] [Typical next steps for this role here include [principal SE / SE manager / solutions architect].]
How to Apply
[Where to apply, and the date the posting closes. If your state requires anything else on the posting, add it here.]
What VPs of Sales Ask Us Before They Post
Should the posting say “solutions engineer” or “sales engineer”?
Use whichever title your best candidates already hold. In software the two are close to interchangeable, so the deciding factor is search behavior, not prestige.
Pull the LinkedIn titles of the five SEs at the competitors you’d most like to hire from. If four of them say solutions engineer, so should you. “Solutions consultant” skews toward application software and ERP vendors. “Pre-sales engineer” shows up more at enterprise infrastructure companies. “Sales engineer” is still the broadest net and the one federal data uses.
Do we have to print the OTE, or just the base?
$145,000 base with a 20% variable means something only if the candidate can see both, so print the base range and the OTE range together.
If you only print one, print the base, because that is the number a candidate negotiates from. But sales engineers compare offers on OTE and then interrogate the base, and a posting that shows only one sends them looking for the other. The salary guide explains why base is the number that wins or loses the candidate. Showing both just saves a phone call.
Can our SE also run onboarding after the deal closes?
Some can, and some will quit over it. Say how many hours a week go to post-sale work, because that split decides which candidates apply more than the title does.
Under ten percent of the week reads as a clean handoff. Thirty percent or more is really a hybrid of SE and implementation consultant, and that’s a legitimate job, but post it as one. We’ve seen good pre-sales people accept a role, discover the onboarding load in month two, and start interviewing by month four.
How technical should the requirements section get?
Technical enough to filter, not so technical it describes a backend engineer. Name the integration patterns your buyers actually ask about and the one language an SE would script a POC in.
If your product lives on Snowflake or Databricks, say so. If prospects always ask about SSO through Okta or Microsoft Entra ID, say that. Don’t list Kubernetes, Terraform, Go, and Rust because the engineering team uses them. A sales engineer needs to explain your architecture with confidence and wire up a convincing demo, not ship production code. For the AI-heavy version of this role, where the SE builds retrieval pipelines or agent demos live, our guide to hiring AI solutions engineers covers the extra depth.
Is it fair to put a quota on a sales engineer?
Usually, yes, as long as the quota belongs to deals the SE can influence. Tie it to aligned reps’ bookings or technical wins, not the whole company’s number.
The resentment comes from mismatch, not from the quota itself. An SE who carried three wins over the line and gets paid on a region that missed by 39% will tell everyone at the next team offsite. Ask an SE you trust how they’d want to be measured. They’ll have an opinion within seconds.
We’ve never had an SE. Who should the first one report to?
The head of sales, in most cases, with a written commitment that the role stays technical. The first SE needs protection from becoming a spare account executive.
Put two sentences in the posting. One saying the role reports to the VP of sales. One saying what the SE will not do, such as prospecting or owning renewals. Plan for a dedicated SE manager once you’re past four or five SEs, and say that in the posting too, because ambitious candidates will want to know whether they’re interviewing for the first hire on a team or a seat that stays alone.
Ask Your Best Rep to Read It
Before the posting goes live, give it to the account executive who’ll sit next to this hire. One question. From this page alone, would a great SE know what their week looks like? Reps tend to answer that bluntly, and when one says “kind of,” the gap is nearly always the ratio, the deal size, or the variable measure.
KORE1 opened its doors in 2005. Across our IT desks, searches average 17 days to hire, 92% of the people we place remain on that payroll a year after starting, and our recruiters bring 15+ years of experience apiece across 30+ metros. Most of that speed is decided at intake, on calls where we pin down exactly the facts above before anyone sources a single profile. If you’d like an SE req read before it posts, send the draft to a recruiter on our team. That’s true whether you plan a direct hire search for a permanent seat, a contract sales engineer to clear a POC backlog before quarter close, or no outside help at all. When you want candidates, our pre-sales recruiting desk can usually spot which of those seven items from the first list your draft leaves out.
