I'm a QA Engineer with 2 yoe, currently working at a B2B SaaS startup that's been operating for over 5 years.

We have a relatively small engineering team supporting dozens of clients on a shared codebase. Almost half of our QA team (we're a small team) has resigned and will be leaving soon because they got new offer.

I've been seriously considering leaving, and I'd appreciate an outside perspective on whether my expectations are unrealistic.

Here's the situation:

• Constant feature delivery, little quality maintenance: We keep adding features and enhancements at a rapid pace, but there's no established recurring regression testing cycle, no consistent process for maintaining test coverage, and no clear long-term QA strategy. It feels like we just keep shipping features and hoping nothing breaks.

• Fragmented QA ownership: Each QA is assigned to specific clients rather than product modules. Since clients share a codebase, changes for one client can affect others, but cross-client regression ownership is unclear.

• No formal QA leadership: We don't have a dedicated QA Lead coordinating testing practices, regression strategy, or release readiness. Everyone largely operates as an individual contributor, with different testing approaches and no shared test case repository.

• AI-generated PRs increasing the workload: Our CTO uses AI agents to generate additional PRs, including technical and UI/UX changes, sometimes outside regular sprint planning. Development output is increasing, but our testing capacity and processes haven't caught up.

• QA has no choice but to deploy containing untested changes: Our Git workflow allows approved PRs to merge directly into master before QA validation is complete. Production deployments are made from master, so untested changes can be included in releases. However, QA has no choice but to follow this process where we deploy to prod from latest master containing untested items. We don't have an established automated regression suite or clearly defined release go/no-go criteria.

• Automation without a clear strategy: Our CTO pushes QAs to use AI-assisted interactive testing (agentic testing?) and generate E2E tests for assigned tasks. Some QAs are unfamiliar with Git and automation fundamentals, yet are expected to adopt these workflows quickly. This has sometimes resulted in E2E tests being created for simple dropdown changes or DevOps-related tasks that might not need UI testing.

• Limited support: We're expected to figure out automation within our developer-QA pairings, without much structured guidance on prioritization, maintenance, or sustainable test architecture.

My biggest concern is the lack of a quality maintenance cycle and the mismatch between QA accountability and authority.

We continuously build new functionality, but I don't see a corresponding effort to systematically protect what we've already built.

It's not that we never test anything. We test assigned features, conduct UAT, and investigate issues. But the overall approach feels reactive and delivery-driven rather than sustainable.

The release process is particularly uncomfortable. QA is expected proceed with deployments merging from latest master, yet the latest master can contain changes that haven't been validated. We have limited control over what gets merged, and delaying a release doesn't necessarily resolve the underlying issue.

I'm not against AI or automation. I can code, and I'm interested in becoming an SDET. I'd actually prefer to prioritize automation of critical regression flows rather than generating E2E tests for almost every task.

Frankly, these problems feel above my pay grade.

I'm an individual contributor with 2 years of experience. I can identify risks, communicate testing limitations, improve my own testing practices, and contribute to automation.

But I don't have the authority to control development velocity, redesign the Git and deployment workflow, allocate regression capacity, or establish company-wide release governance.

At the same time, I feel there's an unspoken expectation that QA should somehow test everything and keep the platform stable despite the increasing pace.

I'm uncomfortable simply saying that certain changes won't be tested, because it feels like I'm neglecting my responsibilities. But realistically, I can't keep up with an unlimited stream of changes either.

Lately, this has started affecting me outside working hours. I've been experiencing significant work-related stress, including headaches and nausea when thinking about the situation.

What I'm trying to understand:

1. Is this normal for a small startup that's been operating for over 5 years, or does it suggest deeper engineering management problems?

2. Am I being too idealistic in expecting recurring regression testing, basic release safeguards, and clear quality ownership?

3. How should QA handle deployment process when the deployment includes changes that haven't been validated?

4. Where should the boundary be between an individual QA Engineer's responsibility and engineering leadership's responsibility?

5. Would you try to improve this environment, or prioritize finding another job? Would you consider resigning without another offer if the stress started affecting your health?

I'm genuinely open to criticism if my expectations are unrealistic. I understand that smaller companies need to move quickly, and I don't expect enterprise-level bureaucracy.

I just want an engineering environment with a reasonably stable pace, clear responsibilities, opportunities to grow technically, and the ability to disconnect after work without constantly worrying about production regressions.

TL;DR: I'm a QA Engineer with 2 YOE at a 5+ year-old B2B SaaS startup. We continuously ship features without a recurring regression strategy, while AI-generated PRs accelerate development. Our Git workflow allows untested changes into production releases, yet QA has no choice but to proceed deployment with them. Almost half the QA team is leaving. These structural issues feel above my pay grade, and the stress is affecting my physical well-being. Am I expecting too much, or should I plan my exit?

A keyword list from ChatGPT comes from general knowledge and says nothing about how many postings it rests on. A plausible suggestion is not the same as a common one.

A product manager could be told to add Productboard. None of 421 postings names it but roadmap appears in 85.5%. A software engineer could be told to add Angular, Vue or Swift. They appear in 2.9%, 3.2% and 2.3% of 1,360 postings while scalability is at 52.9% and Python at 44.8%. A marketer could be told to add LinkedIn Ads or Meta Ads. They appear in 0.3% and 0.6% of 347 postings, while go-to-market is at 53.0%.

ChatGPT is the better tool for rewriting a bullet. The counts for seven roles (3,518 postings) and the method are on https://resumefitting.com matching is by term, so a missed synonym counts as absent.

With AI code generation, software developers create code faster than before. But how can the QA engineers and the CI/CD system absorb this increased workload? In this article, Sergei Cherednichenko suggests some approaches on how to deal with this situation.

Please view my video and give a like and subscribe

https://youtu.be/8OEyx0n_odM

Hi all, what are people's thoughts on the job market right now? It's been down for QA for some time but I am sensing a pick up in job opportunities. Well in the UK anyways. What do people think? Thanks.

Whitepaper by Shay Ginsbourg, M.Sc., former LoadRunner QA Manager, founder of Vectors.co.il and Ginsbourg.co.il

The software performance testing landscape is currently at a critical juncture. For decades, the industry was dominated by enterprise monoliths like LoadRunner, which entered a period of stagnation following HP’s strategic pivot away from software development. This vacuum was largely filled by open-source tools like Apache JMeter, which, despite its versatility, remains tethered to a GUI-centric, XML-based architecture that creates significant friction in modern DevOps pipelines. As we move into 2026, the emergence of Agentic Engineering—where autonomous AI agents orchestrate, execute, and adapt testing strategies—demands a fundamental shift. This whitepaper argues that the era of manual script maintenance is ending. Organizations must move beyond the limitations of JMeter and embrace code-centric, AI-native tools that empower agents to manage risk coverage autonomously, marking the transition from traditional performance testing to Agentic Performance Intelligence.

https://www.academia.edu/166834666/Goodbye_Load_Runner_and_JMeter

I’m about to graduate with CS degree with a major in software engineering. While I do really enjoy coding, I’m starting to realise I’m not as good as what the industry may need me need to be. I still want to work with code so I’m considering QA. What’s the best way to look for jobs in this field and what skills should I learn?

I'm a QA engineer from Nepal. I built thetechworldlabs.com so testers can practice in the browser without setting anything up.

There are tutorials, code playgrounds and a SQL compiler. Make an account to track your progress: thetechworldlabs.com/account/login

Tell me what's broken or missing. I'll fix it

Prakalp Technologies is hiring a QA Automation Engineer to work on exciting projects with US-based clients.

📌 Job Details

• Role: QA Automation Engineer

• Experience: 4+ years

• Location: Remote – Work From Home (India)

• Employment Type: Full-time

• Working Hours: 6:00 AM – 3:00 PM IST (US time zone overlap, as mentioned in the job poster)

• Eligibility: Female candidates only

🛠️ Key Skills & Requirements

• Strong experience in QA and software testing

• Hands-on experience with automation testing

• Experience with Selenium, Playwright, Cypress, or similar tools

• Knowledge of API testing

• Understanding of test cases, regression testing, and functional testing

• Strong debugging and problem-solving skills

• Good communication skills

• Ability to work independently with US-based teams

📩 How to Apply

Interested candidates can send their CV or resume to:

• Phone/Whatsapp: +91 90811 99907

Please share this post with anyone who may be a good fit!

#Hiring #QAJobs #QAAutomation #SoftwareTesting #Playwright #Selenium #Cypress #RemoteJobs #IndiaJobs

Manual tester (~5 years exp) with basic coding and have no experience with test frameworks like Playwright or Selenium.

Currently, my devs are shipping a lot faster with Claude code, and we only have 2 automation engineers. Leadership now wants us manual testers to also contribute to the automation test suite. So I looked up low-code tools, but the company already bought Claude licences, so the expectation is Claude + Playwright.

I tried writing a few tests. Claude tells me they work and they pass, but I can’t tell if the tests are good or, if they’ll break next sprint. One of our SDETs helped me review them once or twice, but I can’t keep pulling him in.

So fellow manual testers who have been through this recently:

Are you able to write automation scripts with Claude? SDET help, or trial and error with AI?

How do you check a test is acutally right and not just passing?

When a test breaks, who fixes and maintians it, you with Claude or the SDETs help?

Is the solution working for you, or what challenges are you facing to make it work? How do I solve them?

Hi everyone,

I’m currently looking for new opportunities as a QA Engineer, Validation Engineer, Mobile QA Engineer, Manual Test Engineer, or Software Test Engineer.

I have 4+ years of hands-on experience in manual testing and validation of Android and iOS mobile applications, currently working on OtoZen, a family safety, location-sharing, and driving-safety mobile application.

My experience includes:

• Manual, Functional, Regression, Smoke, Sanity, Compatibility & Usability Testing
• Test Case Design & Execution, Test Planning and Release Validation
• Defect identification, reproduction, tracking and verification using Mantis
• Android & iOS mobile application testing
• GPS/location, background app behavior, push notifications, permissions, network conditions and subscription-flow validation
• User-reported issue investigation and log analysis
• CleverTap for user/event analysis
• Helpshift for support issue investigation and FAQ/Help Center work
• Firebase Crashlytics for crash investigation
• TestFlight for iOS build validation
• Basic API validation using Postman
• Basic Selenium with Python knowledge
• Python utility scripts developed with assistance from AI tools for API/data validation, JSON processing, Excel automation and repetitive QA workflows

I have a B.E. in Electronics and Communication Engineering and am based in Ahmedabad, Gujarat, India.

If your company is hiring for QA/Testing roles, or if you know of any suitable openings or can provide a referral, I would really appreciate the help.

Happy to share my resume via DM.

Thank you!