<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>QA on LeanTechPro</title><link>https://leantechpro.com/tag/qa/</link><description>Recent content in QA on LeanTechPro</description><image><title>LeanTechPro</title><url>https://leantechpro.com/images/2026/05/leantechpro-og-image.webp</url><link>https://leantechpro.com/images/2026/05/leantechpro-og-image.webp</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 10 Oct 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://leantechpro.com/tag/qa/index.xml" rel="self" type="application/rss+xml"/><item><title>Focus on becoming an engineer who judges quality</title><link>https://leantechpro.com/notes/qa-engineer-who-judges-quality/</link><pubDate>Sat, 10 Oct 2026 08:00:00 +0000</pubDate><guid>https://leantechpro.com/notes/qa-engineer-who-judges-quality/</guid><description>AI already drafts cases, writes scripts, and heals locators. What still pays is owning risk, systems, and verification when the output is cheap and often wrong.</description></item></channel></rss>