> Markdown version of [/jobs/ext/4547884-software-quality-engineer](https://www.wearedevelopers.com/jobs/ext/4547884-software-quality-engineer). 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).

---

# Software Quality Engineer

- **Company:** Zipliens Companies LLC
- **Location:** Franklin, TN, United States
- **Experience:** Experienced
- **Salary:** $77,000.0 - $104,000.0
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Amazon Web Services, Automation of Tests, Code Coverage, Software Quality, Continuous Integration, Django Web Framework, Python (Programming Language), PostgreSQL, Server Administration, Software Engineering, Strategies of Testing, Unstructured Data, ReactJS, Large Language Models, Cypress (Programming Language), Backend, Agentic-AI, Pytest, Kubernetes, Playwright, Front End Software Development, Evaluation of Large Language Models
- **Published:** November 3, 2026
- **Apply:** https://www.careerbuilder.com/job-details/software-quality-engineer-franklin-tn--55acf709-06bc-4242-a841-346bd28c4d50

## About the Role

Quality Engineering, Software Engineering, Liens, Legal, Process Improvement, Testing, Medical Liens, Personal Injury, Quality Engineering, Software Administration, * 3+ years on a QA or software development team, including experience owning test coverage for a feature or product area.

 * Strong skills in at least one of exploratory testing and test design, test automation and infrastructure, or AI/LLM evaluation, with working proficiency in a second. We don't expect the same depth in all three.
 * Hands-on experience building and maintaining automated test suites in a modern framework (Playwright, Cypress, pytest, or similar), including diagnosing flaky tests and fixing their root causes.
 * Comfortable reading and writing code. Our backend is Python/Django and our frontend is React, and you should be able to read a change in either and understand what it affects and what it puts at risk.
 * Experience integrating tests into CI pipelines and deciding which checks should gate a merge or a deploy.
 * Strong SQL. Much of what we test lives in PostgreSQL, and verifying a workflow often means verifying the data it produced as well as what the UI shows.
 * Hands-on experience testing LLM or ML features, whether in production or through prototypes and experimentation: building golden datasets, measuring output quality, and understanding how these systems fail.
 * Experience using or experimenting with agentic coding tools, and good judgment about when their output needs a closer look.
 * Clear written communication. You'll be writing defect reports, test plans, and release sign-offs for engineers and product, and explaining risk to non-technical stakeholders., * Experience testing document processing or extraction from unstructured data.
 * Experience testing third-party integrations, especially where the counterparty's documentation isn't solid and you need contract tests, sandboxes, or recorded fixtures to work around it.
 * Familiarity with AWS and Kubernetes. We have an SRE who owns the cluster - you won't be running it, but you'll be reading logs and working out where a failure happened in it.
 * Experience handling sensitive data such as PHI, or working under HIPAA-style requirements.

## Description

* Own quality for a feature or product area, including the risk-based test strategy, the regression scope, and the release sign-off for that area.
 * Build and maintain the automated test suites for your area and keep them integrated with CI. When tests fail or become flaky, you'll troubleshoot them and fix the underlying cause.
 * Run exploratory testing against the lien workflow and develop a detailed understanding of the applications your team owns, including their risk areas and failure modes.
 * Test our LLM-based features. This includes building the evaluation suite for a feature, setting acceptance thresholds with product (for example, precision and recall targets for extraction), checking LLM-judge agreement against human labels, and adding adversarial and prompt-injection cases.
 * Use agentic coding tools to build and maintain automation, and review AI-generated tests before they merge.
 * Join refinement early enough to shape Acceptance Criteria with the Product Owner, flag testability gaps before development starts, and recommend coverage and risk priorities for your area.
 * Shepherd defects for your area from triage through resolution, writing clear, reproducible reports that engineers can act on.
 * Work directly with the engineers on your team day to day. QA at Zipliens is embedded in the engineering teams rather than run as a separate function.