SDET (Money Movement)

Role overview

Phantom is hiring an SDET (Money Movement) who thinks like an engineer and tests like an engineer. This is an engineering role focused on quality as an output surface, owning test infrastructure for financial-grade systems at startup speed.

What you’ll own

• Test automation platform for Money Movement
  • End-to-end tests
  • API contract tests
  • Integration test suites for:
    • funding rails
    • card transactions
    • KYC flows
    • cash account operations
• CI/CD quality gates
  • Design, implement, and maintain test pipelines running on every PR and blocking regressions
• Failure mode coverage
  • Build tests for real failure scenarios such as:
    • duplicate charges
    • partial KYC completions
    • webhook replay
    • idempotency violations
    • provider outages
• Performance & load testing
  • Validate payment flows under peak load
  • Detect latency regressions before they impact production (e.g., p95)
• Test data & environment infrastructure
  • Tooling to make tests repeatable, isolated, and fast
• Observability for test quality
  • Track metrics like coverage, flakiness, bug escape rate, and regression detection latency

Qualifications

• Core engineering skills: strong proficiency in at least one of:
  • Python
  • TypeScript/JavaScript
  • Go
• Test framework engineering: experience designing/building test frameworks from scratch
• API testing expertise: REST, webhooks, idempotency, retry behavior, edge cases at integration boundaries
• Database/testing: working knowledge of SQL and correct test data seeding/cleanup
• Financial systems (preferred):
  • Experience testing payment flows, 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/CD & infrastructure

• Integrate test suites into CI pipelines (e.g., GitHub Actions, GitLab CI, or similar)
• Instrument tests for flakiness detection, coverage tracking, and runtime performance
• Comfort operating in cloud environments (AWS, GCP) and reading service logs/traces

Operational mindset

• Define what “test passing” means in production terms
• Contributed to/owned incident post-mortems with concrete prevention steps
• Understand canary deployments and feature flags; write tests that survive staged rollouts

Day 1 focus (Money Movement team)

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