Quality Assurance Automation Engineer (Voice AI)

Location: Remote (Pakistan) · Type: Full-time · Level: 2–4 years

About the role

Entropik Labs is hiring a QA automation engineer to own quality for our AI powered products across mobile, web, APIs and backend services.

The job is broader than writing test cases. You'll design the test strategy, automate the workflows worth automating, validate every release before it ships, and then keep watching once it's live. When something breaks in production, you're the first person to look at it.

These systems don't fail cleanly. A release doesn't crash, it just starts returning stale data, or a workflow completes with the wrong value written to the database. So we're looking for someone detail oriented and proactive who is comfortable across the whole lifecycle, from validating requirements before code is written to triaging an alert at an inconvenient hour.

What you'll do

Quality assurance and testing

• Create, maintain and run test plans, test cases and regression suites.
• Test mobile apps, APIs, backend services and web applications, manually and through automation.
• Validate new features, bug fixes and releases before they go out.
• Keep test coverage documented, and make sure the critical user journeys get verified regularly.
• Find, document and track defects through to resolution.

Automation

• Build and maintain automated suites for APIs, backend services and full workflows.
• Wire those suites into CI/CD so they run on every change.
• Cut manual testing effort where automation genuinely pays for itself.
• Watch test runs and investigate failures rather than rerunning until they pass.

Mobile, web and API testing

• Test Android and iOS builds across multiple devices and environments.
• Validate APIs, integrations and backend behaviour directly.
• Run functional, regression, smoke and exploratory passes on web applications.
• Verify business workflows and data consistency across systems.

Operations and support

• Validate releases, and verify them again once they're deployed.
• Monitor production systems, dashboards, logs and alerts.
• Handle L1 and L2 support: triage, investigation, reproduction and escalation.
• Work with engineering to find root causes and track incidents to closure.
• Run periodic health checks and synthetic tests.

Documentation and reporting

• Maintain test execution records, evidence, defect reports and release sign off documentation.
• Produce weekly QA and production quality reports.
• Track quality metrics, open defects, release readiness and testing progress.
• Give stakeholders clear status updates and a recommendation, not just a dashboard.

What we need from you

• Two or more years testing software in a professional release cycle, across both manual and automated work.
• A solid grasp of QA methodology and the testing lifecycle, and a view on what's worth automating and what isn't.
• Experience testing REST APIs with Postman, Swagger, Insomnia or similar.
• Working experience with at least one automation framework: Playwright, Selenium, Cypress, Appium, Pytest, Robot Framework or Katalon.
• Experience with Jira, ClickUp, Azure DevOps or a similar tracker, used properly rather than as a to do list.
• Working knowledge of SQL, enough to verify what actually landed in the database.
• Comfort with Linux, Docker and the command line, enough to stand up an environment yourself.
• Production monitoring and observability: metrics, dashboards, log search and alerting, owned rather than observed, including synthetic checks and triage when something breaks.
• Strong written communication, and the confidence to hold a release when the evidence says so.

Nice to have

• Testing AI, LLM, voice AI or conversational AI applications
• Load and performance testing with JMeter, k6 or Locust
• Mobile automation with Appium
• Observability tooling such as Grafana, Prometheus, ELK, Datadog or Sentry
• Telephony platforms, speech evaluation or voice applications
• Startup environments
• On call or support rotations

What success looks like

In your first three months, we'd expect you to have a reliable test suite running and maintained, test execution tracking and reporting in place that people actually read, and QA sign off on releases owned end to end. Production defects should be measurably down because release validation caught them first, and you should be carrying your share of monitoring and L1/L2 triage.