QA Engineer

At My Funded Futures, we’re transforming the world of proprietary trading by giving traders the capital, tools, and community they need to succeed.

We blend innovation, transparency, and performance to create opportunity — helping traders scale faster and smarter. If you’re passionate about fintech, financial markets, and data-driven growth, you’ll fit right in.

Explore our open roles below and see how you can help us shape the future of funded trading.

Position Summary

Join MyFundedFutures as the next QA Engineer responsible for ensuring that every release that reaches production meets a high bar for quality, stability, and correctness. This is a hands-on role with genuine ownership. You are the gate between code-complete and thousands of users.

You will work closely with product and engineering to define acceptance criteria, have thorough manual test and debugging skills, own the staging environment, build and maintain automation coverage and drive a culture where quality is everyone's responsibility and QA is the last line of defence, not an afterthought.

Key Responsibilities

• Own the QA gate for every release - nothing reaches production without the QA sign-off.
• Radiate knowledge of the trading products and asset classes the platform supports — including equities, futures, and leveraged instruments — so that test coverage reflects real-world user behavior, risk scenarios, and edge cases that matter in live trading environments.
• Stay current with changes to supported asset classes, new product offerings, and evolving platform capabilities; proactively update test plans and regression coverage as the product horizon expands.
• Execute end-to-end regression across all release tickets, verifying against defined acceptance criteria.
• Conduct production smoke tests of every production deploy, validating critical paths are intact.
• Maintain a stable, predictable Staging environment that PM and product can rely on for UAT.
• Build, maintain, and extend the automated regression suite covering critical user journeys: account creation, trading flows, payouts, and authentication.
• Own E2E test coverage; partner with developers on integration and API test coverage.
• Integrate regression suites into CI pipelines so every RC build is automatically validated before manual testing begins.
• Drive automation coverage toward a state where manual regression is focused on new features, not re-testing known-good functionality.
• File all bugs in Jira with clear reproduction steps, environment details as defined.
• Triage and prioritise incoming bugs; communicate release-blocking issues to the product engineering team.