Before you can sell yourself to a hiring manager, you need to understand what you're selling. That sounds obvious — and yet most job seekers skip this step entirely, jumping straight to job boards and cover letters before they've answered the most fundamental question: What do I actually want?
The answer isn't "a job in tech." The answer is a specific combination of the work you're good at, the work you enjoy, and the values you want your career to reflect.
Learning Objectives
By the end of this lesson you will be able to:
- Use a structured audit to identify your professional strengths, interests, and values
- Distinguish the key differences between a QA Tester and Business Analyst career path
- Recognise the internal signals that point toward one role over the other
- Explain why self-knowledge is a competitive advantage in the job market
The Self-Audit: Three Questions Worth Sitting With
Most career advice skips the most important part: the quiet work of actually knowing yourself. Before anything else, answer these three questions as honestly as you can.
1. What Are You Good At?
This isn't about modesty. Think about skills others have recognised in you — not just technical skills, but ways of thinking and working. Do people come to you to find problems? To explain complex things simply? To make sure nothing slips through the cracks?
Write down five skills you've used in any context — school, work, projects, hobbies — where you felt genuinely competent. Not just "okay," but competent.
2. What Gives You Energy?
There's a difference between work you can do and work that leaves you feeling satisfied rather than drained. Think about the last time a task felt engaging rather than effortful.
Was it investigating why something wasn't working? Or was it talking to stakeholders and turning messy requirements into clear documentation? Both are valuable — and they point in very different directions.
3. What Do You Value in Work?
Some people want technical depth. Others want human connection and stakeholder relationships. Some want the satisfaction of finding the bug; others want the challenge of defining what "done" means before a line of code is written.
Knowing your values keeps you from taking a role that looks good on paper but drains you in practice.
QA vs BA: Which Trail Is Yours?
Once you have a clearer sense of your strengths and energies, you can map them to the two roles this course focuses on.
The QA Tester
A QA Tester is the person who finds what's wrong before the customer does. The core of the role is systematic thinking: building test cases, running them with discipline, reporting defects clearly, and advocating for quality when schedule pressure pushes the other way.
You might be wired for QA if you:
- Enjoy finding edge cases and thinking about what could go wrong
- Have a natural eye for detail and inconsistency
- Feel satisfaction when a system behaves exactly as it should — and frustration when it doesn't
- Are comfortable working with (and sometimes pushing back on) developers
The Business Analyst
A Business Analyst is the bridge between what a business needs and what a development team builds. The core of the role is communication: eliciting requirements, documenting them clearly, challenging ambiguity, and ensuring everyone shares the same understanding of what's being built.
You might be wired for BA if you:
- Enjoy conversations more than code review
- Like turning vague ideas into structured requirements
- Feel satisfaction when stakeholders leave a meeting understanding each other
- Are comfortable with ambiguity and good at reducing it
The honest test: When a feature behaves unexpectedly, is your first instinct to write a bug report — or to ask "did we even define this correctly?" The first points to QA. The second points to BA. Neither is wrong. Both are valuable.
Self-Knowledge as a Competitive Advantage
Candidates who know themselves well answer interview questions differently. Instead of "I'm hardworking and detail-oriented" (which every candidate says), they say: "I get genuine satisfaction from finding defects before they reach users — I've never been able to let a broken flow sit without investigating it."
That specificity is memorable. It signals self-awareness. And self-awareness in a QA or BA candidate tells a hiring manager that this person will know when to escalate, when to dig deeper, and when to ask for clarity — all things that make teams work better.
Pro Tips
Don't rush this step. Spend 20 minutes with the three questions before you move on. The clarity you gain here will make every other part of this course more useful.
Talk to people in the roles you're considering. LinkedIn makes this easier than ever. A 20-minute informational interview with someone doing the job tells you more than any job description.
Your direction can change. Choosing QA now doesn't mean you're locked in forever. Many QA professionals move into BA, development, or management. But starting with a clear direction beats wandering.
Summary
Career direction starts with self-knowledge, not job boards. The three questions — what you're good at, what gives you energy, what you value — form the foundation of every good career decision. QA and BA are both rewarding paths; the right one is the one that matches how you naturally think and what satisfies you professionally. Know that, and you'll stand out from the candidates who simply applied because the listing looked interesting.