How to Successfully Jumpstart QA Career?

In a nutshell, this is not the easiest thing to do and not the easiest way to choose in the IT industry. Therefore, everyone should be ready that this profession implies a huge amount of work on oneself, effort, and endless learning.

The expression “It’s easy to get into IT through testing” already stopped being relevant 5 years ago. But with due effort and desire, anything is possible. So, let’s get down to business.

Junior QA: Requirements Today

1. Good knowledge of theory

Where can we go without it? This is the main focus of any technical interview. The goal is to understand how well the applicant is familiar with all concepts in software development and testing in particular. Becoming a QA requires an understanding of the software development lifecycle, knowledge of theory, and basic testing tools.

Basic knowledge of testing theory is the ability to answer the following questions:

• What is testing and why do we need it?
• What types of testing do you know?
• What is a bug? What is bug’s life cycle?
• What documentation is used in the process of testing?

2. Client-server architecture

Usually, this area does not require extensive knowledge. You need at least a general understanding of how modern applications work, what a client and a server are, how they interact with each other. Many articles explain this simply. Just worth reading and remembering.

3. Web services, API, SOAP/Rest

Now, this is more interesting. A modern tester, even a beginner, needs to know what an API is, what is the difference between SOAP and Rest, what JSON and XML are, what request methods are, what HTTP status codes are, and what they mean.

Since almost all projects and applications are related to this topic, knowledge in this area will either be critically important (in most cases), or it will become an opportunity to stand out from other candidates.

4. DB, SQL

Based on my experience, I can say that knowledge about the types of databases, the types of commands, and the ability to write any query on a piece of paper – more than enough.

It is important to remember, it all depends on the project and the company you are interviewing for. Carefully read the requirements for the vacancy and the description of the project to which you want to apply. Looking closely at these things will help you predict the focus of your interview. For example, if this is a mobile application, then you will most likely be asked about the features of testing mobile applications.

Technical Questions at a Tester Interview, or What Should a QA Know and Be Able to Do From the Technical Side? (Most Often)

1. Analysis and clarification of requirements with the customer and/or business analysts
2. Development and writing of test cases
3. Defects (bugs):
4. Search
5. Identification
6. Submission to the bug tracker
7. Rechecking
8. Analysis, etc.
9. Maintaining test documentation
10. Testing the functionality itself

Equally Important Non-Technical Skills

1. Communication skills, ability, and desire to ask questions
2. Attentiveness and perseverance
3. Ability to self-study
4. Responsibility and persistence
5. Ability to defend your point of view and the ability to admit when you were wrong

A day of a tester includes (but is not limited to):

1. Stand-up meetings
2. Writing test cases, testing, documenting errors (depending on the phase of the project)
3. Checking the bug-tracking system for the appearance of fixed errors
4. Study of requirements, their clarification with the customer
5. Active communication with developers
6. Writing test documentation

What Do You Need to Be Prepared For? Why Does the Situation “I Can’t Find a Job” Occur?

1. High level of competition
2. Desire and motivation
3. Many stages of interviews (software requirements specification, technical interview, conversation with a recruiter/HR, etc.)
4. Resilience to “noes” and work on errors
5. Initial compensation level
6. Higher job requirements and self-learning

I wish everyone a successful start in their career!