In short
Yes, according to Rebecca Becker, QA Manager at Vox Media. In a short lightning talk she traces her path from being one of very few women in her university's information technology department to managing QA, and explains why manual exploratory testing remains essential. Her message to newcomers is direct: coding skills, certifications and a technical degree are all optional. A passion for problem solving and finding strange bugs is enough to start.
Key takeaways
- How to get into quality assurance in the tech industry
- Being a woman in tech in a male-dominated field
- What being a QA analyst is really about
Walking into a room full of men
Becker began her tech journey at Rochester Institute of Technology in upstate New York in 2001. She describes the moment clearly: "And here I am on the middle of this slide, and I have walked into my first class of the information technology department only to be surrounded by all men." (0:58)
Rather than being put off, she was proud to be one of the very few women pursuing a technology degree at that time. Her classmates and professors were supportive throughout her four years. The working world proved different, and she says she had to overcome many hurdles once she graduated and lost that built-in support. What carried her through was a lesson learned early: "However, from a young age, starting with university, I started learning that it didn't really matter when anyone else thought of me regardless of their gender." (2:05) She chose to work hard and follow her ambition for a tech career.
Seven years before discovering QA
Becker's first job after university was not in quality assurance at all. She spent seven years travelling across the United States training people and customers to use software, while also doing technical writing, documentation and software support.
After several roles, she stopped to ask what she really wanted to do for the rest of her career. She realised her passion lay in learning products, websites and apps, and in making sure the end user had the best experience possible. Researching other tech careers led her to quality assurance, which she found was the perfect fit.
Why QA is critical and often overlooked
Becker opens her explanation of QA with a joke familiar to every tester, a bug report that reads "everything is broken, steps to reproduce: do anything, expected result: it should work." Then she turns serious: "And don't worry, my bug reports are a lot more robust than this, but on a more serious note quality assurance is oftentimes overlooked and sometimes a really misunderstood field in our tech industry today and even in the past." (3:41)
She has worked with companies that relied solely on product managers or engineers to test their own code. For her, that is a risk: "Of course, as somebody like me in QA that was a little bit scary to me and having a dedicated team of skilled quality of testers is extremely important." (4:30)
The human side of testing
When people think of QA, Becker notes, they often think first of automation and writing code for automated tests. She values automation and says teams need it, but her career has been built on manual testing, also called exploratory testing. Manual testers get into the product, click around, think outside the box and find the unexpected bugs that leave engineers asking how anyone thought to look there.
She does not expect that work to disappear: "And for me, to be honest, this part is really never going to go away in our industry, there will always be a need for this human creative aspect of quality assurance." (5:24) In her view, people find bugs in creative ways that automation code cannot.
Three myths that keep people out of QA
Becker focuses on three points she feels are not discussed enough.
First, you do not need to be a master coder, or know how to code at all. "In my entire 18 year career so far, I have not written one single line of code and I say that because i'm really actually appreciative of that because it's not something that is my main interest." (6:27) She picked up some HTML and CSS along the way, and stresses that people who love code can thrive as QA or automation engineers. Teams need both.
Second, you do not need certifications. She acknowledges there are many online QA certifications available, but she has never held one and has still been very successful. If they interest you, go for them, but they are not a requirement.
Third, you do not need a technical background or degree. "The third point I like to make is that you don't need a highly technical background or degree, a lot of people think a tech career requires a tech degree and i'm here to say no it doesn't." (8:05) Her own QA colleagues have held degrees in marketing, political science and journalism.
As practical starting points, she suggests software support or software training, as she did, or going straight into a junior software quality role. "I would say that if you have a passion for problem solving being creative thinking outside the box finding those strange bugs and making products great that's enough to start your learning of QA." (8:49)
She closes with a slide that mirrors her first: after more than 18 years in tech, she is now surrounded by many more women who share her passion for QA.
Watch the talk
Becoming a QA Analyst in the tech world: What being a QA Analyst is really about!, Rebecca Becker, 10 minutes: https://www.womentech.net/video/becoming-qa-analyst-in-tech-world-what-being-qa-analyst-really-about-rebecca-becker
About the speaker
Rebecca Becker is a QA Manager at Vox Media, working fully remotely, and has worked in the tech industry in various roles for 18 years. She has a passion for quality assurance and a drive to deliver the best possible products, and she loves to teach and mentor others.
Questions this talk answers
- Do you need to know how to code to work in QA?
- Are QA certifications required to get a job in quality assurance?
- Do you need a technical degree to break into QA?
- Will automation replace manual testing?
- How can someone get started in QA?
Drafted with AI from the talk transcript. Editor review pending.