off-the-stack
cd ~/careers
Pre-sales / technicalaka "SE"

Solutions / Sales Engineer

The technical co-pilot on every big deal — and frequently the highest earner in engineering.

Entry
$100k
Mid
$160k
Senior
$240k+
Demand
High

The Solutions Engineer is the technical half of a sales team: you run demos, design proof-of-concepts, answer the customer's hard architecture questions, and make a complex product make sense to the people writing the check. It is one of the best-kept secrets in tech compensation, because pay comes with a commission engine attached.

The myth

You'll be a salesperson who lost their soul.

The reality

You're the technical truth-teller in the room. The best SEs win deals precisely by being honest about fit, and they build more real demos than most engineers ship features.

cat ./what_you_actually_do.md

  • Run technical demos tailored to a specific customer's stack, not the canned script.
  • Design and build proof-of-concepts that prove the product works in the customer's real environment.
  • Answer the deep architecture, security, and integration questions a salesperson can't.
  • Write the responses to brutal security questionnaires and RFPs that decide enterprise deals.
  • Carry the field's reality back to product, since you see exactly where the product fails to close.

cat ./why_underrated.md

CS students never hear about it because it's filed under 'sales', a word that scares away the technical crowd on contact. But the role is deeply technical, the comp is among the highest in the building, and burnout is generally lower than in quota-carrying sales because your number is shared and your job is to be right, not pushy. The people who discover it usually do so by accident — a SWE who got pulled into a customer call and realized they were good at it, and that it paid more.

grep -i 'good fit' ./who.md

  • Engineers who light up presenting and thinking on their feet.
  • People who want their income tied to outcomes, with upside.
  • Generalists who like seeing many customer architectures instead of one codebase forever.

cat ./pay.md

Comp is base + variable, typically a 70/30 or 75/25 split, and the totals are why people quietly move from SWE into SE. Senior SEs at strong infra/data companies routinely clear $220–300k all-in — often more than the engineers building the product they're selling.

./break_in.sh

  1. Reframe your demo skills

    Every demo you've given, every talk, every time you explained tech to a non-engineer — that's the core of the job. Surface it.

  2. Learn the sales motion

    Understand discovery, qualification, and the POC cycle. Speaking the commercial language is what gets you taken seriously.

  3. Move from a SWE seat

    The cleanest path is lateral: be a SWE who's great with customers, then transfer. Companies love internal SE converts.

  4. Interview with a live demo

    Most SE loops include a 'demo this product to us' exercise. Nail the storytelling and you're most of the way there.

tail -f ./a_day.log

  • 09:00Prep a tailored demo against a prospect's actual architecture, not the generic deck.
  • 11:00Technical discovery call: ask the sharp questions that decide whether this deal is even real.
  • 14:00Build a POC in a trial environment proving the integration the customer is worried about.
  • 16:00Knock out a 200-line security questionnaire that's blocking a six-figure deal.

ls ./toolbelt

  • The product, deeply
  • Cloud platforms
  • SQL & APIs
  • Demo environments
  • Architecture diagramming
  • Slides that don't suck