About the role

We are building a multi-sided marketplace platform for the GCC market a customer web portal, vendor and sales mobile apps, an admin console, and the backend services behind them. Arabic-first, mobile-heavy, and growing fast.

This is our first dedicated QA hire. There is no existing automation framework, no test data infrastructure, and no device lab. You will build all of it, then own it.

You will work directly with the Principal Architect and a small, senior development team. You will be the only QA voice in the room, which means you set the standard and you are expected to push back when something shouldn't be built, shipped, or automated.

If you are looking to slot into an existing rig and write test cases against a spec, this is not that role. If you want to design a test strategy from zero and see it hold up under real delivery pressure, read on.

What you'll own

- Test strategy. Decide what gets automated and what doesn't. Map risk across web, API, and mobile, and defend those choices.
- Web automation. Playwright suites covering the customer portal, admin console, and vendor microsites including Arabic RTL layout verification.
- API automation. Contract and integration tests against our .NET REST APIs, with OpenAPI schema validation.
- Mobile automation. Appium suites for our React Native (Expo) vendor and sales-agent apps, on Android and iOS. You will own the mobile automation strategy and framework, working with engineering to establish the required CI/device infrastructure.
- CI integration. Tiered suites wired into GitHub Actions: fast smoke checks developers run before raising a PR, targeted regression on PRs, full runs nightly.
- Reporting. A per-run quality dashboard the team actually looks at — pass rates by area, flakiness trends, failures traceable back to Jira tickets.
- Test data. Deterministic, containerised environments so nobody debugs a failure caused by someone else's data.
- Exploratory and release testing.



Roughly 30% of the role. Automation doesn't replace looking at the product.

What we're looking for

Required

- 5+ years in QA, with 3+ writing production automation in TypeScript or JavaScript
- Deep hands-on Playwright or Cypress — you've carried a suite through at least one major release cycle, not just written tests against a stable app
- Appium on real devices, including local setup. Appium server, UiAutomator2 and XCUITest drivers, iOS provisioning and WebDriverAgent. Experience limited to a hosted device cloud won't be enough here — you'll be building the rig.
- REST API testing: authentication flows, schema validation, seeded state
- Docker, and the ability to run tests without depending on a shared setting
- CI pipeline experience — GitHub Actions or equivalent, including sharding and artifacts
- Clear written English; much of our work is async
- Comfortable querying PostgreSQL and diagnosing data/state-related test failures.

What we'll actually probe in the interview

- A flaky suite you diagnosed and fixed. What was actually wrong — not what you retried.
- Something you decided not to automate, and the reasoning.
- A framework you built or substantially reshaped, and what you'd do differently now.

Nice to have — we'll teach these

- Performance testing (k6, JMeter, Gatling)
- Security scanning basics (OWASP ZAP, dependency scanning)
- Allure or similar test reporting
- Testcontainers
- React Native or Expo familiarity
- RTL or multi-locale testing
- Marketplace, directory, or e-commerce domain experience

Not required

- Arabic language
- Any specific device-cloud vendor
- ISTQB or similar certification
- Experience with test management tools — we keep tests in code, not in a separate repository

Our stack TypeScript • Playwright • Appium • k6 • Allure • Testcontainers • GitHub Actions (self-hosted runners) • Turborepo • Docker

Product side: .NET / PostgreSQL / Redis / RabbitMQ backend, Next.js web, React Native (Expo) mobile.

📌 Senior Quality Assurance Automation Engineer (Kochi)
🏢 Secdaddy IT Solutions
📍 Kochi