The first kind of questions: self-introduction (psychological first cause effect tells us that first impression is very important). The most important thing about introducing yourself is to leave a good first impression on the interviewer. To put it more bluntly, it is to make the interviewer comfortable. But I found that many people simply introduced the past experience, in fact, on the one hand, the past experience did not make people find the advantages well. Actually, an interview is like a blind date. It doesn't matter what you want to say, what matters is what people want to hear. A better self-introduction routine is like this: "Hello, my name is XXX, and I am very glad to get this interview opportunity. I came for an interview today to prove that I am the most suitable candidate. On the other hand, combined with my past work and study experience, I am confident that I can meet the recognition of our company. Next, do you think I should continue to introduce the projects I have done, or ask questions you care about? "
The second kind of problem: project introduction (project experience directly determines whether a person is competent for a certain job, and enterprises value a person's thinking and specific ability to solve problems). The most important idea of project introduction is that the whole should follow the part. When introducing the whole, there should be quantitative data (from the five dimensions of project measurement: scale, including project code scale, demand scale, use case scale, workload, schedule, quality and cost), then roles and responsibilities, then the characteristics of the project, such as doing the best, encountering the greatest difficulties, the worst case, and finally the experience.
The third kind of problems: knowledge about databases. The most basic requirements are database records (insert, delete, update and select), table structure (create, delete, change and describe), stored procedures and triggers.
The fourth kind of problems: related to linux operating system. The basic goal is to be familiar with 50 common commands, such as find command (-name, -type, -perm, -user, -group, -ctime, -atime) and so on. And be familiar with vi and linux to build a test environment. For example, lighting environment construction.
The fifth kind of problems: knowledge related to defects. The most basic is the process of defect tracking (the basic elements of the process), the overall process, it is best to draw it on paper for the interviewer (especially for male interviewers, it is very important to write it clearly from the perspective of male lust), the attributes of the defect list, at least 20 attributes, the meaning of each attribute, how to describe the defect list, and the 5C principle of defect list description, such as the completeness of defect reproduction steps. How to describe a Bug list that you think is the most classic?
The sixth problem: use case correlation. The basics include the format elements of use cases, the engineering methodology of use case design, the requirements of each method (background, operation steps, advantages and disadvantages, scope of application, and how to cooperate with other use case methods), and how to use test cases to design engineering methods in projects. How to evaluate and review test cases, and from what dimensions? What knowledge structure is needed to design test cases, such as technology, business, methods, etc.
Seventh question: software testing process. Process of relevant specifications and standards for system testing: be familiar with products/projects, requirements review, test requirements, test plans, test schemes, test cases, pretests, first round formal tests, second round regression tests, third round tests, test reports, test summaries and test guides.
The eighth problem: network association. The most basic network knowledge, such as TCP/IP protocol.
Question 9: Testing tools. It includes three categories. The first category is performance testing tools, automated testing tools and test management tools. The minimum requirement is familiarity with the use of tools.
Question 10: Give you a software, such as QQ, QQ. How do you test it? The basic idea of this kind of problem is to solve it macroscopically from the perspectives of software quality model, testing tools, testing methods, testing process and exploratory testing, and then explain in detail how to design use cases.
Question 11: What abilities and qualities should an excellent/excellent software testing engineer possess? Qualities include communication skills, five-minded engineers, and the pursuit of perfection.
The twelfth question, the last question, the interviewer will usually ask you what else you want to ask or know. Generally speaking, the most important thing is to leave a good recency effect, just like leaving a good last impression on a blind date. The basic idea should be divided into three situations. First of all, if the interviewer is satisfied with you and feels good about himself, thank him first, and then ask questions on his own initiative. For example, thank you very much for giving me this opportunity, but I still want to ask, if I have another interview, I want to know when. In the second case, the interviewer feels exactly like himself and feels like a chicken rib. At this time, it is very important to say or not. The basic routine is, thank you very much for giving me this opportunity. Frankly speaking, I am not very satisfied with my interview performance today. I can do better, but if I still want this opportunity, can you give me some advice? The third situation is that the interview is bad. In this case, few people will say thank you, but it just reflects a person's demeanor. The basic idea is, anyway, thank you for giving me the opportunity to realize my own shortcomings. Frankly speaking, I am still far from the requirements of this position, but I still want to know if you can give me some specific suggestions if I want to come to our company for an interview in the future.
To sum up, the interview is a blind date process. The success or failure of blind date depends on many factors, but good and sufficient preparation can make us face the pressure and challenge more calmly and positively, instead of simply turning ourselves into a supermarket.