I explore QA/Tester SEiT open positions from time to time and I noticed that there are less and less of them, especially in potentially interesting places.<p>Do you have QA in your team? Of no, may I ask why?
I think QA is still a very important role in a serious company, we still have a lot of QAs in the company I work in.
We developers do write tests but that is usually not enough and QA always founds meaningful bugs.
IMO a good QA team is still really valuable.
Management may not see it that way, but a cunning, experienced tester is invaluable.<p>The nature of testing may have changed.<p>For one, the approach to testing is different with more smaller iterations and more powerful automation.<p>For another, better automation has split testing into more of an automated test developer/pipeline plumber part and an exploratory (manually testing the juicy stuff, the boring routine is handled by automation) part.
Not dead at all. At my current company, 15% of the total tech team is comprised of QA/SDETs. Though, Manual QA is now being replaced with automation. For every new feature we work on, we have to make sure that we have automation ready before we go live into production. We work on Selenium, Appium, Karate for automation. We use ADF for testing our apps on real devices. Our CI/CD pipeline takes care of running the tests and when the tests fail, deployment doesn't happen.<p>Like every other job, you've to keep yourself updated with the latest.
For many, the QA/tester was someone not worthy of being a developer because of not having sufficient programming skills. Nowadays the testing frameworks (web front-end!) got so complex and testing stacks so hysterical that QA/tester job is basically full time development job. Thus, developers do the QA/tester job nowadays (which doubles their work).
The QA/Tester profession isn't dead, but the traditional manual testing role is dying out. Most of the companies I know that use manual QA processes have outsourced the manual QA to teams in Asia (primarily India) and those are only used for legacy products where writing tests are difficult/impossible. My current company (~50 people) doesn't have QA, and we would only consider hiring someone in QA if they were able to write high-quality test code (contractors we've used in the past have written test code but not high-quality). Using GUIs to create automated tests are a no-go. Those people I know with QA backgrounds all have significant difficulty finding new positions, even if they are good (6 months unemployed would not be unusual)
We’re having trouble finding QA’s to hire at my current company so that may have something to do with there being less positions.<p>To be fair, we’re not really in a tech hot zone so that might be why we struggle.
QA is still much a thing in our company, although not necessarily working in the traditional "assurance" role but rather in a "assistance" role.
Lately, I have been searching for open engineering test positions in Microsoft, and I have found none of QA, Tester, SDIT, SEIT etc.<p>The same goes for duckduckgo