Umber

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

1. Intro call (40–60 min)
2. Technical interview with CTO (60–90 min): experience-based discussion + short practical task
3. 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

We're Umber — a small development team working with fintech systems and complex business platforms. We're expanding our QA capacity and looking for a Manual QA Engineer to join us across two web products in active development.

About the role

Until recently, quality was covered by engineers. Over the past year we've been building out a dedicated QA function, and now we're growing it. You'll join an existing QA on one of two products — or work across both.

The role is manual QA at its core: business logic, API behavior, data consistency, edge cases, regression before releases. We're not looking for someone to write automation frameworks, but we do care if you use AI tools to work smarter — generating test cases, parsing logs, breaking down requirements faster. That kind of practical boost is a plus.

The products

One is a payment aggregator handling real transaction volume across multiple regions and payment providers. The work here is about correctness: transaction flows, integration behavior, data consistency across systems, edge cases in financial logic. 

The second is an internal workforce management platform — scheduling, time tracking, payouts, role-based access, multi-location operations and ATS+job board functions. It's at an active MVP stage with lots of moving parts and frequent changes, so flexibility matters as much as depth.

Both run on the same stack: 

Node.js, NestJS, TypeScript, PostgreSQL, TypeORM, microservices, Docker, AWS, CI/CD pipelines, provider APIs, external provider integrations. Devs use Jest for unit tests.

What you'll be doing

• Testing business logic, API integrations, and data flows — not just UI
• Writing and maintaining test cases, checklists, regression coverage
• Running smoke and regression checks before releases
• Logging and tracking bugs in ClickUp through to resolution

• Working with engineers and PM to clarify requirements and keep QA docs up to date

   

What we're looking for

• 2-4 years in manual QA on web products
• Real experience with API testing — Postman, reading Swagger, understanding what the backend is actually doing
• SQL / database validation: you know how to write queries and check data, not just look at the UI
• Experience with business logic that's genuinely complex — financial systems, SaaS platforms, integrations
• Comfortable reading logs (Kibana, Sentry or similar) to understand what's happening
• Ownership mindset: you decide what to cover, you follow things through, you don't wait to be told
• English sufficient for documentation and async team communication

Nice to have

• Experience with fintech, payments, or high-load systems
• Familiarity with CI/CD — you don't need to set it up, but knowing how deploys affect testing helps

• Using AI tools in your QA work (generating test cases, log analysis, requirement parsing) — with your own judgment on when to trust the output

   

Hiring process

1. Intro call (40-60 min)
2. Technical interview with CTO (60–90 min): experience-based discussion + short practical task

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