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

---

# Quality Engineering Lead

- **Company:** Thyme Care
- **Location:** United States (Remote available)
- **Experience:** Expert
- **Salary:** $200,000.0 - $235,000.0
- **Contract:** Permanent contract
- **Skills:** Automation of Tests, Software Bug Management, Software Quality, Continuous Integration, Software Debugging
- **Published:** September 30, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=09d0dd1e4ee6ba37

## About the Role

* You have 5+ years building, shipping, and supporting software in production, as an engineer, quality engineer, or SRE, including 2+ years leading or mentoring engineers as a manager or tech lead.
 * You're fluent in quality tooling like CI pipelines, automated testing, and observability, and you can raise the bar on a product you don't own.
 * You've communicated objectively about quality with technical and non-technical stakeholders, including when the news is unwelcome.
 * You can brief engineering and product leadership on quality trends concisely, verbally, and in terms they can act on.

Nice to have, but not required:

 * You have prior experience working in healthcare or health tech.
 * You've thoughtfully leveraged AI tooling to support developer productivity, code quality, and engineering best practices.

WHAT LEADS TO SUCCESS

Curiosity. You want to learn an entire product and the systems underneath it, including the parts nobody has documented. You're energized by finding out how something actually works rather than how it's supposed to.

A debugging instinct. You like the part of the job where something is broken and nobody knows why. Root cause analysis is satisfying to you, not a chore you complete after the fix ships.

Clear signal. Most of your interaction with engineering and product happens in Slack and Linear, and the rest happens live with Thyme Box leadership. You can explain what's wrong and why it matters without getting sidetracked.

Influence without ownership. You can raise the quality bar on a codebase another team owns. You get there through evidence and relationships rather than gates and mandates.

## Description

As a Quality Engineering Lead, you will own the feedback loop that tells the Thyme Box team what's breaking and what to fix first, and you'll make sure a quality mentality shows up at every stage of how we build. Thyme Box is our proprietary internal care management platform, and the primary tool that enables 600+ Care Team members to deliver clinical and non-clinical navigation services to members every day.

Additionally, you will:

 * Manage and grow a team of 1-2 quality engineers, staying hands-on technically as you do it.
 * Set quality strategy for Thyme Box: what good looks like at each stage, and how to measure it. The Thyme Box team owns its test planning and testing; you own the standard and whether it's being met.
 * Add feedback points throughout the product lifecycle, from requirements and technical design through implementation and release.
 * Check that test plans exist and hold up before work is built.
 * Lead the team that owns our Thyme Box bug triage process and the systems that track it, and bring the trends to engineering and product leads so they can prioritize. You own the trends and the recommendations; the Thyme Box team owns the fix.
 * Run exploratory testing on new and existing functionality yourself, especially at system boundaries and integration points.
 * Support automated testing and quality tooling where it unblocks the Thyme Box team, without taking the work off them.
 * Occasionally pick up a fix yourself when it helps the Thyme Box team move faster.
 * Own root cause analysis on escaped defects and production incidents, and share written findings broadly.
 * Participate in incident review and close the loop from production issues back into how we build, so the same class of defect doesn't return.
 * Mentor and develop your reports, and hold the hiring bar as the team grows.