What is the level of interviewing 20k test engineers? Knowing the enemy and knowing yourself can win a hundred battles...

Contents: Guide

foreword

What do you need to know about interview software testing?

As the saying goes: Know the enemy and know yourself, and you will never be imperiled in a hundred battles. So for interview software testing, what aspects we need to know is the magic weapon for us to win.

1. The importance of a resume

First of all, as a test taker, you should be very familiar with any technical points mentioned on your resume, because this is the first choice for interviewers to ask targeted questions. Even if you can't explain its principles very clearly, at the application level, you should at least be able to clearly state the use in work, and you can succinctly describe the application in your own project.

For example, in the project I participated in, what kind of test framework was adopted, and if it was automated, what platform was it based on, what tools were there, and what functions were completed.

In other words, you, as an applicant, should be able to talk about all the projects written in your resume, instead of just writing some of them when you see hot spots. Although such a resume looks good, it is actually full of loopholes and cannot withstand scrutiny and questioning.

Similarly, during the self-introduction stage, the interviewer will also focus on screening and asking questions about the interviewer's expression. The preparation and attention points for this section of self-introduction are similar or even the same as preparing a resume.

2. Technical requirements for testing positions

Secondly, before the interview, you should have some understanding of the position you are applying for. According to the responsibilities and requirements of the position, make focused preparations, including resumes and interviews. The content of software testing is not just as simple as testing software, but you should have an understanding of all related aspects.

If it is a manual test, then test case design and test ideas are very common points of investigation. If it is automated testing, then the mastery of automated testing tools and even the test of some code capabilities is a must.

In the current software industry, agile and even DevOps have become industry standards, so it is necessary to have a clear understanding and mastery of the relevant background knowledge under this architecture. Talking about agile topics from a testing perspective will give you a lot of points.

3. Choose a suitable position

The interview is not a selective examination, not a merit-based admission, but a selection of candidates suitable for the current position. Therefore, if you are a junior test engineer, it is understandable that it is difficult to successfully apply for a test expert.

Then, conversely, when a senior test engineer with rich experience applies for the position of junior and intermediate test engineer, the possibility of success is not great.

So the interview is not an occasion where the more powerful you are, the more you can take it all. In any case, fit is the most important thing.

What is the difference in skill requirements between junior VS intermediate and senior test engineers?

From the point of view of the test engineers themselves, junior and intermediate and senior test engineers may focus more on the gap in test ability and experience.

In fact, in enterprises, for junior test engineers, it is often more about arranging test case execution, or relatively basic and simple functional testing. Those who have the ability to design use cases and test plans can advance to intermediate test engineers. With automated testing capabilities, an in-depth understanding of testing theory, and own insights into testing work, one can be classified as a senior testing engineer.

From the perspective of the above division criteria, in addition to the coverage of testing skills and testing fields, whether the testing work can be analyzed and mastered from a theoretical perspective is a watershed for distinguishing junior, middle and senior test engineers.

We can understand that the difference between a craftsman and a master is simply the difference from Executer to Designer. Simple execution is the foundation of the work, and the top-level design involving testing theory and testing ideas is the superstructure of the entire testing work.

This can sort out a relatively clear path:
①Starting from junior personnel, the execution of test cases will be used as the baseline of the entire work throughout. Perhaps for junior test engineers, whether it is manual testing or automated testing, the ability to execute test cases is a must.

②Beginning as an intermediate test engineer, with the understanding of the work and the accumulation of his own experience, he has a certain design and planning ability, which is a sign that the intermediate test is different from the primary test, and the work content at this time will also be included Certain design and planning.

③If you want to advance to a senior test engineer, in addition to a comprehensive grasp of skills, you must also have a grasp of the top-level test architecture, and the basis of this mastery is an in-depth understanding and proficiency in test theory and test thinking.

Everyone understands the truth, but many people don't know how to improve technology? How to fight?

The following is the most complete software test engineer learning knowledge architecture system diagram in 2023 that I compiled