> Markdown version of [/jobs/ext/1421254-qa-testing-engineer-iii](https://www.wearedevelopers.com/jobs/ext/1421254-qa-testing-engineer-iii). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # QA Testing Engineer III - **Company:** Southern Motor Carriers Association, Inc. - **Location:** Peachtree City, GA, United States - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Testing (Software), Application Programming Interfaces (APIs), Agile Methodology, Artificial Intelligence, JIRA, Automation of Tests, Code Coverage, Databases, Continuous Delivery, Continuous Integration, Design of User Interfaces, JSON, Load Testing, Scrum Methodology, Software Engineering, Software Quality Assurance (SQA), Subversion, Systems Integration, Test Execution Engine, Strategies of Testing, Extensible Markup Language (XML), Data Processing, Backend, Git, Playwright, Data Analytics, Software Version Control, Text Files, Jenkins - **Published:** July 24, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=8579e18462cc1add ## About the Role * College degree in a related area of study, equivalent experience, or certification in QA tools and techniques. * 5-7 years of software testing experience, including automated testing; 2-3 years of performance and load testing; software development experience desired. * Experience creating, maintaining, or contributing to automated tests using Playwright, Claude Code, or comparable AI-assisted coding/testing tools, with the ability to identify automation opportunities across test execution, data setup, validation, reporting, and regression coverage. * Experience testing APIs, user interfaces, integrations, backend services, and data-driven system behavior, including the ability to read, understand, and validate XML and JSON messages. * Experience using Jira or similar work-tracking tools within Kanban or other Agile practices to document testing activities, track defects, and support team visibility. * Strong analytical skills and QA testing knowledge to define problems, collect data, establish facts, determine test coverage, and apply risk-based testing approaches. * Strong collaborative skills for working with Product Owners, Software Engineers, Scrum Masters, QA team members, and business stakeholders. * Ability to work effectively in a continuous delivery environment using Jenkins or similar CI tools and version control systems such as Git, SVN, or similar tools. * Ability to work in a dynamic, fast-paced Agile environment with changing requirements and concurrent project demands., * Problem Solving * Detail Oriented * Interpersonal Skills * Oral Communications * Written Communications * Organization * Accuracy * Adaptability * Dependability ## Description The QA Testing Engineer III designs and maintains manual and automated tests that support product quality and defined requirements. This highly experienced individual contributor leads product-area test strategy, identifies quality risks, provides release-readiness input, and supports maintainable automation. The role collaborates with Product, Engineering, QA, Security, and other stakeholders to validate product behavior, improve quality outcomes, and support continuous delivery. This position uses modern QA tools, including Playwright or similar frameworks, and responsibly applies AI-assisted testing while validating outputs and protecting sensitive data., Note: The duties listed below serve only as illustrations of the various types of work performed. The omission of specific statements of duties does not exclude them from the position if the work is similar. * Independently create, execute, maintain, and document manual and automated API, UI, regression, integration, and performance tests aligned to user stories, acceptance criteria, and project goals. * Lead product-area test strategy, make risk-based coverage decisions, support release readiness, and maintain automation using Playwright or comparable tools. * Communicate defects effectively to the product team and work with product owners to ensure defects are properly documented, prioritized, and addressed within the product backlog or active sprint/workflow. * Collaborate with Product Owners, Software Engineers, Scrum Masters, QA team members, and stakeholders to resolve defects and quality risks while ensuring test artifacts and validation activities reflect security requirements, sensitive-data handling, and secure testing practices. * Can independently query raw data sources, including text files, databases, APIs, XML/JSON messages, and system outputs, to verify accuracy of product responses and expected results. * Recommend tactical alternatives and process improvements within the testing arena. * Provide level III recommendations for assigned product areas, including test strategy tradeoffs, risk assessment, release-readiness input, and automation maintainability concerns. ## Related Videos - [Improving quality with Agentic AI with Rovo Dev and Xray](https://www.wearedevelopers.com/videos/2005-improving-quality-with-agentic-ai-with-rovo-dev-and-xray) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [Tips and Tricks for Working with JSON](https://www.wearedevelopers.com/videos/1229-tips-and-tricks-for-working-with-json) - [How I Built QA from Scratch in a Scaling Startup - no fluff real life story](https://www.wearedevelopers.com/videos/2041-how-i-built-qa-from-scratch-in-a-scaling-startup-no-fluff-real-life-story) - [Git for Code Reviews](https://www.wearedevelopers.com/videos/429-git-for-code-reviews) - [Continuous testing - run automated tests for every change!](https://www.wearedevelopers.com/videos/190-continuous-testing-run-automated-tests-for-every-change) ## Related Articles - [The 8 Best Code Testing Tools](https://www.wearedevelopers.com/magazine/402-the-8-best-code-testing-tools) - [How to create a test plan for software testing](https://www.wearedevelopers.com/magazine/56-how-to-create-a-test-plan-for-software-testing) - [What is a Test Plan: Guide to Test Planning](https://www.wearedevelopers.com/magazine/191-what-is-a-test-plan-guide-to-test-planning) - [Benefits of Using JMeter For Performance Testing](https://www.wearedevelopers.com/magazine/96-benefits-of-using-jmeter-for-performance-testing) - [Integration And E2E Testing: Are They Complementary or Interchangeable?](https://www.wearedevelopers.com/magazine/86-integration-and-e2e-testing-are-they-complementary-or-interchangeable) - [13 AI Tools for Developers](https://www.wearedevelopers.com/magazine/302-13-ai-tools-for-developers)