--- title: Tester 2.0: becoming indispensable in the age of AI description: Testers won't automatically get job security just because AI produces more code, Filip Hric argues. He identifies three comforting lies: that a 'golden age' of... canonical: https://daily.dev/posts/tester-2-0-becoming-indispensable-in-the-age-of-ai-liomahwgt twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Tester 2.0: becoming indispensable in the age of AI | daily.dev og:description: Testers won't automatically get job security just because AI produces more code, Filip Hric argues. He identifies three comforting lies: that a 'golden age' of... og:url: https://daily.dev/posts/tester-2-0-becoming-indispensable-in-the-age-of-ai-liomahwgt og:image: https://api.daily.dev/og/posts/lIomAhWGT.png og:image:alt: Tester 2.0: becoming indispensable in the age of AI og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Tester 2.0: becoming indispensable in the age of AI **[Filip Hric](https://daily.dev/sources/filiphric)** · 14 min read · 0 upvotes · 0 comments ## Summary Testers won't automatically get job security just because AI produces more code, Filip Hric argues. He identifies three comforting lies: that a 'golden age' of testing hiring is coming, that quality inevitably worsens without testers, and that things will stay the same. He urges testers to abandon avoiding technical expertise, treating critical thinking as their only important tool, and treating test automation as their only tool. Instead he describes a 'generation and verification' workflow he uses himself, with a separate review agent, and points to roles like eval engineer and forward-deployed engineer as places where testing skills transfer. A skill-file experiment burned extra tokens without really improving results. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Should QA testers learn to code and understand technical systems in the age of AI? Yes, testers should become technically proficient rather than avoiding it. Technical understanding is treated as a prerequisite for assessing quality in other engineering fields like motorsports and aviation, and LLMs reward users with more expertise, since a senior developer gets noticeably better results from AI than someone casually vibe coding without understanding the problem. _Developers weighing how deep to go on AI tooling can track these skill shifts on daily.dev._ ### How can I use AI agents to catch bugs before running end-to-end tests? Split work into generation and verification: one coding agent implements a ticket, while a separate review agent (often a different model) checks whether the ticket was fully implemented, whether rules were followed, and whether there are bugs, security issues, or wider blast radius effects. This review can run on uncommitted changes, implementation plans, or even the ticket itself, giving feedback before end-to-end tests run. _Teams redesigning their test feedback loops with AI agents can follow workflow write-ups like this on daily.dev._ ### Does adding a skill file to an AI coding agent actually improve its output? Not necessarily. In one comparison of an agent working with a skill file versus without it, token usage and response time were measured alongside output quality, and the team mostly burned a lot more tokens without meaningfully improving the response, showing that adding a skill file doesn't guarantee better results. _Anyone evaluating AI agent configurations can compare real-world experiments like this on daily.dev._ ## Similar posts on daily.dev - [Testers, testing and the future: A Bifurcation into Testing AI and AI-powered Testing.](https://daily.dev/posts/testers-testing-and-the-future-a-bifurcation-into-testing-ai-and-ai-powered-testing--xgg52y1q9) · Scott Logic · 0 upvotes · 0 comments - [AI Isn’t Replacing Testers — It’s Replacing Outdated Testing](https://daily.dev/posts/ai-isn-t-replacing-testers-it-s-replacing-outdated-testing-gj6chv50o) · Medium · 0 upvotes · 0 comments - [A Seasoned Tester's Crystal Ball](https://daily.dev/posts/a-seasoned-tester-s-crystal-ball-9guhg69yw) · A Seasoned Tester's Crystal Ball · 1 upvotes · 0 comments - [Maslow's Hammer and Three Lies QA Tells Itself](https://daily.dev/posts/maslow-s-hammer-and-three-lies-qa-tells-itself-5onpjrv9e) · Filip Hric · 0 upvotes · 0 comments --- Tags: [#career](https://daily.dev/tags/career), [#testing](https://daily.dev/tags/testing), [#ai-coding](https://daily.dev/tags/ai-coding) [View this post on daily.dev](https://daily.dev/posts/tester-2-0-becoming-indispensable-in-the-age-of-ai-liomahwgt) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Tester 2.0: becoming indispensable in the age of AI","url":"https://daily.dev/posts/tester-2-0-becoming-indispensable-in-the-age-of-ai-liomahwgt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/tester-2-0-becoming-indispensable-in-the-age-of-ai-liomahwgt"},"datePublished":"2026-10-27T12:34:36.775Z","dateModified":"2026-10-27T12:35:05.894Z","description":"Testers won't automatically get job security just because AI produces more code, Filip Hric argues. He identifies three comforting lies: that a 'golden age' of...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/15754cfeebd3463136bb4941c472e802?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/15754cfeebd3463136bb4941c472e802?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Filip Hric","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Filip Hric","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/a9db5ec0eda5480592d92a27fa1ec894","url":"https://daily.dev/sources/filiphric"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/tester-2-0-becoming-indispensable-in-the-age-of-ai-liomahwgt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"career,testing,ai-coding","timeRequired":"PT14M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Filip Hric","item":"https://daily.dev/sources/filiphric"},{"@type":"ListItem","position":3,"name":"Tester 2.0: becoming indispensable in the age of AI"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/tester-2-0-becoming-indispensable-in-the-age-of-ai-liomahwgt#faq","mainEntity":[{"@type":"Question","name":"Should QA testers learn to code and understand technical systems in the age of AI?","acceptedAnswer":{"@type":"Answer","text":"Yes, testers should become technically proficient rather than avoiding it. Technical understanding is treated as a prerequisite for assessing quality in other engineering fields like motorsports and aviation, and LLMs reward users with more expertise, since a senior developer gets noticeably better results from AI than someone casually vibe coding without understanding the problem. Developers weighing how deep to go on AI tooling can track these skill shifts on daily.dev."}},{"@type":"Question","name":"How can I use AI agents to catch bugs before running end-to-end tests?","acceptedAnswer":{"@type":"Answer","text":"Split work into generation and verification: one coding agent implements a ticket, while a separate review agent (often a different model) checks whether the ticket was fully implemented, whether rules were followed, and whether there are bugs, security issues, or wider blast radius effects. This review can run on uncommitted changes, implementation plans, or even the ticket itself, giving feedback before end-to-end tests run. Teams redesigning their test feedback loops with AI agents can follow workflow write-ups like this on daily.dev."}},{"@type":"Question","name":"Does adding a skill file to an AI coding agent actually improve its output?","acceptedAnswer":{"@type":"Answer","text":"Not necessarily. In one comparison of an agent working with a skill file versus without it, token usage and response time were measured alongside output quality, and the team mostly burned a lot more tokens without meaningfully improving the response, showing that adding a skill file doesn't guarantee better results. Anyone evaluating AI agent configurations can compare real-world experiments like this on daily.dev."}}]} ```