Manual QA Engineer

About the Role

Ruby Labs is seeking a QA Engineer (manual-first, API-heavy) to ensure the stability of their payments platform amidst frequent releases and urgent hotfixes. Operating in a Kanban/continuous delivery setup, you will focus on clarifying scope, building lightweight test coverage, and shipping fast without compromising critical payment routes. Your primary focus will be risk-based testing of payment flows, end-to-end API validation, and maintaining pragmatic regression checklists.

Key Responsibilities

• Manual testing: Validate new features, fixes, and hotfixes across Web UI + APIs.
• Risk-based testing: Define test scope based on financial/customer impact and identify residual risks.
• API / E2E validation: Test REST APIs, async flows, and webhooks using Postman/Newman (or equivalent).
• Data validation: Verify state transitions and side effects in PostgreSQL; understand idempotency and retries.
• Regression ownership: Maintain and continuously improve smoke + regression suites for critical payment routes.
• Incident-to-tests: Convert production incidents into new regression cases or monitoring checks.
• Collaboration: Work closely with engineers/PMs to clarify requirements, reproduce issues, and verify fixes.
• Release reporting: Provide concise QA notes per release (scope, result, risks, follow-ups).

Qualifications

• 3+ years in QA with strong manual testing fundamentals.
• Strong API testing skills (Postman/Newman, curl, Swagger/OpenAPI).
• Practical understanding of: auth vs capture, refunds, webhooks, idempotency, retries.
• Basic SQL (PostgreSQL): ability to validate records, joins, state transitions.
• Experience with logs/monitoring (Grafana, Kibana/ELK, Sentry or similar).
• Comfortable in Kanban / no-sprints / fast-changing requirements.
• Good English (written + spoken) for remote async work.

Nice to have

• Experience with PSPs (Stripe, Adyen, PayPal, Braintree, Worldpay, etc.).
• Experience with 3DS flows (frictionless vs challenge) and SCA constraints.
• Familiarity with test automation frameworks (pytest, Playwright) and CI (ability to read/maintain existing checks is a plus).
• Understanding of network tokenization (DPAN / network tokens).

Location

• The role operates within the CET (Central European Time) zone. Applicants should be located within approximately ± 4 hours of CET to ensure optimal collaboration.