off-the-stack
cd ~/careers
Post-sales / technicalaka "CSE"

Customer Success Engineer

The engineer who makes sure the product actually works for the people paying for it.

Entry
$80k
Mid
$115k
Senior
$160k+
Demand
High

Half the day you're reading code and reproducing bugs; the other half you're on a call keeping a $400k account from churning. You sit between the customer's engineers and your own — too technical for plain support, too people-facing for a backend team. It is one of the few engineering-adjacent roles where being good at humans is a raise, not a rounding error.

The myth

It's glorified customer support.

The reality

Support closes tickets. A CSE owns whether a technical buyer renews — you debug, you write integration code, you influence the product roadmap with the receipts to back it.

cat ./what_you_actually_do.md

  • Reproduce customer bugs against real code and file the issue your own engineers will actually act on.
  • Write sample integrations, SDK snippets, and the occasional Terraform module so a customer's team gets unblocked today, not next sprint.
  • Run technical onboarding: architecture reviews, environment setup, the migration plan nobody read the docs for.
  • Translate angry-customer noise into a prioritized signal product and engineering can trust.
  • Sit in renewal and expansion conversations as the technical credibility in the room.

cat ./why_underrated.md

CS Engineering grew up inside the SaaS boom and never got a clean career story told about it, so CS students walk right past it. It rewards the exact combination schools don't grade: you can read a stack trace AND you can de-escalate a furious VP. Because the value maps directly to retained revenue, the ceiling is higher and the job is far stickier than its 'support-adjacent' reputation suggests.

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

  • Engineers who like the problem AND the person attached to it.
  • People energized, not drained, by a hard conversation.
  • Generalists who'd rather touch ten systems shallowly than one deeply.

cat ./pay.md

Base looks lower than a SWE role, but most CSE seats carry a variable component (retention/expansion bonus) that adds 15–30%. At a fast-growing infra or dev-tools company, senior CSEs with a strong book clear $180k+ all-in.

./break_in.sh

  1. Show the hybrid

    Pair one shipped technical project with one example of you teaching or supporting someone through something hard. The combination is the whole pitch.

  2. Target dev-tools & infra companies

    The more technical the product, the more a CSE is treated as an engineer. Stripe, Datadog, HashiCorp, Twilio and their long tail of competitors.

  3. Learn the renewal motion

    Read about net revenue retention, churn, and expansion. Speaking the commercial language is what separates you from a support applicant.

  4. Interview with a reproduction

    Ask for a real product, hit a wall on purpose, and walk them through how you'd debug it live. That demo closes the loop.

tail -f ./a_day.log

  • 09:00Triage overnight tickets from enterprise accounts; one is a genuine bug, you write the repro.
  • 11:00Onboarding call: walk a customer's platform team through SSO setup, screen-share some config.
  • 14:00Build a small proof-of-concept integration to show an account what's possible before they churn.
  • 16:00Sync with Product, armed with three customer quotes that move a roadmap item up.

ls ./toolbelt

  • A real programming language
  • SQL
  • Postman / API tooling
  • Zendesk / Intercom
  • Gainsight
  • The product's own SDKs