EXPOSED
A large slice of the sales engineer's week — RFP and RFI responses, spec sheets, configuration quotes, technical FAQ answers, competitive comparison decks, follow-up summaries — is exactly the text-and-spec work generative AI already does at usable quality, and interactive product tours are increasingly self-serve. What survives is the live part: reading a room of skeptical engineers, running a proof-of-concept on the customer's messy actual infrastructure, and being the person who says 'our product will not do that' and is believed. Modal workers in complex B2B capital equipment and enterprise software keep their seat; those whose job is mostly configuring quotes and answering standard technical questions will see headcount thin.
Most of this decline happened after 2021 — it is not the pandemic dip.
Median pay $103,900 → $124,900 -3.8% in real terms
This line is counted by the Bureau of Labor Statistics — the one figure on this page that isn't a judgement of ours. Headcount moves on demand, offshoring, demographics and the business cycle, and automation is one term among several, often not the loudest.
So a falling line is not evidence that AI did it, and a rising one is not evidence that it won't. Both happen in this register: some occupations resist automation and shrink anyway, others are highly automatable and keep growing. The marked year is 2020.
BLS projection, 2024–2034
+5.5% 56,800 → 59,900 on the projections basis
Exposed, but growing
AI can already do a lot of these tasks, and the BLS still expects +5.5% more of these jobs by 2034. Demand for the output is growing faster than the work is being automated away — the mechanism BLS gives for software developers, and the combination people most often misread as an error.
Different clocks. The score is what current AI could do to this work today. The projection is how many of these jobs will exist in 2034. Everything between the two — how fast employers actually adopt, whether demand grows in the meantime — is why they can point opposite ways without either being wrong.
~5,000 openings a year on average, including replacing people who leave.
Sales EngineerSales SpecialistCustomer EngineerPre-Sales EngineerField Sales EngineerInside Sales EngineerOutside Sales EngineerProduct Sales EngineerRegional Sales EngineerProduct Support EngineerTechnical Sales EngineerEnterprise Sales EngineerSales Engineering ManagerProduct Support SpecialistInside Sales RepresentativeSales Applications EngineerChannel Sales Engineer (CSE)Field Service RepresentativeOutside Sales RepresentativePre-Sales Solutions EngineerTechnical Marketing EngineerBusiness Development EngineerField Marketing RepresentativeCeramic Products Sales Engineer
Presales ConsultantPresales EngineerSolution ArchitectSolutions ConsultantTechnical Account Manager
Holding it up: trust premium . Weakest point: liability shield .
Mixed — a routine tier and a judgment tier At 9, roughly half the week — RFP responses, bill-of-materials configuration, sizing calculators, standard technical objection handling — is text and spec work a model handles now, while the other half (scoping a POC against a customer's undocumented legacy stack, diagnosing why the integration failed on their network, whiteboarding architecture live with their engineers) still needs a person in the loop, which is why it sits mid-band rather than at 5 with inside sales or at 14 with field service techs.
Some physical or field component An 8 reflects that most of the job runs from a laptop on Zoom, but the deals that matter still involve flying to a plant floor to measure clearances, hooking demo hardware to the customer's PLC or test bench, or sitting in their datacenter during a pilot cutover — travel and on-site equipment handling that is real but intermittent, not the daily uncontrolled-environment work of an installer.
No licence, no signature requirement A 2 is accurate because no state licenses sales engineers; a PE stamp is rare and never required to quote or demo, and when a misconfigured spec causes a failure the exposure lands on the employer's contract terms and the customer's own engineering sign-off, not on the individual who built the proposal.
Meaningful discretion An 11 fits calls like whether to commit to a custom integration in writing, which failure mode to disclose before the customer discovers it in production, and how to scope a POC so it proves the thing that actually blocks the deal — genuine discretion with revenue and reputational consequences, but decisions that get reviewed by sales management, product, and legal before they become binding.
The verdict above describes this occupation as a whole. Almost nobody does the typical version of a job — tick what's actually in your week and see how your own mix sits.
Your task mix speaks to task resistance (9/20 here) — how much of the day's work current AI already does. That is the dimension the boxes above are about.
It cannot move the other three. Liability shield (2/20) is whether the law requires a licensed human to sign. Trust premium (14/20) is whether buyers specifically pay for a person. Judgment and accountability (11/20) is whether the role exists to own consequential calls. Those are facts about the occupation's standing, not about which tasks are in your week — a paralegal who does only trial exhibits still holds no licence. Together they are 27 of this occupation's 44 points (61%).
Embodiment (8/20) is also a property of the work rather than the worker, but we don't tag individual tasks as physical or not, so the picker can't tell you anything about it. That's a limit of this tool, not a claim.
Did we get the list right? Tell us what's missing — the tasks are written from the outside, and you're reading this from the inside.
No occupation passed every test: close enough to sales engineers on skills and subject matter, at least 10 points more resistant, no big jump in training, no new licence, no pay cut, and not shrinking on its own. That happens for 223 of the 654 occupations here that aren't SAFE, and it is worth stating plainly rather than leaving the section off.
The usual reason is that exposure travels with the skill profile. The jobs most similar to yours tend to be exposed for the same reasons yours is, so the near neighbours don't clear the gap — and the ones that do are a different kind of work, not a transfer of what you already know. Read that as a limit of this method, not a verdict that you're stuck: it only compares whole occupations, and it cannot see specialisation, industry, or anything you'd bring that isn't in a federal skill survey.
Here is that claim on your own job rather than in the abstract. These are the three occupations closest to this one by skill and subject matter — the places the work would most naturally transfer — with what the register scores them:
That is the whole problem in three lines. The nearest work is not meaningfully safer, so there is no move here that trades a similar skill set for a better verdict. This is not us running out of ideas — it is what the neighbourhood looks like.
The moves above are yours to make. This is the other half: what would have to change in the world for the occupation itself to score higher. None of it is in any one person's gift, but it is where the floor actually comes from. Scores here are not a one-way ratchet. Only two of the five dimensions — task resistance and embodiment — track what machines can do. The other three track law, what buyers will pay for, and who is answerable, and those move in both directions, often in response to the same pressure AI creates. If every lever below landed, this occupation would score around 59/100, still EXPOSED.
Task-mix shift is genuine here: RFP/RFI drafting, config quotes and FAQ decks are already being absorbed by AI (Salesforce/Vivun-style tooling, PandaDoc/Loopio autoresponse), leaving the residual job as on-site proof-of-concept work against the customer's undocumented, non-reference-architecture infrastructure and live objection handling in front of hostile buyer-side engineers. If the headcount thins to the POC-and-discovery tier only, the surviving role's daily work is materially less automatable.
If POC and integration validation increasingly must happen on premises — air-gapped defense/OT environments, hospital networks under HIPAA segmentation, industrial equipment commissioning where the sales engineer physically instruments a customer's line — the physical share of the week rises. Visible in capital-equipment and OT-security sales where customers refuse cloud sandbox trials.
Enterprise procurement norms that require a named vendor technical contact for the POC and go-live, plus buyer distrust of AI-generated capability claims after publicized cases of hallucinated feature support in RFP responses, would push buyers to insist on a human who is personally on the hook for 'yes it does that'. Watch for RFP language requiring disclosure of AI-generated responses — already appearing in some government and large-enterprise RFPs.
If the role consolidates into deal-qualification authority — the person empowered to disqualify a deal, veto a custom commitment, or size scope against engineering capacity — the consequential-call ownership rises. Mechanism to watch: vendors formalizing SE sign-off gates in deal desk process (a technical-win approval that sales cannot override), as some enterprise software firms have instituted after custom-commitment blowups.
Where the sales engineer signs a statement of work, performance guarantee, or technical fit certification that the vendor is contractually bound to, some buyers (and vendor E&O insurers) require a named human attesting the configuration meets stated specs. A concrete watchpoint: FAR/DFARS technical-capability representations on federal solutions sales, and PE-stamped requirements where the sold system is engineered equipment. Only applies to a minority of the SOC; broad licensure for sales engineering is not on any board's agenda.
The limit. Even with every lever, this stays a commercial role with no licensure and no personal liability; the realistic ceiling is upper-50s/low-60s, and it comes almost entirely from thinning headcount into a judgment tier rather than from the occupation becoming protected. The 51,790 count is likely to shrink even as the surviving role's score rises.
| New York-Newark-Jersey City, NY-NJ | 3,440 | $147,570 +18% |
| Dallas-Fort Worth-Arlington, TX | 2,690 | $133,280 +7% |
| Boston-Cambridge-Newton, MA-NH | 2,410 | $136,620 +9% |
| Denver-Aurora-Centennial, CO | 2,010 | $139,990 +12% |
| Los Angeles-Long Beach-Anaheim, CA | 1,770 | $133,380 +7% |
| San Jose-Sunnyvale-Santa Clara, CA | 1,600 | $177,490 +42% |
| Houston-Pasadena-The Woodlands, TX | 1,340 | $127,800 +2% |
| Atlanta-Sandy Springs-Roswell, GA | 1,250 | $99,230 -21% |
| San Jose-Sunnyvale-Santa Clara, CA | 1,600 | $177,490 +42% |
| Durham-Chapel Hill, NC | 330 | $175,310 +40% |
| San Luis Obispo-Paso Robles, CA | 30 | $163,810 +31% |
We have no reported case of a named organisation automating this occupation. Not one deployment, not one announcement.
That is worth saying out loud next to a score of 44. The verdict above is about what the work exposes — what current AI could do to these tasks. It is not a claim that anyone has done it. For this occupation those two things have come apart completely: the capability argument is on this page, and the evidence column is empty.
Has AI actually changed your work? One tap, anonymous, and the running tally is public. Nothing else is asked of you.
Rather than check back: get the digest and we'll tell you what changed — or watch a single occupation from its own page.