SDET (Money Movement)

Role Overview

Phantom is hiring an SDET (Money Movement) to think like an engineer and test like one too. This is an engineering role focused on quality, where you design and own test infrastructure for financial-grade systems such as payment flows, KYC pipelines, card transactions, and compliance rails.

Responsibilities

• Build and own the test automation platform for Money Movement:
  • End-to-end tests, API contract tests, and integration test suites
  • Cover funding rails, card transactions, KYC flows, and cash account operations
• Create and maintain CI/CD quality gates to run tests on every PR and block regressions
• Implement failure-mode coverage for scenarios like:
  • Duplicate charges, partial KYC completions, webhook replay
  • Idempotency violations, provider outages
• Perform performance and load testing to catch latency regressions before production (e.g., p95)
• Own test data and environment infrastructure to keep tests repeatable, isolated, and fast
• Provide observability for test quality using metrics such as:
  • Coverage, flakiness, bug escape rates, and regression detection latency

Requirements

• Strong engineering background and proficiency in at least one of:
  • Python, TypeScript/JavaScript, or Go
• Experience designing and building test frameworks from scratch
• Strong API testing knowledge (REST, webhooks, idempotency, retry behavior, edge cases)
• Working knowledge of SQL and ability to implement correct test data seeding/cleanup

Nice to Have

• Experience testing financial systems (payments, ledger systems, or compliance pipelines)
• Understanding of idempotency/double-spend prevention and eventual consistency
• Familiarity with webhook-based event systems and out-of-order delivery
• CI integration experience with GitHub Actions or GitLab CI
• Comfort operating in cloud environments (AWS, GCP) and reading logs/traces
• Experience defining success criteria for production quality and contributing to incident post-mortems

Day 1 Focus

• Address test coverage gaps in:
  • KYC state machine transitions
  • On-ramp provider failure paths
  • Card authorization edge cases