QA Automation Engineer

We promise clients weekly releases. That only survives contact with reality because the tests, the pipeline and the observability are in place. You'd be the person who makes that true instead of aspirational.

This is an engineering role, not a clicking-through-scripts role. You write code, you sit in the product team, and you decide what deserves automating and what's a waste of everyone's Friday.

Two engagements at a time, so you see how different teams solve the same problem and can carry the better answer across.

Agents cut both ways for quality. They'll generate tests in seconds, and someone has to make sure those tests are worth having. That's you.

• Cover the paths that matter. End-to-end suites in Playwright or similar on the journeys that would embarrass us if they broke.
• Push tests down the pyramid. Work with engineers so unit and integration coverage lands where it belongs, instead of everything piling into slow browser tests.
• Hunt flakes. A suite nobody trusts is worse than no suite. Keep CI fast, stable and readable when it fails.
• Own the release checklist. Including accessibility and cross-browser checks, automating the parts that repeat.
• Close the gaps. Investigate what reached production, then make sure that class of bug can't again.

• Three Years in Test Automation: for web products, writing real code in the same repo as the engineers.
• Suites That Run in CI: on every pull request, in parallel, with traces and screenshots when they fail.
• API and Contract Testing: REST clients, Postman or Pact, because not every check belongs in a browser.
• Test Data Discipline: fixtures, factories and seeded databases rather than one shared account everyone keeps breaking.
• Cross-Browser and Device: emulators or a device farm, and Safari, which will find your bug for you.
• Load Testing Basics: k6, Artillery or similar, for when the question is how many, not whether.
• Accessibility in the Pipeline: axe or equivalent, so the audit finds nothing the suite hadn't already caught.
• Strong JavaScript or TypeScript: you're a developer who specializes in quality, not a tester who scripts a bit.
• Playwright or Cypress Depth: including the unglamorous work of keeping a suite stable for a year.
• Flake Hunter: you know exactly what makes a suite trusted or ignored, and you optimize for trusted.
• API-First When Faster: you go around the interface when that's the shorter, steadier path.
• Precise Bug Reporter: your write-up leaves no follow-up questions.
• Fluent English, Written and Spoken: most of our work happens in a written thread or on a call, and both have to be clear. Arabic is a genuine advantage across the region.
• AI-Assisted Testing: you generate coverage with agents, then throw out the tests that assert nothing.

• Skeptical: It works on my machine is where your interest begins, not ends.
• Systematic: you reproduce before you theorize.
• Diplomatic: you deliver bad news about someone's feature without starting a war.

• Performance or load testing.
• Accessibility testing beyond what the automated checks catch.
• Mobile automation on real devices.

• Remote across MENA. Work from wherever you are in the region, with hours built around your team's overlap rather than someone's attendance spreadsheet.
• Work that ships. Products go live in weeks, not quarters. When someone asks what you have been building, you can open it on your phone and show them.
• Small teams, no ticket queue. Four to eight people carry a product from the first client call to handover. Nobody hands you a spec and disappears.
• Kit and tools you choose. A budget for your setup, and for the editor, licenses and services that make you fast. No three-week procurement saga.
• A learning budget with time attached. Money for the course or the conference, plus room in the week to use it. The second half is the part most places skip.
• Client contact from day one. You sit in the room where the decisions get made. Plenty of engineers wait a decade for that seat.
• Time off people take, and no timesheets. We measure engagements, not humans in fifteen-minute increments. Book the holiday, go, come back.