Join the cutting edge of quality

Are you a test automation expert? We are transforming software testing for the world’s biggest brands.

Apply to be a Quality Engineer

Responsibilities

Quality Engineers have horizontal responsibilities that run across four major pillars.

People

Lead by example and share automation best practices with teams across the world.

Technology

Fuel innovation by advocating for new approaches and providing feedback to improve platform capabilities.

Process

Develop sustainable, effective, and efficient quality processes and standards.

Governance

Foster an accountable, transparent, and regulated culture that adheres to organizational values and objectives.

What you’ll bring

To deliver the best results for our clients, we are looking for Quality Engineers with the following experience:

Coding ability (in Java, Python, Node, etc.)
Creating test scripts
Experience with Appium (iOS and/or Android testing)
Experience with Selenium (web testing)
Working knowledge of at least one test automation tool (BrowserStack, BitBar, Sauce Labs, Eggplant, Applitools, etc.)

What you’ll do

Quality Engineers focus on the following strategic and tactical initiatives:

Write and maintain scripts
Validate and analyze results for automation
Define what needs to be re-tested with automation or manual testers
Assist in developing testing processes that can scale
Provide feedback to Testlio on how to improve our platform

Apply now

Meet our freelancers

QA for Beginners: Unit Testing Vs Regression Testing

As the SaaS and other IT-related markets grow and become more ingrained in the daily operations of businesses and enterprises and the lives of users, the notion of quality becomes even more critical.

How to Write Test Cases

25% to 35% of a software testing team’s time is spent on writing and maintaining test cases. Yet, poorly written or incomplete test cases can lead to missed defects, inefficient testing, and costly rework.

Understanding Risk-Based Testing in Software Testing

Suppose you’re working on a complex software project with a tight deadline. Your team has limited time and resources, but the application is growing in complexity with each sprint. Testing every feature thoroughly is impossible, so how do you decide what to test first?

Ready to be a Testlio QE?