🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Job Type Full-time Description What We Offer You Ownership of quality for a real revenue product used by carriers and brokers. A team that treats automation and AI-assisted testing as the standard, not an experiment, and gives you room to shape how AI is used in QA. Growth into test architecture and AI-assisted testing practices. About The Role We are looking for a QA / Test Engineer to own quality for Truckloads (TL), our logistics SaaS platform for carriers and brokers. You will design and automate tests across mobile and API layers, and, just as importantly, help us push testing into an AI-assisted model, where AI generates test cases and scripts from PRDs, Figma, and our knowledge base, and the engineer focuses on judgment, calibration, and coverage decisions. This is a hands-on role for someone who is excited about automation-first QA and about using AI as a serious part of the testing workflow, not just a novelty Responsibilities Design test cases from business rules and requirements, covering happy paths, edge cases, and error paths, not just the obvious scenarios. Build and maintain Truckloads automation suites: Mobile UI: Maestro (Android + iOS) AND API: Python / pytest Use AI to accelerate testing: generate and refine test cases and automation scripts from PRDs, Figma designs, and the knowledge base; review and calibrate AI output for correctness and coverage. Keep the knowledge base structured and “AI-consumable” (clear naming, machine-readable structure) so that AI-generated tests stay reliable. Own the bug lifecycle: reproduce, triage, file well-documented tickets, and verify fixes through regression scripts. Run and analyze test results, classify failures (environment / script / product bug), and drive them to resolution, with no unexplained skips or failures. Requirements Must-have 3+ years of experience in QA / test automation. Solid programming ability in Python. Hands-on experience with test automation frameworks (mobile UI and/or API). Experience with API testing and understanding of REST/HTTP . Comfortable using AI / LLM tools (e.g. Claude, Copilot) in daily engineering work, and able to critically review AI-generated output rather than trust it blindly. Familiarity with Git-based workflows and CI/CD pipelines. Strong analytical mindset, able to root-cause failures from logs and evidence, not guess. Working proficiency in English (written and spoken) for cross-region collaboration. Nice-to-Have Experience with Maestro (mobile automation). Mobile app testing experience (Android / iOS). Experience designing prompts or workflows for AI-assisted test generation. Background in SaaS, logistics, or transportation products.
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.