AI-Native Product QA Engineer (Business Flows & Operational Quality)

MUST Company; Angola (IN); Hybrid; USD 90,000 - 150,000; Full time

Job summary

MUST Company is hiring an AI-native Product QA Engineer to own operational quality across live crypto wallet and marketplace products. The role emphasizes business flow testing, time-zone handling, and automated regression using AI-assisted test design.

You will ensure the product works for real users once live and prevent post-release failures. The position is fully remote, full-time, and open to candidates worldwide.

Qualifications

• 2+ years of QA/test engineering experience for live products used by real customers.
• Hands-on testing of web applications and APIs (functional, integration, regression, end-to-end).
• Experience investigating production incidents, identifying root causes, and creating regression tests.

Responsibilities

• Test against business rules and real user flows, including edge cases and time-based rules.
• Review features against real user journeys, including notifications, login, admin settings, and configurations.
• Create regression tests for every incident or support case and map repeat issues to backlogs.

Skills

QA engineering

Test automation

API testing

Web testing

Edge case analysis

Release readiness

AI tools

Education

Bachelor's degree or equivalent in QA/CS

Tools

Playwright

Cypress

Postman

Selenium

Job description

AI-Native Product QA Engineer (Business Flows & Operational Quality)

An engineer who understands business velocity and takes ownership of real-world operational quality

What is an AIC?

AIC stands for AI-native IC (Individual Contributor). Moving beyond simply using AI as a support tool, an AIC integrates AI into every step of designing, executing, and validating work, taking direct end-to-end ownership of their outcomes.

Rather than people management, this role prioritizes the ability to leverage AI to get critical work done quickly while ensuring uncompromising quality for real end-users.

About MUST Company

MUST Company is a South Korea-based company building AI-native products. This role is fully remote, full-time, and open to candidates based in any of the countries listed on this posting.

About the Role

We ship fast. What has hurt us is what comes after: small gaps in a live product that turn into weeks of operation support. A user's settlement alert never arrives. A user completes a task on Sunday, settlement runs on Tuesday, and nobody can say whether it counts. Each case is small, but together they pull engineering time away from building.

We are hiring a QA engineer who stops these cases before users find them. You understand how the business works and how users actually move through the product, and you test against that, not only against the ticket. When a prototype works, you are the person who makes it ready to operate: the edge cases, the dates and time zones, the notifications, the admin settings, the failure paths and the recovery.

This is not a test-case-counting role, and it is not a business-lead role. You will not own the business direction. You will own whether the product works for real users once it is live, and your impact is measured by how much repeat failure and after-the-fact support disappears.

You will work across our live crypto wallet and marketplace products: weekly settlements and payouts, date-based participation rules, seasonal programs, in-app token swaps, notifications and the admin console.

AI is part of how you work (generating test scenarios, reading logs, reproducing issues, automating regression), but you remain accountable for the judgment and the outcome.

What you will own

• Learn the business rules end to end (who gets paid what, when, and why) and turn them into testable scenarios before release
• Review every feature and proof of concept before release against real user flows, including dates, time zones, weekends and cut-off times, notification delivery, account and login changes, and admin configuration
• Turn every support question or incident into a root cause and a regression test, so the same case does not come back
• Track repeat operation-support requests, group them by cause, and push the top causes into the backlog with clear acceptance criteria
• Build and maintain automated regression for the flows that move money or trigger user notifications
• Define release readiness (what must pass before a change goes live) and hold the line on it
• Work with engineers, product owners and the operations team so fixes land in the product, not in manual workarounds

What success looks like

• First 30 days: the business rules for settlements, participation and notifications are documented as test scenarios, and the last three months of operation-support requests are mapped to root causes
• First 60 days: every release in your scope passes a defined readiness check, and the top repeat support causes have fixes or regression tests in place
• First 90 days: repeat support requests for the flows you own are measurably down, and fewer production issues are found by users instead of by QA

Submission Requirements

• Portfolio or case write-ups (links are fine) covering 2-4 cases where you found a defect or gap before users did, or turned a production issue into a lasting fix. For each case: the business context, what you found, how you found it, what changed, and the result.
• A Loom video of no more than 5 minutes: one case where your testing prevented operation support or a production incident, how you use AI in your QA work, and what you personally owned.
• Do not submit confidential information, personal data, credentials or API keys from past employers.

Evaluation Criteria

• Business understanding: do you test against how the business and its users actually work, not only against the ticket?
• Prevention: can you show defects or edge cases you caught before release?
• Root cause: do you fix the cause and add the test, or only close the ticket?
• Impact: can you show fewer incidents, fewer repeat support requests or safer releases?
• AI and automation: can we see what you delegated to AI or automation and what you verified yourself?

Quest Assessment

Choose a high-impact failure in a settlement, payout or notification flow. Reproduce it, establish the business rule, and build a regression check that prevents it from returning. Pass: 76/100 or higher. Required: Loom, intent.md and final directive.md.

Use a local demo, an open-source sample, or your own sanitized project. Suggested fictional case: a rewards service settles completed tasks every Tuesday at 09:00 UTC for the previous Monday 00:00 UTC through the following Monday 00:00 UTC, with the upper boundary excluded. Each qualifying task earns 10 test credits. Task IDs must be counted once; retries must not create a second payout. A notification is sent only after a successful payout, and notification failure must not reverse that payout. These are assessment rules, not a description of a live MUST product. You may instead define an equally concrete business flow with explicit rules.

What to do:

• List at least three possible failure problems and rank them by user impact, frequency or likelihood, and effort. Choose one to solve deeply. Explain uncertainty rather than inventing incident history.
• Map the flow and write at least eight test cases with inputs and expected outcomes, covering the happy path, a cut-off boundary, a timezone conversion, duplicate input, a retry, and partial failure. State any assumptions about account changes or admin settings.
• Implement a minimal reproducible fixture and automated checks for the selected failure. Show the regression failing against the faulty behavior and passing after a fix or corrected reference implementation. Do not test a live financial system.
• Produce one actionable defect report with reproduction steps, expected versus actual behavior, severity rationale, root cause, evidence and a proposed fix. Explain which release checks would block this failure.
• Demonstrate the final test run, record remaining gaps, and give a short release-readiness decision and handoff instructions.

Role-specific outputs to link from directive.md: A runnable test project or exported test collection, eight or more cases and results, a defect/root-cause report, and a release-readiness checklist.

Submit a Loom video of no more than 5 minutes, intent.md explaining why you chose the problem and how you prioritized alternatives, and the final directive.md with objective, scope, requirements and completion criteria. Include accessible links to your work and verification evidence in a results/handoff appendix in directive.md. Earlier directive versions, problem.md, agents.md, claude.md and career_leverage.md are optional.

The role-specific Quest brief contains the full instructions and weighted rubric. Scores are whole points out of 100; 76 or above passes and 75 does not. This is separate from the profile match score. The reviewer records the final evaluation. The invitation states the exact deadline/timezone and any compensation terms before participation.

Requirements

Required Qualifications2+ years of experience in QA, test engineering, or quality ownership for live products used by real customersHands-on experience testing web applications and APIs, including functional, integration, regression, and end-to-end testingProven ability to identify edge cases and defects in business rules, user flows, permissions, configurations, and system behaviorExperience investigating production incidents or support tickets, identifying root causes, and creating regression tests to prevent recurrenceHands-on experience with test automation for web applications or APIs, using tools such as Playwright, Cypress, Postman, Selenium, or similarComfortable reading logs, API responses, and database records to reproduce and troubleshoot issuesAbility to create clear and actionable bug reports, test plans, test cases, and release documentationStrong written English and ability to communicate effectively with developers, product teams, and operationsHands-on use of AI tools in QA work, such as test design, test case generation, log analysis, debugging, or automation

Preferred QualificationsExperience testing Web3 products, including crypto wallets, wallet connections, token swaps, on-chain transactions, quests, waitlist registration, or other blockchain-based user flowsExperience with web3/API integrations and blockchain transaction validationExperience testing mobile applications, particularly FlutterExperience testing Node.js backends and APIsExperience testing push notifications, SMS, or messaging deliveryExperience owning release readiness, regression testing, or quality gates in a fast-moving environmentExperience working with operations or customer-support teams to identify recurring issues and reduce ticket volumeExperience working with distributed, multi-country teamsExperience testing payments, settlement, payouts, or financial workflows — valuable but not required

Skills: QA engineering, test automation, business rule testing, edge case analysis, root cause analysis, regression testing, release readiness, API testing, mobile app testing, fintech, crypto wallets, AI tools