About us

Role Overview

Responsibilities and Duties

• Domain Ownership: Own the quality and risk picture for an assigned domain (for example mobile, funding and trading, or backend services). Know its architecture, its integrations, its failure modes, and its history well enough to be the team's reference point on it.
• Risk-Based Test Strategy: Decide what to test and what to leave untested, and justify both. Produce release risk assessments that state the residual risk plainly so the business can make an informed ship decision.
• Feature Ownership: Take assigned features from requirements through release sign-off. Be the person accountable for whether that feature was adequately tested.
• Test Design: Write your own test cases from requirements, acceptance criteria, and how the product actually works, including negative paths, boundary conditions, and error states as well as the happy path. Maintain them as the product changes.
• Test Execution: Carry out manual and automated testing across mobile, web, and backend services, with repeatable results and clear records of what was run and what passed.
• Defect Reporting and Investigation: Identify, reproduce, and document defects clearly. Isolate reliable reproduction steps, narrow down where the problem sits, and keep verified observation separate from your own analysis in the write-up.
• Test Automation: Write and maintain automated test coverage using tools such as Playwright, Appium, WebdriverIO, and JavaScript, with support from senior team members where needed.
• Documentation: Keep test cases, test results, and QA documentation organized and current, so that the team's coverage is transparent and someone else could pick it up.
• Platform Knowledge: Build working knowledge of the platform's architecture and integrations, including how the client, API, backend services, and data layer fit together, and use it to inform what you test.

• Cross-Functional Partnership: Work directly with developers, product managers, and designers on the features you test. Ask the questions that surface gaps in requirements early, and follow them to an answer.
• Communication: Report status, findings, and risk clearly to both technical and non-technical audiences. Escalate as soon as something looks likely to affect a release. Early escalation is expected here.
• Peer Review: Take part in second-QA review of teammates' test cases and bug reports, and act on the feedback you receive on your own.

• Grow Your Depth: Build your testing craft and your knowledge of the product domain you work in most, working toward owning that domain's risk picture.
• Contribute to QA Practice: Suggest and help implement improvements to QA tooling, templates, and workflow. Help shape the team's shared standards as well as following them.

Qualifications and Skills

• Bachelor's degree in Computer Science, Software Engineering, or related field preferred (or equivalent work experience).

• 2+ years of experience in quality assurance or software testing, including testing features independently from requirements.
• Experience across both frontend and backend testing, and exposure to both manual and automated approaches.
• Experience in a fast-paced tech environment. Fintech, crypto, or payments experience is an advantage.

• Hands-on experience with at least one automation framework such as WebdriverIO, Playwright, Appium, or Cypress, and comfortable writing test code in JavaScript, Python, or Ruby.
• Working knowledge of back-end technologies (e.g., PHP, MySQL) and front-end technologies (e.g., HTML, CSS, JavaScript).
• Ability to write basic SQL to verify data-level behaviour and confirm expected against actual state.
• Comfort with API-level testing tools and with reading application logs during investigation.
• Familiarity with cloud infrastructure and CI tooling (e.g., AWS, Bitbucket Pipelines) is a plus.
• Experience using Claude or another LLM as part of your testing work, for example investigating defects, drafting test cases, or working through documentation, together with the judgment to verify what the model produces before relying on it.

• Ability to design test coverage from requirements without being handed a case list, including negative and boundary cases.
• Debugging instincts strong enough to reproduce an issue reliably and narrow down where it originates before handing it off.
• Attention to detail and consistency in execution, so that results can be trusted without a second run.

• Strong analytical mindset and excellent problem-solving skills.
• Ability to communicate clearly with both technical and non-technical stakeholders, and to raise concerns about quality directly.
• Excellent organizational skills, with the ability to manage several features in flight in a fast-moving environment.
• A collaborative, team-oriented approach, with a willingness to both learn from and support teammates.