Quality Assurance (QA) Engineer at OneAsset · Dubai

OneAsset is a regulated Real-World Asset (RWA) platform for compliant on-chain tokenisation, yield distribution, secondary trading, and governance of real estate and private assets.

The platform is built as a modular, state-driven system operating under strict requirements for correctness, auditability, and regulatory clarity.

At OneAsset, execution quality is system-critical, and QA is a core reliability function, not a downstream checkpoint.

Role Overview

The QA Engineer is responsible for ensuring that OneAsset’s MVP and post-MVP releases behave exactly as specified, across all happy paths, edge cases, and failure scenarios.

This role exists to:

• Detect inconsistencies before users, partners, or regulators do
• Validate that product behavior matches documented requirements
• Protect launch credibility and operational confidence

This is not a superficial UI testing role. It is a state, flow, and correctness-focused QA role in a compliance-sensitive platform.

Core Responsibilities

1. Functional & Flow-Based Testing

• Validate end-to-end user flows including:
  • Onboarding and identity states
  • Wallet and custody interactions
  • Portfolio and yield visibility
  • Claim, restriction, and settlement behaviours
• Ensure flows behave correctly across:
  • Success states
  • Failure states
  • Pending and asynchronous states
• Confirm that user-visible behavior matches defined requirements and acceptance criteria.

1. Non-Happy Path & Edge-Case Validation

• Actively test and validate:
  • KYC/KYB failures, expirations, and rechecks
  • Restricted or blocked actions
  • Partial failures, retries, and timeouts
  • Delayed or withheld outcomes (e.g., yield, settlement)
• Identify undefined or ambiguous behavior early and escalate to PM/BA.

1. Regression & Release Readiness

• Own regression testing for:
  • MVP stabilisation
  • Post-MVP feature additions
• Ensure fixes do not introduce new issues in previously validated flows.
• Provide clear go / no-go input for releases based on functional readiness.

1. Collaboration & Defect Triage

• Work closely with PM/BA to:
  • Clarify acceptance criteria
  • Validate test coverage
• Collaborate with engineering to:
  • Reproduce issues consistently
  • Verify fixes against original intent
• Participate in defect triage with a focus on:
  • User impact
  • Compliance risk
  • Launch criticality

1. Test Documentation & Quality Signals

• Maintain structured test artifacts including:
  • Test cases
  • Scenario matrices
  • Known risk areas
• Ensure test documentation is usable for:
  • Release validation
  • Audit support
  • Knowledge transfer

Experience & Skills Required

Required

• 3–6+ years experience in a QA or software testing role
• Strong experience testing:
  • Complex, state-driven applications
  • Workflow-heavy systems
• Ability to:
  • Think in edge cases
  • Document findings clearly
  • Communicate issues precisely
• Comfortable working closely with engineering and product teams

Preferred

• Experience in fintech, Web3, or regulated environments
• Exposure to custody, payments, or financial workflows
• Familiarity with basic test automation concepts (manual-first is acceptable)

KPIs & Success Metrics

• MVP released with no critical undiscovered functional defects
• Reduction in high-severity defects over time
• Regression issues detected before release, not after
• QA feedback actively used in product and engineering decisions
• Confidence from product and engineering in QA release signals

What Success Looks Like

By MVP Rollout (February 28)

• MVP flows behave exactly as specified across all tested scenarios.
• Edge cases and failure paths are validated, not assumed.
• Launch confidence is based on testing, not optimism.

By Alpha & Beta (March–June)

• Platform stability improves as new features are added.
• Regression defects decrease, not increase.
• QA becomes a trusted quality gate, not a blocker.

By Mainnet (Early July)

• OneAsset reaches Mainnet with predictable, test-validated behavior.
• QA processes are repeatable and reliable.
• Quality risks are identified early, not discovered in production.