
Sign up to save your podcasts
Or


The entry-level QA job is dead. It didn't die because of the economy. It died because the barrier to entry has been completely nuked by AI.
In this episode, I explain why companies are no longer hiring junior testers, why the "just learn prompt engineering" advice is a trap, and what you actually need to do to survive the AI extinction event in software testing.
If nobody hires juniors today to do the grunt work, who the hell is going to become a senior in five years? Companies are eating their own seed corn.
📺 Prefer the visual version? Watch this episode on YouTube: https://youtu.be/VmYj03Su6KI
🤝 Join the discussion and connect with me on LinkedIn: https://www.linkedin.com/in/ciepielewski/
Go look at a QA job ad on LinkedIn right now. It asks for Docker, AWS, Kubernetes, and microservices. And somewhere at the bottom, in tiny font: "must know how to write test cases".
The job title says QA, but the interview is for a Full Stack Developer. And it's time we talked about it.
In this episode, I explain why companies copy-paste developer interview processes for QA roles, why you're expected to know everything from architecture to DevOps, and why this trend is ruining the industry.
📺 Prefer the visual version? Watch this episode on YouTube: https://youtu.be/1Pem2Q71xMM
🤝 Join the discussion and connect with me on LinkedIn: https://www.linkedin.com/in/ciepielewski/
AI isn't coming for QA. It's coming for the people who think QA is just executing a checklist.
In this episode, I break down why the panic about AI replacing testers is mostly misunderstood, who is actually going to lose their job, and what skills you need to develop to survive the next three years.
AI is a mirror. It reflects exactly how much actual value you bring to the table.
📺 Prefer the visual version? Watch this episode on YouTube: https://youtu.be/hrR7nKF28mA
🤝 Join the discussion and connect with me on LinkedIn: https://www.linkedin.com/in/ciepielewski/
Vibe testing: the practice of letting AI write your code and then letting AI test it. Sounds efficient. Isn't.The data on AI-generated code quality is genuinely alarming - and most teams haven't seen it. In this video I go through what the research actually says, why "the AI tested it" is not a testing strategy, and what teams should be doing instead.
📺 Prefer the visual version? Watch this episode on YouTube: https://youtu.be/I-mtSIloerk
🤝 Join the discussion and connect with me on LinkedIn: https://www.linkedin.com/in/ciepielewski/
"Quality is everyone's responsibility" sounds great in a corporate slide deck, but in reality, when everyone owns quality, nobody does.
In this episode, we break down the diffusion of responsibility in software engineering teams, why vague management slogans lead to sloppy code delivery, and how senior teams build real accountability across dev, QA, and product.
Does your team have clear quality boundaries, or are you hiding behind shared responsibility? Share your experience in the comments below.
📺 Prefer the visual version? Watch this episode on YouTube: https://youtu.be/Z0WwIEYqNxU
🤝 Join the discussion and connect with me on LinkedIn: https://www.linkedin.com/in/ciepielewski/
The idea that your staging environment mirrors production is a costly illusion.
From stale seed data and broken third-party sandboxes to false confidence and big-bang deployment delays, staging environments often cause more friction than they prevent.
In this episode, we break down why true staging parity is impossible, the hidden cost of sandbox dependencies, and how modern engineering teams use feature flags, canary deployments, and observability to test safely where it actually counts: in production.
📺 Prefer the visual version? Watch this episode on YouTube: https://youtu.be/zh7QjNIv-Co
🤝 Join the discussion and connect with me on LinkedIn: https://www.linkedin.com/in/ciepielewski/
"QA will catch it before release." It’s one of the most dangerous phrases in software engineering.
When teams start using QA as a safety net, developers stop taking responsibility for quality. What was meant to be a layer of defense becomes an excuse to ship unverified code, leading to endless context switching, toxic team friction, and a massive drop in delivery velocity.
In this episode, we break down the "moral hazard" of software delivery, the true cost of the Dev-QA ping-pong loop, and why true quality can only be built at the source - not tested in at the end.
If you are tired of process anti-patterns slowing down your engineering team, make sure to subscribe to the channel. Let's discuss your team's approach to dev testing in the comments below.
📺 Prefer the visual version? Watch this episode on YouTube: https://youtu.be/P-i7YBsaE-U
🤝 Join the discussion and connect with me on LinkedIn: https://www.linkedin.com/in/ciepielewski/
The tech industry has convinced us that more automated tests always equal better software quality. But in reality, over-testing creates fragile, high-maintenance test suites that destroy engineering velocity and slow down deployments.
In this episode, we break down the hidden cost of test maintenance debt, why trying to test every edge case is a symptom of fear-driven engineering, and how senior quality architects use risk-based testing, feature flags, and observability to ship faster without breaking production.
📺 Prefer the visual version? Watch this episode on YouTube: https://youtu.be/8-CyImnJ0mA
🤝 Join the discussion and connect with me on LinkedIn: https://www.linkedin.com/in/ciepielewski/
Modern software engineering has become obsessed with corporate metrics. We track 100% test coverage, 100% pass rates, story point velocity, and zero defect leakage. But according to Goodhart's Law, the moment a measure becomes a target, it ceases to be a good measure.
In this episode, we break down how vanity metrics encourage teams to game the system - writing assertionless tests, quarantining failing suites, and inflating Jira ticket counts—and outline what high-performing engineering teams should actually focus on instead.
📺 Prefer the visual version? Watch this episode on YouTube: https://youtu.be/A9-DUiOOSp8
🤝 Join the discussion and connect with me on LinkedIn: https://www.linkedin.com/in/ciepielewski/
The tech industry loves preaching the concept of "Shift Left" testing - the idea that involving QA early in the development lifecycle prevents bugs and saves millions. But for most engineering teams, the reality looks completely different. In this episode, we break down how shift left has been transformed into a corporate buzzword used to gaslight testers, hide broken project management, and shift blame for late-stage delivery failures.
We look at the contrast between the theoretical PowerPoint slides and the brutal reality of the two-day sprint deadline panic, and outline practical, data-driven ways to push back against corporate process theater.
If you are tired of superficial agile advice and want a realistic look at modern software delivery, make sure to subscribe to the channel. Let’s talk honestly about your team's current process bottlenecks in the comments below.
📺 Prefer the visual version? Watch this episode on YouTube: https://youtu.be/flqsBhalB-Y
🤝 Join the discussion and connect with me on LinkedIn: https://www.linkedin.com/in/ciepielewski/
From the publisher's feed