QA Engineer

Remote · Full Time · Engineering

About the role

For a small, fast-moving team building a multi-tenant CRM/e-commerce system (Django/Postgres backend; React admin; Angular storefront; a couple of Node microservices). Development velocity is currently blocked by manual QA—especially in high-risk financial areas (refunds, credits, settlements). We’re hiring a fully-remote Freelance QA Automation Engineer to design and own test automation, wire it into CI, and unblock safe, confident releases. Strong overlap with Israel time is important; onboarding and domain knowledge are primarily in Hebrew.

Capacity: 60h / Month

What you'll do

  • Define and own the QA strategy: test levels (API/e2e), environments, data, coverage targets, reporting.
  • Stand up automation from scratch (framework selection, repo scaffolding, conventions/utilities).
  • Prioritize and automate money-critical flows first: refunds/credits, payment provider integrations, ledgers, orders/reservations, webhooks, retries/idempotency.
  • Integrate suites into CI/CD: PR gates, deploy-time smoke tests, nightly runs; provide clear, actionable reports.
  • Build reliable test data/fixtures (sandbox accounts, test cards, seeded datasets, reset tools).
  • Translate existing manual flows into maintainable automated cases; write concise test plans/checklists.
  • Track and reduce flakes; define release criteria; triage failures to drive down MTTR.
  • Collaborate with engineering/product; coach teammates to contribute tests and follow QA best practices.

What we're looking for

Must-haves

  • 4+ years hands-on QA automation, including building frameworks from zero.
  • Strong JavaScript/TypeScript with Playwright or Cypress for UI; plus Python/pytest or Postman/Newman for API testing.
  • CI experience (GitHub/GitLab/Bitbucket pipelines), artifacts & reporting dashboards.
  • Solid grasp of web apps (React/Angular), REST APIs, and basic SQL (Postgres).
  • Proven work testing payment flows (refunds, credits, settlements, webhooks) and other high-risk financial features.
  • Comfortable owning a roadmap, making pragmatic trade-offs, and communicating clearly with stakeholders.
  • Hebrew fluency (onboarding and much of the domain context are in Hebrew).

Nice-to-haves

  • Familiarity reading Django code; factories/fixtures; Django admin.
  • Experience with Israeli acquirers or Stripe-like gateways.
  • Multi-tenant systems, roles/permissions, complex back-office workflows.
  • Basic performance/security testing (e.g., k6/Locust).

Logistics

  • Contract, fully remote; strong overlap with Asia/Jerusalem hours.
  • Initial engagement ~3–6 months, with potential extension.

Apply for QA Engineer

Upload your CV and links. A person reviews every application and we'll get back to you either way.

* Required

Frequently Asked Questions

01

What are the working hours and expectations for this job?

Since this is a remote role, the working hours are flexible. The work model in some cases could be hourly-based, and in other cases project-based.
02

How does the hiring process work?

1. Initial Screening of your application and CV 2. An introductory interview to assess fundamental qualifications and key criteria. 3. Technical interview/s covering DevOps, Platform Engineering, and SRE principles, as well as proficiency and problem-solving skills. 4. CEO interview assessing both advanced technical skills and personal character.
03

What types of projects will I be working on?

We work on a wide variety of projects across multiple industries and company sizes, each involving different technologies. Our clients are located in different countries worldwide, providing opportunities to work on international projects. Projects are matched based on the candidate's expertise, ensuring the best fit for both the project requirements and your skillset.
04

How is the payment structured?

We offer hourly contracts and you get paid for the hours worked every month.
05

Is there potential for long-term collaboration?

Absolutely! Most of our engineers stay with us long-term. Even after a project concludes, we usually have new opportunities available, allowing us to continue our collaboration.