QTNA: Do You Need Certifications to Work in Tech?
After delivering my talk at the Techsgiving Summit, I opened the floor for Q&A. One attendee asked: “Do we need certifications to work in tech?”
It’s a question I hear often, so I thought it was time to add it to the QTNA (Questions That Need Answers) section of my digital journal.
So let’s talk about it.
Tech is bigger than IT
First, let’s clear this up: working in tech does not mean you’re working in IT.
IT-specific roles—think cybersecurity, networking, or cloud infrastructure—often require certifications. These act as proof of expertise in areas where precision is critical. But when it comes to product teams—roles like UX Researcher (that’s me), Product Designer, Product Manager, Data Scientist, or Software Engineer—certifications matter less.
We’re building software, solving user and business problems, not configuring networks or firewalls. Yet it’s easy to lump all “tech” roles into the IT bucket.
So, do you need certifications to land a role on a product team? Probably not.
💡 But I think there’s a bigger question underneath this one: How do I show credibility as I navigate my career?
The Real Currency: Critical Thinking
So my answer to the question, every single time: Show you can think critically.
Working on a product team means being a problem solver. It doesn’t matter what your title is—at the end of the day, we’re all solving problems.
As a UX Researcher, I solve problems through research: understanding the user, their needs, and what isn’t working.
A Product Designer might solve problems through prototyping.
A Product Manager tackles problems through prioritization.
💡 The point is: our success comes down to our ability to identify problems, and arrive at thoughtful solutions.
But here’s the tricky part. While we are smart people, we’re not always given opportunities to truly think critically—to step back, challenge assumptions, and explore solutions deeply.
Open-Book Thinking Won’t Get You Far
In college, I used to split my classes into two categories:
1. Classes where the answers were readily available. These felt like open-book tests where you didn’t need to think beyond the text.
2. Classes that forced me to think. The ones where the answers weren’t laid out for you—you had to make connections, form arguments, and challenge ideas.
I’m sparing my professors’ reputations by leaving out the class names… but I’ll just say… go Owls! 🦉
It’s easy to look credible on paper. It’s harder—and far more valuable—to think deeply, test ideas, and sharpen your reasoning.
Just A Little Mental Gymnastics
💡 If you’re thinking — it’s time to level up your critical thinking skills, here’s a weekly practice to incorporate into your routine:
1. Identify a problem. Pick something in a product you use regularly—whether it’s a work tool, or your favorite app. What’s not working?
2. Dig deeper. Why is this a problem? What’s causing it?
3. Brainstorm solutions. What might fix it? Don’t overthink—just start.
4. Challenge yourself. Share your ideas with someone who has a different perspective and invite constructive feedback (they say feedback is a gift).
5. Reflect and refine. Write down your thought process. Spot any biases or gaps in your reasoning.
The goal of this exercise isn’t to find a perfect solution. It’s to practice how you think—and get better at solving problems thoughtfully.
Certifications? Nice to Have. Critical thinking? Non-Negotiable.
〰T.
