We're Umber - a small dev team building back-office and payment infrastructure for large-scale operation. One of our core products is a payment aggregator handling real transaction volume across multiple regions and payment providers. We're looking for a QA engineer who genuinely enjoys digging into financial logic, not just checking UI.
About the role
One QA engineer is already on the product. We're expanding the function — and looking for someone who'll take ownership of their own coverage area.
The work is backend-heavy: transaction flows, provider integrations, reconciliation logic, webhook handling, edge cases in financial data. You'll need to understand what's happening at the API and database level, not just what's visible on the screen.
We don't need someone to build automation frameworks. But if you use AI tools to move faster: generating test cases, parsing logs, breaking down requirements - that's a real plus.
The product
A payment aggregator integrated with multiple payment providers across regions. Core testing areas:
Transaction flows end-to-end: initiation, processing, status updates, failures
Provider API integrations and webhook behavior
Financial data consistency across systems
Edge cases in payment logic: retries, timeouts, partial failures, reconciliation
Role-based access and operational back-office workflows
Stack: Node.js, NestJS, TypeScript, PostgreSQL, Docker, AWS, CI/CD pipelines, external provider APIs.
What we're looking for
2.5+ years in manual QA on web products
Real API testing experience — Postman, reading Swagger, understanding what the backend is doing
SQL / database validation: you write queries to check data, not just look at the UI
Experience testing payment flows, financial transactions, or integration-heavy systems
Comfortable reading logs (Kibana, Sentry or similar) to understand what's happening
Ownership mindset: you decide what needs coverage, you follow things through
English sufficient for documentation and async communication
Nice to have
Experience with high-load or multi-provider payment systems
Familiarity with CI/CD — you don't need to set it up, but knowing how deploys affect testing helps
Using AI tools in QA work (test case generation, log analysis, requirement parsing) — with your own judgment on when to trust the output
Hiring process
Intro call (40–60 min)
Technical interview with CTO (60–90 min): experience-based discussion + short practical task
Offer
Terms
Full-time · Contract-based (FOP) · 3-month probation · 24 paid days off + New Year & Christmas · Fully remote · No time trackers · Annual performance review
