QA Engineer
QA Engineer owning test strategy and automation for a React web front-end at a payments company: writing unit/integration/E2E suites treated as production code, building CI/CD test pipelines, and filing root-cause bug reports, plus occasional manual testing of an Android/iOS SDK. Core stack: React, JavaScript/TypeScript, Playwright/Cypress/Jest, and CI tools.
- Compensation
- Not disclosed
- Location
- UA
- Work setup
- Remote
- Seniority
- Not specified
- Employment
- Not specified
- Experience
- 3+ years
- Category
- Qa
- Posted
Skills
Must have
- 3+ years as a QA Engineer or SDET, with hands-on test automation experience
- Strong software engineering fundamentals: able to read, write, and debug real code
- Ability to read and understand React code — components, hooks, state/props flow
- Solid JavaScript/TypeScript skills
- Proficiency with a modern JS/TS test automation framework (e.g., Playwright, Cypress, Jest, React Testing Library)
- Experience with CI/CD tools (e.g., GitHub Actions, CircleCI, Jenkins) and building test infrastructure
- Able to clearly explain why something is a bug, its impact, and root cause
- Experience manually testing mobile apps on real devices/simulators (iOS and/or Android)
Nice to have
- Experience testing native or cross-platform SDKs
- Familiarity with Android (Kotlin/Java) and/or iOS (Swift) enough to read stack traces or sample integration code
- Experience setting up mobile test automation (e.g., Appium, XCUITest, Espresso)
- API/backend testing experience (e.g., Postman, REST-assured)
- Performance or accessibility testing experience
- A blog post, talk, OSS contribution, or side project related to testing/QA
Full description
The Mission
Wallee Group is a leader in advanced payment solutions, dedicated to providing robust, scalable, and secure systems across multiple domains. We enhance customer experiences through innovative payment and finance technology that empowers businesses to grow efficiently. With operations spanning several countries, we thrive on collaboration and agility, utilizing the Scrum framework to drive our international teams. At Wallee, we stay at the forefront of market trends, continuously innovating to deliver premier services to our global customers.
The Role
QA Engineer to own test strategy and automation for a React-based web front-end.
We're looking for a strong software engineer who has chosen quality engineering as a deliberate specialization — someone who finds testing, tooling, and preventing bugs at scale genuinely interesting. The role also involves occasional manual testing of a cross-platform mobile SDK (Android & iOS), with mobile test automation as a possible future direction.
Core Responsibilities
Design, write, and maintain automated test suites for the React front-end (unit, integration, and end-to-end tests) — treated as production code, not an afterthought
Read and understand React component code well enough to reason about edge cases, state transitions, and failure modes, not just click through UI flows
Build and maintain CI/CD test pipelines and test infrastructure — this is engineering work, not configuration
Define test strategy and coverage standards for the team, and advocate for testability in code review and design discussions
Investigate, document, and file clear, reproducible bug reports; go deep enough to identify root cause, not just symptoms
Contribute to test plans and acceptance criteria during feature planning — as a peer in design discussions, not downstream of them
Occasionally perform manual testing of the mobile SDK (Android & iOS)
Requirements
3+ years as a QA Engineer or SDET, with hands-on test automation experience
Strong software engineering fundamentals: able to read, write, and debug real code, not just scripts
Ability to read and understand React code — components, hooks, state/props flow — well enough to reason about what needs testing and why
Solid JavaScript/TypeScript skills
Proficiency with a modern JS/TS test automation framework (e.g., Playwright, Cypress, Jest, React Testing Library)
Experience with CI/CD tools (e.g., GitHub Actions, CircleCI, Jenkins) and building test infrastructure, not just using it
Able to clearly explain why something is a bug, its impact, and root cause — not just that it happened