SDET (Money Movement)

Qualifications Core engineering: Strong proficiency in at least one of: Python, TypeScript/JavaScript, Go Experience designing and building test frameworks from scratch (not just adding tests to an existing suite) Deep familiarity with API testing — REST, webhooks, idempotency, retry behavior, edge cases at integration boundaries Working knowledge of databases (SQL) and the ability to write test data seeding/cleanup logic correctly Financial systems (strong preference, will train for the right engineer): Experience testing payment flows, ledger systems, or compliance pipelines Understanding of idempotency, double-spend prevention, and eventual consistency in distributed systems Familiarity with webhook-based event systems and out-of-order delivery scenarios CI/CD and infrastructure: Experience integrating test suites into CI pipelines (GitHub Actions, GitLab CI, or similar) Ability to instrument tests for flakiness detection, coverage tracking, and runtime performance Comfort operating in a cloud environment (AWS, GCP) and reading service logs/traces Operational mindset: You can define what "this test passing" actually means in production terms You've contributed to or owned an incident post-mortem with concrete prevention steps You understand canary deployments, feature flags, and how to write tests that survive staged rollouts

What You'll Work On (Day 1 Context) Your first 90 days will likely include: 30 days: map current test coverage against known failure modes; identify the top 3 gaps; ship at least one meaningful test suite that catches a real class of bugs 60 days: own CI quality gates for at least one pod's test suite; establish baseline metrics (coverage %, flakiness rate, regression detection latency) 90 days: reduce bug escape rate measurably; present a test infrastructure roadmap to

the team How We Measure Success Bug escape rate (regressions caught in test vs. caught in production) Time-to-detection for regressions (commit to test failure) Test flakiness rate (< 2% target) Manual testing time eliminated via automation CI pipeline reliability and run time Red Flags We Screen For Test suites that only cover the happy path No incident ownership story ("QA doesn't do oncall") Can't reason about failure modes, retries, or idempotency at the code level Treats test coverage % as the goal rather than a signal Cannot explain the business impact of a quality gap What We Offer Work on infrastructure that handles real money for millions of users A team that treats quality as a first-class engineering problem, not a compliance checkbox Remote-friendly with a distributed, high-ownership engineering culture. We strongly encourage candidates of all different backgrounds to apply. We believe that our work is stronger with a variety of perspectives, and we’re eager to further diversify our company. If you have a background that you feel would make an impact at Phantom, please consider applying. We’re committed to building an inclusive, supportive place for you to do the best work of your career. By submitting your resume and application materials, you acknowledge and agree that Phantom may use automated tools, including AI systems, and may engage trusted third-party service providers to process your application and ensure an efficient hiring process. Phantom does not sell your information and your materials will be handled securely and in accordance with applicable data protection laws.

A meeting lands on your calendar

If they’re a yes, I book the chat. You show up — that’s the whole job-hunt.