SDET - Indigo

What you’ll do

Build out our automated testing suites. Own the end-to-end layer in Playwright and TypeScript, in the same Nx monorepo the product lives in, and help strengthen the unit and integration layers underneath
Own quality strategy: what gets automated, what gets a dedicated QA pass, and what isn’t worth testing at all
Go deep on high-impact featuresets. When a release has real blast radius, you plan and run the QA for it
Own CI test signal and the test data problem. A red build should mean something is actually broken, and engineers should trust the suite
Do hands-on exploratory testing on high-risk surfaces: payments and billing, telephony, integrations, real-time sync
Turn production incidents into regression tests so the same bug never ships twice

Weeks 1-4, mostly manual on purpose. Learn ProVision by testing it by hand. Build a risk map: what breaks, what hurts when it breaks, what nobody is watching.
Weeks 5-12, build against what you found. Stand up the E2E suite over the highest-risk flows, running reliably in CI, and get the team using it.
Beyond, roughly 70/30. Mostly automation and test infrastructure, the rest exploratory and release work. You’ll keep touching the product by hand. That’s the job, not a detour from it.

5+ years in QA, with at least 3 building and owning test automation for a production web application
You’ve built a test framework, not just written tests inside someone else’s. We’ll ask you to walk us through one
Strong TypeScript or JavaScript. You’ll write real code in our repo, reviewed like any other code
Hands-on Playwright, Cypress, or similar. Playwright is what we use
Judgment about what not to automate, and a real approach to flaky tests beyond retries
Comfortable testing APIs and backend behavior, not only the UI
You still test by hand and you’re good at it. You find the bug nobody wrote a ticket for
High ownership and excellent written English. Most of our work happens async, in writing (pull requests, design docs, Linear, Slack)
Meaningful working-hours overlap with US Eastern

CI/CD pipeline work: GitHub Actions, test parallelization, keeping suite runtime sane
Testing multi-tenant B2B SaaS, especially tenant isolation and permissions
Testing payments (Stripe), telephony, or event-driven systems: queues, webhooks, WebSocket sync
Using AI tooling to accelerate test authoring and maintenance, with opinions about where it helps and where it doesn’t

You aren’t expected to have shipped everything below, but you should be excited to work close to most of it.

Language: TypeScript end-to-end
Frontend: React, Material UI, Vite, GraphQL clients
Backend: Node.js Lambdas, AppSync (GraphQL), a Hono-based REST Public API, EventBridge, SQS, DynamoDB
Data: Postgres (Aurora), tsvector-based full-text search, real-time sync engine over WebSockets
Infra & Observability: AWS, CDK, Sentry, CloudWatch
Testing & Tooling: Playwright, Vitest, pnpm + Nx monorepo, Linear, Slack, Notion, Claude Code

Minimum bureaucracy, direct access to leadership. You’ll work directly with the Head of Engineering. The rest of the time is for building.
Six-week cycles. Long enough to do something real, short enough to course-correct.
Engineers own domains end-to-end, from architecture through rollout and ongoing health. Nothing gets thrown over the wall, including to you. Quality is shared; you own the system that makes it possible.
Async-first, writing-first. Most decisions happen in pull requests, design docs, Linear, and Slack threads. Meetings are for things writing can’t do.
AI-native by default. We use AI tooling across the team and expect everyone to be fluent and opinionated about where it helps and where it doesn’t.

A condensed version of our company values:

Be ferociously curious. If a problem matters, go dig. Try to prove yourself wrong.
Be proactively transparent. Speak your mind early and often. Give and receive feedback respectfully.
Be tenacious. The important problems are hard. Working through difficulty is how we differentiate.
Take action, thoughtfully. Measure twice, cut confidently.
Own the experience. Take responsibility for great outcomes.
Embrace mistakes. Fail fast, fail forward, share what you learn.
Practice EQ, not just IQ. No brilliant jerks.
Put the partner first. Their challenges are our North Star.