{ "source": "Cooked Index — occupational AI risk register", "page": "https://cookedindex.com/jobs/sales-engineers/", "methodology": "https://cookedindex.com/methodology", "notice": "Verdicts are re-examined as evidence accumulates. Re-fetch before relying on this; the page above always carries the current score.", "scored_at": "2026-08-11", "model": "claude-opus-5", "occupation": { "title": "Sales Engineers", "soc_code": "41-9031", "category": "Sales", "us_employment": 51790, "median_annual_wage": 124900 }, "verdict": "EXPOSED", "risk_resistance": 44, "contested": false, "near_boundary": false, "dimensions": { "task_resistance": 9, "embodiment": 8, "liability_shield": 2, "trust_premium": 14, "judgment_accountability": 11 }, "reasoning": { "task_resistance": "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.", "embodiment": "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.", "liability_shield": "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.", "trust_premium": "At 14, the buying engineer's willingness to believe 'no, our product won't do that' is the asset — that credibility is built over multi-quarter evaluation cycles and follows the individual to their next employer — though it stops short of 18 because the account is co-owned with the AE and backed by the vendor's brand, reference customers, and support organization rather than resting on one person's name.", "judgment_accountability": "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." }, "rationale": "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.", "outlook": "The role persists in complex, high-ticket, integration-heavy sales but shrinks meaningfully as AI absorbs RFP response, quoting, and first-line technical Q&A, concentrating headcount around field pilots and solution design.", "what_would_raise_it": { "levers": [ { "dimension": "task_resistance", "change": "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.", "plausibility": "already happening", "would_add": 4 }, { "dimension": "embodiment", "change": "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.", "plausibility": "plausible", "would_add": 3 }, { "dimension": "liability_shield", "change": "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.", "plausibility": "unlikely", "would_add": 2 }, { "dimension": "trust_premium", "change": "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.", "plausibility": "plausible", "would_add": 3 }, { "dimension": "judgment_accountability", "change": "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.", "plausibility": "plausible", "would_add": 3 } ], "ceiling_note": "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." }, "adjudication": null, "employment_history": { "points": [ { "y": 2017, "emp": 70820, "wage": 98720 }, { "y": 2018, "emp": 65720, "wage": 101420 }, { "y": 2019, "emp": 63550, "wage": 103900 }, { "y": 2020, "emp": 63780, "wage": 108830 }, { "y": 2021, "emp": 59550, "wage": 103710 }, { "y": 2022, "emp": 59700, "wage": 108530 }, { "y": 2023, "emp": 59340, "wage": 116950 }, { "y": 2024, "emp": 56690, "wage": 121520 }, { "y": 2025, "emp": 51790, "wage": 124900 } ], "from": 2017, "to": 2025, "change_pct": -26.9, "comparable_from": 2019, "spans_soc_revision": true }, "pivots": [], "license": "https://cookedindex.com/terms" }