QA Engineer

Paybis

format:Remotecompany:Product

postmanjirasqlchrome devtools

seleniumcypressmobile app testing

test task:yes

englishB2

domainFintech

> full description

About Paybis

Paybis is a global crypto/fiat platform operating since 2014, serving customers across 180+ countries. We build and scale complex fintech products focused on payments, crypto transactions, and seamless customer experience.

We are looking for a Junior QA Engineer who wants to grow inside a quality-driven team, work on a real product, and understand that behind every test case are real users and real money.

This is a product-focused role for someone who cares about ownership, not just task completion.

What You’ll Do

Run functional and regression testing of client flows via UI and API
Write and maintain test cases, checklists, and bug reports
Use Chrome DevTools and Postman to analyse application behaviour and diagnose issues
Work closely with developers and QA engineers throughout the SDLC
Perform cross-browser and cross-device testing
Identify and document usability issues in the interface
Optionally participate in UI automation if you have the interest and baseline knowledge

What We Expect

Must-Have:

Testing theory: types, levels, design techniques (BVA, EP), bug lifecycle
Writing test cases and checklists independently, without a template
REST API testing via Postman: requests, status codes, headers, response body
Chrome DevTools — active use of Network, Console, Elements tabs
Structured bug reports in Jira with correct severity and priority
Basic SQL for data validation
Git basics: branch, commit, pull request
Understanding of client-server architecture and REST principles
Agile / Scrum: real sprint experience
English B2+ — documentation and day-to-day communication are in English
Strong analytical thinking and ownership mindset

Nice-to-Have:

Experience in fintech, e-commerce, or crypto products
Familiarity with automation basics (Selenium, Cypress)
Mobile testing experience (iOS / Android)
Understanding of payment flows at user level (KYC, 3DS)
ISTQB Foundation or equivalent knowledge

Soft Skills:

Attention to detail — in a payment domain, one missed bug can cost users real money
Ownership mindset — you don’t wait to be asked: you spot risks yourself and raise them proactively
Clear communication — you explain bugs clearly to developers, ask the right questions about requirements, and aren’t afraid to say “something feels off here”
Analytical thinking — you think systemically: what breaks if this step fails? Which scenarios aren’t covered yet?
Eagerness to learn — the domain is complex and the stack evolves; you seek knowledge independently rather than waiting for everything to be explained
Adaptability — release priorities shift; you refocus quickly without losing quality
Collaborative by nature — QA is a developer’s partner, not a gatekeeper; you know how to work with people, not against them

What Success Looks Like

First 30 Days:

Onboarding complete. You understand the product, team, and processes. You independently execute assigned test cases and actively participate in sprints.

First 90 Days:

You maintain test cases and bug reports with minimal supervision. You proactively report bugs, ask clarifying questions about requirements, and suggest improvements to checklists.

First 6 Months:

You fully own your assigned testing area. You consistently contribute to release quality and independently identify edge cases and risks.