Thankyou for giving honest view from your experience. It is really an eye opener.

Your videos are really informative and I appreciate the effort you put into them. As someone who is currently a senior in college and going to be entering the field soon, I really appreciate everything you have to say. Keep it up! Hopefully this channel continues to turn into a fun thing for you to spread your knowledge to people like myself.

I tested Windows 10 at Microsoft and found a plethora of bugs. Test engineers are never going away, and this is classic lack of respect for quality assurance. Customers should not be your test engineers.

Explanation is amazing as always.✌️✌️

Hi John, I graduated in an unrelated field to cs, but I found my passion the last two semesters (thanks to some engineering programming classes) and I applied to tech jobs. It was hard to get my foot in the door, but I eventually found a job in QA/Testing role. It has been a great year but like you said, I wanted to move on to actual development. I just landed a job offer as software engineering. So it is nice to hear that I'm making a rational move. I'm a bit worried though, the company I got the offer has bad reputation online, plenty of posts of how is a witch company and will ruin my career (a bit dramatic in my opinion) but the team I interviewed with did not give any of those red flags listed online. I would love to hear any of your recommendations on how to assess these offers. Thank you on the videos!

I hear and understand what you're saying mate, but as a seasoned tester of 23 years, one thing I've learned about developers is that they don't always properly test their own code (they also test to pass) and that includes integration in the small. Many don't follow a set standard of coding, each person has their own personal standard for meeting requirements/usecases. Many builds eventually moved into the test environment fail a basic smoke test and get rejected by QA. Often developers underestimate in their estimating, which often results in less time for QA testing, as Dev took longer to deliver than expected, not to mention all the environment issues in DEV/QA/UAT not closely reflecting Production, hence installation issues and data issues. So what I'm trying to point out is that a manual QA team is still needed (let's not forget all those browsers, tablets and mobile phones with their different operating systems and versions and the need for scalability and legacy testing). User Acceptance Testing for the most part is still run by a QA team that helps walk business through software changes and new features. Also let's not forget that Test automation (require skills in coding) has been around for some time as well and AI in testing seems to be the new push. I understand it's about budgets and time and the client wants everything for nothing, but many many many organisations would go bust if they cut out QA Testing.

Hey John, It's quite shocking to me since I am trying to jump into QA test. I have no background about IT and hopefully with 2 years studying polytechnic, I can find a job in this field. So if QA is not a good field to invest in, which part of IT should a beginner as me begin with? I come from Sweden and I guess maybe Sweden in the next few years would be the same as in US now. Looking forward to your suggestion.

So what do you think about other types of role that kind of hang off of / support development, but are not actually part of it, like build engineering, or change management? Kind of DevOpsy type roles that you see at some companies? Is there a future for those groups?

Hey i am 28 years old having 2 years of automation testing and 5 years into manual , somewhere i agree but the codebase and infrascructre is so vast that testing would likely to be a key skill while doing migration to new tec stacks or environments, suddenly stumbled at your video title and not sure what to do next ? Any suggestions?

Great video as always

great video, as always. Do you think the same applies to roles like Site Reliability Engineering?

appreciate your video, really gives some good advice, do you think transitioning to pre-sales/solutions engineer/sales engineer is a good decision for long term career ? where you help customers onboard to your product

Hi John, I just discovered your content and by far it has been a trip. I am in QA and noticed there are some principal test engineer position. What are your thoughts on that type of position? Or would it be similar to what you said in the video?

Got put on a QA team for my first rotation on a software engineering grad programme. I was livid, and that's before I knew I'd be doing mostly manual testing. Put me in a pretty awkward position as I could not claim to have any software engineering experience on my resume, so I wasn't able to find a better job in my area. Tried to get switched to another team to no avail, despite the original job listing having zero resemblance to my actual role. Thankfully I'll be on a software engineering team soon for the second rotation, but I'm still a year behind in terms of experience and not too happy about that.

How does one move out of QA/SDET? If looking internally, within the company, didn't work and looking outside the company is not working. What do you recommend? Do you have to start from the bottom as a junior SWE, even if you have a decade of QA experience? And will this require taking a pay-cut?

Coming from a non-tech background I'm looking at QA as an entry point to get my foot in the door while I work on my Software Engineering degree because I hate my current job and want to get into tech as soon as possible. Do you think this is a good plan?

Absolute gem! What do you think about Release Engineering/Devops ?

Thank you for your insight. What can you tell about modern QA teams who run literally thousands of automated tests ensuring quality (like banking apps for example). I am talking about sdets. The reason I am asking is it seems like modern web apps have low quality and qa's seem to be relied upon.

Great content. 👍👍👍

Hi John, I'm interested in testing but doesn't QA Testing invovle less actual coding than a regular Dev, especially if you're using codeless tools like JMeter, UI Testing, etc ? I enjoy testing, finding bugs, UI/UX and so on but don't want a job that's all or even mostly coding.

Do you have a link to that paper on the efficacy of testing?

Hey John - I feel like I've just stumbled across a gold mine here watching your content. We need more folks with your wealth of experience sharing the do's and don'ts that they've experienced, so thank you very much! I'm not personally within Software, rather I'm in Security. How common was it across your career with collaborating with Security?

Oh man, your videos are underrated, this channel is going to the moon really soon!

I’ve been a QA for about 1.5 years now, after one year in my previous company I was recruited by another one that gave me a promotion as Midd QA. I support what this video says. I was considering just continuing on this path and becoming a Senior/Manager, as I think I’m a pretty good QA and Im growing fast. However… I’ve always felt QA is second class (because it is) and it’s not enough.

I used to work in companies that consisted of larger test teams: The developers to testers ratio was about 3-5 to 1. The development teams did not have much incentives to test their own work or write automated tests. They were incentivized by shipping new features. In this case, these organizations required dedicated testers. Retaining only a skeleton test team could increase the impact generated per employee, but training developers with an eye for quality does not take place overnight. The developers need coaching and positive reinforcements to produce high quality work. Do you have any stories, anecdotes or solutions to have the developers to own the quality of their own work in a greater capacity than before?

This is interesting, but it will also be valuable to counter some points. OP just chanced to work in conditions which while common, aren't representative of every kind of software. Microsoft made a big push towards spending less on QA, while Amazon was always known for dedicating very few resources to QA. This doesn't mean they didn't do testing, they just made developers into bad testers. The general idea here is that there isn't much to know about testing and that a developer will easily be able to do what QA does. This works some times more... sometimes less. Specifically, this doesn't work when QA has to be a domain expert (think medicine, or finance as an example). It's just very hard to find a programmer who's also a certified nurse or a mortgage advisor. Another situation when this approach to QA doesn't work: highly reliable systems. Think stuff like air traffic control or just even filesystems. Testing these things requires a lot of dedicated knowledge which developers will normally not have (i.e. knowledge of dedicated testing tools or load generators etc.) Products like MS Windows on the other hand are designed for users with no special expertise and aren't required to be very reliable (outside of a few components). So, there's a lot of truth to what this video claims. Often times dedicated QA teams produce very little value and owe their existence to the inertia of how development process used to be organized decades ago. This isn't always the case, but, probably, building your career on hoping to get that exceptional role / position isn't a sound strategy.

I just started a bootcamp on QA, and I feel screwed after watching this video. Any tips on how to make myself marketable so I can switch once I am done with mt QA bootcamp.

Glad I came across this video as someone who’s in QA/Test development. I work at a small startup and recently informed my manager that I want to switch to a product developer role within the company, so hopefully that happens this year. I enjoy being in QA/test now but I think it’s because our company values it/needs it. This may not apply to other companies going forward like you mentioned. How was your experience transitioning from writing test code to product code? Do they have a lot of things in common? Just want to know your thoughts.

I work as senior SDET i know python java and sql...Can u suggest which path i can take...Can i take data scientist or do u think new roles of QA will come for AI or data scientist or ML.Please suggest

Started out in QA, and a couple months in I was feeling what you describe here. Moved into an SDE position in the same company, and I haven't looked back. That brief QA period got me up to speed with the more broad aspects of what my company does since I had to validate projects in different areas, yet save for that, and some scripting/general knowledge (which you get anyway in the SDE role), I don't think anything else would've been really transferable. The domain can be very specific, which had me fearing that I could put years into the QA role, and end up becoming an expert... in my company's niche. The "I helped make that better" vs "I made that" hit hard. I actually told some variation of that to HR when they asked why I wanted to move. I agree with another comment: this channel should be going to the moon!

If I have to write a testing document for QA, what’s the point of having QA? The only type of QE I support is when I don’t have to give them specifics. Juts a summary of changes and they try to find bugs. The rest is useless

I am a QA engineer for over seven years in different areas now. I‘ve been switching companies and teams a lot within the past years because there often came the point that I was frustrated about the way the team or the company handled the quality aspects of the product. Than I was realizing more and more that my work often do not bring in the value of making the product better than thought it would be. That’s a bit tough because I really love to do test automation. Now your video catches me up right at the process of thinking about switching to the production development and to build parts of the product. Do you have any experiences or best practices on switching to become a developer from someone who was Test Automation Engineer before?

What's your opinion on working in operations ?

What advice would you offer to someone beginning their career as a manual QA, especially if their initial role also marks the company's first venture into QA? Essentially, this individual will be the pioneer, establishing the standards and expectations for the role.

I am a QA inspector, but I don't test software. I do quality assurance on aerospace and military.

I have been working in QA for 4 years, How do I move out of QA to SDE , what skills should I upgrade. If I am looking to move within the company , how should I approach it. Also what do u think of the learning gained in job as a software tester vs software developer

Hey, John. It's been a while. I hope everything's going well. In addition to the things you said, I'd point out that the market for software engineers is a broader market than for SDETs. Being in test limits your career unnecessarily. When I switched from SDET to SDE at Microsoft in 2004, they had said the same things you indicated -- that the role was just as valuable, etc., etc. But if you looked at the ladder level for compensation, SDET was one level down from SDE for corresponding competency and responsibility levels.

You are forgetting to mention that developers are stressed out, burned out, and on call rotations. QA isn't like that. You couldn't pay me 1 million a year to be on call and burn out often, causing my mental health to suffer, not worth it...

Well for people like me, it’s a foot in the door. Someone with no contacts or social capital, I think that’s the way to look at it and respectfully disagree. Not only that, the startup world is extremely different.

I don't know if this is a trend in the industry or I've just had bad luck in my last couple of jobs, but I've noticed a really toxic pattern in software QA over the past few years. Management sets unreasonable expectations for how much a small QA team can test over a period of time. To meet the deadlines, the QA team can only test at a very superficial level. However, if a bug ever gets through, the tester for that feature is thrown under the bus for missing it.

do you remember the papers about efficacy?

I agree for the most part. I do QA in video games and think the impact has been damning for the game industry. Many companies took this approach " i can just patch it" . With entertainment software and art you will lose your customers. I can't remember a large video game release that hasn't been a buggy mess since 2015.

Do you think Platform teams are bad for your career?

I think there will always be room for skilled testers as long as there is software to sell. End users, developers, and automated checks can find a lot of problems, but in many cases, just using these approaches alone doesn't work very well.

Been seeing a lot of Manual QA ppl getting laid off. Happened to me. I'm in QA but trying to learn Development now

I don't understand... Who cares if product is shipped in a box, or it can have online patches. You still have to have person for quality. I mean, even if you outsource production in China factory, there is someone for quality of final product.

6+ years as "test developer" in Microsoft? :D No wonder of thy conclusions.

I am a former QA Analyst. I left the field in 2017 because I decided it wasn't my thing. Actually, it never really was what I wanted to do. Now I'm gearing up to be a Data Engineer, which is so much closer to what I'm best at.

Isn't QA testing like a entry level to hi tech industry. If someone wants to progress go ahead but I don't see nothing wrong being QA tester

Yeah there some parts that u did great, but as saying SDE only the most important role in development cycle that's totally wrong.

You clearly don’t work in government departments that still are 15/20 years behind the trend 😂

i just found oiut that this guy is a phd from cambridge university. he's insane.

This video is so passe it is laughable. No big tech is laying off based on dev/QA roles, heck you think these big ceos have time to weed out the devs from QAs? It's just an old outdated philosophy that was perhaps true while he was in the peak of his career. Just compare this advice with the recent layoffs and you'll know his opinions are so so outdated.

Can I connect with you on LinkedIn ??