[Hiring] SDET Intern @Tokenmetrics

Role Description

We are building a mobile-first passive investing app on HyperEVM. Our software handles real user funds and there is no undo button on-chain. Reliability and safety are core product features. This role builds automated testing and quality gates that catch failures in CI before they reach users.

• Build and maintain an automated defense system for our highest-risk flows:
• Wallet connection
• USDC deposit and withdraw
• Portfolio selection
• Rebalance and risk guardrails
• veTMAI membership gating

Stack

• Mobile automation: Maestro (YAML-based flows for mobile UI and WebViews)
• Smart contract testing: Foundry (unit tests, fuzzing, invariants)
• Web automation: Cypress (secondary coverage for the read-only web dashboard)
• CI/CD: GitHub Actions
• Core code: TypeScript (React Native) and Solidity (ERC-4626 vaults)

Requirements

• Must-haves:
• You are engineering-first.
• You write automation as production-quality code, not record-and-playback scripts.
• Experience with at least one mobile E2E tool: Maestro, Detox, or Appium.
• Comfortable with CI/CD and GitHub Actions workflows.
• Strong debugging habits:
• You read logs, isolate root cause, and fix determinism issues.
• Clear written communication and consistent progress updates.
• Nice-to-haves:
• DeFi familiarity:
• ERC-20 approvals, wallet signatures, and basic transaction states (submitted, confirmed, reverted).
• Foundry experience (or strong Solidity testing instincts).
• Experience testing React Native apps with WebViews.
• Experience shipping in a fast-moving startup environment.

Interview Process

• Portfolio review: We review your GitHub and look for evidence you built automation, CI, or test infrastructure that shipped.
• Take-home build: We provide a simple React Native build and ask you to produce a working Maestro flow plus a minimal CI workflow.
• Technical walkthrough: You explain your selector strategy, wait strategy, failure handling, and how you would scale coverage.

To Apply

• Send:
• GitHub link (or a code sample)
• A short note describing the hardest test automation problem you solved and how you approached it