Automation Test Engineer
Turing • Remote, Bangladesh, Egypt, India, Kenya, Mexico, Nigeria, Pakistan, Turkey, Ghana
Education
Bachelor's
Type
Hourly
Listed
121d ago
Apply opens Turing in a new tab.
Apply Now → ⚡ Boost your chances - Optimize your resume with Rezi.aiWhat We Know About This Role
- Interview
- Required i As stated in the listing: “Duration of contract : 2 months; [expected start date is next week]”
- Weekly hours
- 40 hrs/week
- Timezone overlap
- Partial overlap with US Pacific time required
- Contract length
- 8 weeks
About this role
From the Turing listing
About Turing
Turing is one of the world’s fastest-growing AI companies accelerating the advancement and deployment of powerful AI systems. Turing helps customers in two ways: Working with the world’s leading AI labs to advance frontier model capabilities in thinking, reasoning, coding, agentic behavior, multimodality, multilinguality, STEM and frontier knowledge; and leveraging that work to build real-world AI systems that solve mission-critical priorities for companies.About the RoleTesters verify that each task's automated test suite works correctly. You run the reference solution inside a Docker container and confirm it scores 1.0 against the verifier. If it doesn't pass, you diagnose the failure, determine whether the issue lies in the solution, the verifier, or the environment, and escalate accordingly. Testers are the last checkpoint before a task is marked ready to ship.What You Will DoExecute reference solutions inside Docker containers and capture the output Run the pytest-based test suite against the solution outputDiagnose failures: distinguish between a broken solution, a misconfigured verifier, an environment issue, or a task design flawReport failures clearly to the Pod Lead or Annotator with enough detail to reproduce the issue Track test results in the shared tracker and flag tasks that are consistently failing or require environment changesRequired:Bachelor's degree in Computer Science, Engineering, or a related technical field 5+ years in software QA, DevOps, backend development, or automated testing Comfortable working in a Linux command-line environment Hands-on experience with Docker (building images, running containers, reading logs)Ability to read and understand Python code and basic pytest output Systematic debugging mindset: Ability to isolate whether a failure is in the code, the config, or the environment Nice to Have: Familiarity with CI/CD pipelines and containerised test environments Experience with domain-specific libraries (e.g., pandas, openpyxl, pdfplumber, librosa, astropy) depending on batch assignment Understanding of how LLM evaluation pipelines work
Offer Details
- Commitments Required: 40 hours per week with overlap 4 hours with PST
- Engagement type : Contractor assignment(no medical/paid leave)
- Duration of contract : 2 months; [expected start date is next week]
- Location : India, Pakistan, Nigeria, Kenya, Egypt, Ghana, Bangladesh, Turkey, Mexico
Evaluation Process (approximately 60 mins)
- 1 round of interviews (Round 1 - 60 min technical )
Requirements
- QA
- Automation Testing
- DevOps
- Must be eligible to work in one of: Remote, Bangladesh
How long hiring takes
Across the AI training platforms we refer candidates to, the median gap between referral and hire is about 30 days. It varies by platform and role, so treat it as a rough guide for this one.
Interview Prep
Sample questions for a Test Automation Engineer role, written in-house to help you prepare.
How do you decide which test cases are worth automating versus better left as manual tests?
I prioritize automating tests that run frequently and have stable, well defined expected outcomes, since those give the best return on the investment of writing and maintaining the automation. Tests that change frequently or require significant human judgment tend to be more trouble to automate than they're worth.
What's your approach to writing automated tests that don't become flaky or unreliable over time?
I avoid relying on fixed wait times and instead wait for specific conditions to be true before proceeding, since timing based waits are one of the most common sources of flakiness. I also isolate tests from each other so one test's failure or side effect doesn't cascade into unrelated test failures.
How do you evaluate whether a new testing tool or framework is worth adopting over what your team is already using?
I weigh the actual problem the current tool has against the migration cost and learning curve of switching, rather than adopting a new tool just because it's newer or has more features on paper. A tool switch is only worth it if it solves a real, specific limitation the team is running into.
What's your process for debugging a test failure to determine whether it's a real bug or a problem with the test itself?
I reproduce the failure manually against the actual application to see if the behavior the test flagged is genuinely wrong, rather than assuming the test is correct by default. If the application behaves as the test expects when done manually, the issue is usually in the test's setup or assumptions rather than the product.
This listing calls for this tool directly. Prep for the technical screen:
What to Expect
Looking at Turing STEM listings we've tracked, contracts in this domain typically run about 8.5 weeks. Actual length varies by project, but this gives you a realistic baseline going in. This listing's 8-week contract is shorter than the typical 8.5-week Turing STEM engagement.
Based on 11 extracted Turing STEM listings.
Why this role
This Automation Test Engineer role covers building automated test suites that validate AI-generated code. The suites need to catch regressions and edge cases a one-time manual review would miss on a fast-moving codebase.
Talent pool
We're light on STEM candidates
We've matched 65 people with a STEM background against 726 STEM listings we've tracked, so most go out without one. Set up a profile and we'll consider you for a role like this one.
Set up your profileSkills and categories
Explore other opportunities in related specializations:
Related jobs
Browse All Jobs from Turing
Discover more opportunities on Turing that match your skills and interests.
View All Turing Jobs →Verified Reviews
Community Reviews
Share your experience with Turing
Help other candidates make better decisions by leaving a review.
Sign in to leave a reviewLeave your review
Common questions
Do I need to be a software engineer to work for Turing?
No, not anymore. Turing built its name matching senior engineers with Silicon Valley companies, but it has since expanded into AGI infrastructure work and now hires non-engineering domain experts, technical writers, and researchers for post-training data annotation and RLHF. A strong analytical background and excellent English matter more than coding ability.
How does Turing's talent matching work?
Turing calls it the Intelligent Talent Cloud. You build a profile and go through vetting (automated tests, an AI-powered interview, practical skill assessments), and once vetted, Turing's algorithm surfaces your profile directly to partner companies like Fortune 500s and top AI labs. You don't browse listings or bid on work; matches come to you.
What does asynchronous AI training work mean in practice?
No set hours, no check-ins, no meetings. You log in when you want, pick up an available task, complete it, and submit; nobody is waiting on you in real time. That's different from remote employment, where you're expected online during business hours. The tradeoff: you're competing with others for available tasks, so an empty queue means there's simply nothing to do until more work is released.
What does STEM work look like for an Automation Test Engineer?
Tasks here are scoped to STEM, not generic labeling. As an Automation Test Engineer, expect to draw on real domain judgment (evaluating outputs, correcting errors, or providing expert reasoning specific to STEM) rather than following a one-size-fits-all rubric. If you don't have hands-on STEM background, this is likely not the right listing to start with.
What specific skills does this listing call for?
QA, Automation Testing, DevOps, and Coding are named directly in the listing. If you don't have hands-on experience with these, expect the screening process to test for them directly rather than accepting adjacent experience as a substitute.
How many hours per week does this role require?
Based on the listing, this role is scoped at about 40 hours per week, over roughly a 8-week contract. Treat this as a real commitment expectation, not a loose estimate.
How much does this specific role pay?
The listing doesn't state a rate. The $12–$30/hr shown here is our estimate from the role type and location (see /pay-methodology), so treat it as a rough guide and confirm the actual rate with the platform before committing time.
What happens when I click Apply on this listing?
You'll be taken to Turing's external site to complete your application there. This listing links through a referral, but the process is identical to applying directly; the link just routes you correctly. Create an account on their site and follow their onboarding steps.
Can I apply from outside Bangladesh, Egypt, India and 6 other countries?
This specific role is open only to people based in Bangladesh, Egypt, India, Kenya, Mexico, Nigeria, Pakistan, Turkey, and Ghana. If you are somewhere else, applying is unlikely to lead to an offer even if you pass the assessment, because the restriction is usually about where the work can legally be contracted rather than your skills. Read the full description for any tax-residency or right-to-work caveats before you apply, since they can differ by country.
Is there an interview?
Yes. 1 round of interviews (Round 1 - 60 min technical )