Quality Assurance QA Engineer

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 OneAssets 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
  
  

• Onboarding and identity states
• Wallet and custody interactions
• Portfolio and yield visibility
• Claim, restriction, and settlement behaviours

• Success states
• Failure states
• Pending and asynchronous states

• KYC/KYB failures, expirations, and rechecks
• Restricted or blocked actions
• Partial failures, retries, and timeouts
• Delayed or withheld outcomes (e.g., yield, settlement)

• MVP stabilisation
• Post-MVP feature additions

• Clarify acceptance criteria
• Validate test coverage

• Reproduce issues consistently
• Verify fixes against original intent

• User impact
• Compliance risk
• Launch criticality
• 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
  

• 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
  

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

• 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
  
  

• 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.
  
  

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

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