QA Engineer
Zero Hash provides B2B infrastructure enabling any platform to integrate digital assets through APIs for buying, selling, custody, and payment services.
Maintainer signals as of 8/29/2026
Funding history
About zerohash
Zero Hash helps businesses add cryptocurrency services by providing API infrastructure that handles regulatory and technical complexity. With it, companies can offer trading, custody, payment processing, and rewards programs without building infrastructure from scratch. Zero Hash serves neo-banks, fintech platforms, and investment services seeking to integrate crypto capabilities.
Skills
About the Role
You will plan and execute functional, exploratory, regression, and user acceptance testing across API- and SDK-based products. You will create test scenarios, investigate defects, work with development and product stakeholders, test across environments, support release readiness, and contribute to ad hoc automation.
Requirements
- 5+ years of QA or test engineering experience
- Experience in fintech, payments, or another regulated API-driven environment is preferred
- Knowledge of QA processes across test planning, data setup, execution, defect management, and release sign-off
- Experience testing REST and JSON APIs with tools such as Postman or cURL
- Experience writing BDD-style scenarios with Gherkin, Cucumber, or similar tools
- Experience maintaining automated tests with Playwright or Selenium
- Proficiency in JavaScript, TypeScript, Python, or another test-automation language
- Working knowledge of SQL and Git-based workflows
- Experience with Jira and Confluence or equivalent tools
- Experience with TestRail, Zephyr, or a similar test-management tool
- Experience testing ledgers, settlement, reconciliation, or payments is preferred
- Exposure to CI/CD pipelines is preferred
- Experience in an Agile or Scrum environment is preferred
Responsibilities
- Design, document, and execute functional and exploratory test cases
- Perform automation testing for critical-flow gaps and automation technical debt
- Translate acceptance criteria into test scenarios
- Identify coverage gaps and edge cases
- Own regression testing before releases
- Run user acceptance testing
- Log, triage, and track defects through resolution
- Coordinate deeper automation coverage with developers
- Test across development, certification, and production environments
- Participate in release-readiness reviews