Tell Me About Yourself and Why QA

Why the opening questions matter

The interviewer isn’t really asking for your biography. They’re checking:

• Can you communicate clearly and briefly? Testers explain problems all day, to developers, product owners and sometimes customers.
• Do you know what the job is? “I like computers” suggests you don’t.
• Is your move into QA a real choice? Especially for career changers.
• What should I ask next? Your pitch gives them hooks. A good one leads to questions you’re ready for.

“Tell me about yourself”

The structure: present, past, future

Then stop. Silence after a good answer is fine. The interviewer will pick a thread.

“Why do you want to work in QA?”

What they’re checking: that you understand what testers do and chose it on purpose, not as “an easy way into IT”.

A strong answer has three parts:

1. A true moment or pattern that drew you to testing: a bug you found, a process you fixed, a product that frustrated you.
2. What you enjoy about the work itself: investigating, thinking like a user, finding the cause, making things reliable.
3. What you’ve done about it: the course, the practice project, the open-source issue you filed.

Model answer on the Interview Prep page: Why do you want to be a tester?

“Why our company?”

What they’re checking: that you applied to them, not to every ad on the board.

Prepare in 30 minutes:

• Use their product. Install the app or use the website for 15 minutes like a customer. Note one or two things you liked and, carefully, one question.
• Read the job ad again for clues about how they work: “testers embedded in squads”, “release every week”, “mobile-first”.
• Look at their careers page, engineering blog or LinkedIn posts for values, team size and tech.
• Check app store reviews. They show what real users love and complain about. Mention them tactfully, if at all.

Template:

“I tried your [app/site] before this call. I liked [specific thing], and as a tester I noticed [respectful observation or question]. I’m also interested in [something about how they work, from the ad or blog], because [why it fits you].”

“What are your salary expectations?”

This question makes most people nervous, mostly because they haven’t prepared for it. Prepare, and it becomes a normal part of the conversation.

Step 1: research a range before any call

Salaries for junior testers vary hugely by country, city, company size, industry and remote policy, so there is no single right number, and we won’t give one here. Instead, build your own range from several sources:

• Job ads with published salary ranges. Some countries and US states require employers to share a pay range in the job ad or before the interview; where that applies, it’s your best source.
• Salary surveys and comparison sites for your country, and official statistics where they exist.
• People: testers in local meetups or online communities, friends in IT, and recruiters, who usually know the market well.

Write down a realistic range for a junior role, decide the lowest number you’d accept, and know whether you’re talking gross or net, monthly or yearly, as is usual where you live.

Step 2: early in the process, ask for their range first

In a first recruiter call, it’s polite and common to ask for their range before you give a number:

“I’d like to understand the role a bit better first. Could you share the range you’ve budgeted for this position?”

Many recruiters will tell you. If the range fits, say so: “That range works for me, depending on the full package.”

Step 3: if they insist, give your researched range

“Based on what I’ve seen for junior QA roles in [city/country], I’m looking at something between [X] and [Y], depending on the full package and the growth opportunities.”

A range with your realistic target near its lower end is common practice. Don’t name a number far above the market for juniors, and don’t undersell yourself out of nervousness either.

Step 4: be honest

• Never invent a current salary or a competing offer. It can be checked, and it destroys trust.
• In some places, employers aren’t allowed to ask about your salary history. You can still choose to share it or politely decline: “I’d rather focus on what’s fair for this role.”
• If an offer comes in lower than your research suggests, you can ask once, politely, with reasons. See the offer stage in How QA Hiring Works.

Model answer: What are your salary expectations?

“You don’t have any experience”

Sometimes it’s a question, sometimes a statement, sometimes a test of how you react. Either way: don’t apologize, don’t argue, show evidence.

A four-part answer:

1. Agree honestly. “That’s right, I haven’t worked as a tester yet.”
2. Reframe with real work. “But I’ve done the work of testing on a practice project: I planned it, wrote test cases, filed bug reports and wrote a release recommendation. I can show you.”
3. Bring transferable experience. “And in five years of support I reproduced customer problems and wrote tickets developers could act on every day.”
4. Show you learn fast. “I went from zero to that project in six months while working full-time, and I’d bring the same energy to learning your product.”

Model answer: Why should we hire you without experience?

Fill-in templates

Tell me about yourself

PRESENT: I'm a <current role or situation>, and for the last <time> I've been
<what you've done toward QA: course, practice project, open-source bugs>.

PAST: Before that / in my current job, I <tester-like task you did often>.
For example, <one short concrete story with a result>.

FUTURE: Now I'm looking for <type of QA role>. <Company> appeals to me because
<specific reason>, and I'd bring <your strength>.

Why QA?

I realized I enjoy <investigating / getting details right / thinking like the user>
when <true moment>. Testing is exactly that, for software. So I <what you did about it>,
and the part I enjoy most is <specific activity>.

Why our company?

I used <product> before this call and liked <specific thing>. I also noticed
<question or observation, tactfully>. And I like that your team <how they work>,
because <why it fits you>.

Salary expectations

Early: "Could you share the range budgeted for this role?"
If pressed: "For junior QA roles in <place>, I'm looking at <X> to <Y>,
depending on the full package and growth opportunities."

No experience

That's right, I haven't worked as a tester yet. But I <practice project + deliverables>,
and in <past job> I <transferable skill with example>. I learned all this in <time>
while <circumstance>, and I'd love to show you <portfolio piece>.