QA Engineer at zerohash
Chicago, IL
—
Aug 17, 2026
Chicago, IL
Sep 25, 2026
What this job asks for AI summary
A QA Engineer role at a crypto and stablecoin infrastructure company, responsible for owning test planning, functional and exploratory testing, and UAT across API- and SDK-based product flows. The position involves collaborating with engineers and SDETs to define test scenarios, manage defects, and drive release readiness, with occasional automation work to address coverage gaps. Well-suited to an experienced QA professional with a background in fintech or payments.
Senior level · 5+ years
Quick apply — this platform usually takes a CV and a few fields.
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $106,594 (middle half $82,076–$136,109).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Aug 20, 2026. It is a model, not a headcount.
Why we read it this way (9)
Location is not specified in the posting. The Colorado wage-disclosure note suggests US-based candidates, but no city, metro, or explicit remote policy is stated — CBSA left blank and remote set to false as a conservative default.
The posting lists Postman and cURL as examples of API testing tools within the requirements section; cURL is captured as an alternative to Postman since both serve the same function here.
JavaScript/TypeScript and Python are presented as interchangeable scripting language options; JavaScript is used as the primary name with TypeScript and Python as alternatives.
Playwright and Selenium are listed as examples of automation frameworks within the requirements section; Selenium is captured as an alternative.
Gherkin and Cucumber are listed as examples of BDD tooling within the requirements section; Cucumber is captured as an alternative.
TestRail and Zephyr are listed as examples of test management/UAT tools within the requirements section; Zephyr is captured as an alternative.
Jira and Confluence are listed together with 'or equivalent tools' — the equivalence qualifier means the specific tools are interchangeable, but the capability (test planning/tracking/documentation tooling) is a hard gate.
CI/CD pipeline exposure and Agile/Scrum experience appear under the 'Preferred' section and are marked accordingly.
No compensation figures are published in the posting; Colorado candidates are directed to email for compensation details.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.