off-the-stack
cd ~/careers
Quality engineeringaka "SDET"

Software Engineer in Test

A real software engineer whose product is confidence — and it pays like engineering, because it is.

Entry
$80k
Mid
$120k
Senior
$170k+
Demand
High

The SDET writes code to test code: automation frameworks, end-to-end suites, performance and reliability harnesses that catch failures before users do. It's a world away from manual QA clicking through screens — it's engineering, with the same languages and rigor — and it's chronically undervalued by people who assume 'testing' means 'junior'.

The myth

QA is a stepping stone, not a career.

The reality

An SDET builds test frameworks, CI test infrastructure, and performance harnesses in real code. It's a senior engineering discipline with its own deep specialism.

cat ./what_you_actually_do.md

  • Build and own automated test frameworks across UI, API, and integration layers.
  • Write end-to-end and performance suites that run in CI on every change.
  • Design for testability and push quality upstream into how features get built.
  • Hunt the flaky tests and gaps that erode everyone's trust in the suite.
  • Make 'ship with confidence' a real, measurable property of the codebase.

cat ./why_underrated.md

The word 'testing' carries a junior stigma that scares ambitious people away, so they never learn that modern test engineering is just engineering with a different goal. But every company that's ever shipped a catastrophic bug knows what good SDETs are worth, and the supply of engineers who can architect serious test automation — not just record-and-playback scripts — is thin. It's a stable, well-paid specialty hiding behind an unglamorous name, and it travels with you to any stack.

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

  • Engineers with a destructive streak who enjoy finding how things break.
  • Systems thinkers who like building tools and infrastructure.
  • People who take quiet pride in catching the bug before the customer does.

cat ./pay.md

Pay tracks software engineering because the work is software engineering. Senior SDETs and test-architecture leads at companies that take quality seriously clear $160k+, and the role is far more stable than feature work during downturns — broken software is expensive everywhere.

./break_in.sh

  1. Automate a real app's tests

    Pick an open-source app, build an end-to-end suite with Playwright or Cypress, and publish it. That's your portfolio.

  2. Get strong in one language

    SDET work is coding work. Solid JavaScript/TypeScript, Python, or Java is the foundation, not a nice-to-have.

  3. Learn the CI side

    Running tests reliably in a pipeline — parallelization, flakiness, reporting — is what separates an SDET from a script-writer.

  4. Apply to quality-serious teams

    Fintech, healthcare, and infra companies treat test engineering as the senior discipline it is, and pay for it.

tail -f ./a_day.log

  • 09:00A flaky end-to-end test failed the build overnight; reproduce, diagnose, and stabilize it.
  • 11:00Extend the API test framework to cover a new service's edge cases.
  • 14:00Build a small performance harness to catch a latency regression before release.
  • 16:00Pair with a feature team on making their new module testable from the start.

ls ./toolbelt

  • TypeScript / Python / Java
  • Playwright / Cypress
  • API testing tools
  • CI/CD
  • Performance tooling
  • Docker