Here is a summary of my interviews this year:
Let me talk about my personal situation first. I usually have a second degree in computer science. I know python, script writing, selenium, and performance. Taking advantage of the job-hopping season of gold, silver and silver, I had already passed the technical aspects of the interview for the ByteDance test position. I thought it would be a steady ending. Then I communicated with the final interviewer, and the interviewer came up with a salary figure. I accepted the offer and synchronized the number with HR. After the 4 interviews, I felt uneasy. I waited for two days without any news. I asked the HR specialist who sent me the interview email and told me that I had passed the interview in the system and asked me to wait. I was quite happy, so I turned down one of the other two good offers, and did not continue to interview with other companies during the period. As a result, I waited for another two days and still heard nothing.
In order to live a safe life, I asked again, and this time I was told that the interviewer from the third interview did not write a review for me, and the HR specialist did not know what was going on and went to verify it for me.
As soon as I hung up the phone, I knew it was 100% cool.
Sure enough, I got a phone call at six o'clock and said that I was not a match, but expressed high recognition of my abilities and other nonsense. Finally, he said that he would help me see if there are any suitable positions in other positions, and if so, he would contact me again. Basically, it was over here. I thought it must be because my skills were not up to par, I lacked experience in automation, and I had encountered obstacles in applying for a job in a large factory, so I decided to calm down and practice in seclusion for more than a month.
Life has to go on, so let me briefly tell you about the interview. I have been working for about 5 years. You can refer to some of the questions asked during the interview.
Test interview topic 1: Agile development and testing
The following are some of my personal experiences:
Traditional development models: V model, waterfall model. Traditional development models tend to follow the rules, starting from requirements, outline design, detailed design, development, unit testing, integration testing, system testing, acceptance testing, and online release. The entire cycle often takes half a year to a year. Due to the long cycle, the product is in the development process. There will be changes in demand, and the traditional model cannot adapt to changes in demand. In order to solve this problem, the agile model currently appears.
Agile is divided into agile development and agile testing. Its characteristics and characteristics are:
1. Test-driven development and behavior-driven testing
Test-driven development means that unit tests are written first and then the development code is written. When the unit tests run through, the code development is completed.
Behavior-driven testing is done by directly writing user stories, such as the Cucumber framework. It is very simple to say, that is, writing the steps corresponding to the scenario for each test case in Excel, and each step corresponds to a keyword (action function), and then As long as the userstory/test scenario is supplemented, one test case after another can be expanded. Of course, the functions at the beginning need to be written and implemented one by one.
2. Take small steps and embrace change
Agile thinking divides a product into multiple stages, each stage lasts about 2 to 4 weeks. During these 2 to 4 weeks, the requirements set are clear and excessive changes are not accepted. This ensures the realization of clear requirements. We embrace changes in terms of product progress and demand for the next cycle.
3. Don’t force too much on documentation and emphasize communication between people.
However, if you insist on documentation, it does not mean that you reject documentation. It is best to have documentation. However, due to time reasons, not writing documentation is allowed.
Emphasis is placed on communication between people. Development and testers are in a small space (round table, office environment without baffles), and can communicate face-to-face if they have any problems.
4. Stand-up meeting (use sticky notes to show progress)
Daily stand-up meetings are held to report progress on development and testing, and to talk out and discuss any difficulties encountered. It is also easy for everyone to understand the progress of the project.
5. Pair Programming
The same piece of code is written by two people, one person writes the code and the other reviews or exchanges it. This method is a method used by Google
6. Continuous integration
Emphasizing rapid construction and rapid testing, you can use the continuous integration tool Jenkins. The benefits are: quickly discovering problems, quickly locating problems, saving troubleshooting time and costs, etc.
7. Automated testing
Mostly unit tests
8. Refactoring
Because in agile development, speed is emphasized, and many codes are not written well enough. The code may need to be rewritten later. At this time, unit testing is particularly important. Unit testing can verify whether the code rewrite is normal.
Test interview topic 2: How not to miss the test?
The topic of not missing tests is a false proposition in itself. Microsoft's products are patched every day, including Google and Facebook. There is no way for testers to ensure that no tests are missed, but they can try to avoid missing tests as much as possible, and the reasons for missing tests are different every time.
No missing tests means that the software has no bugs. This is a matter for the entire team. The team is responsible for the quality of the entire product. Testing is only a small link in quality management.
How to build a good product quality through the team is a good topic.
Product testing layering and effects: unit testing > interface testing > UI testing
Unit testing: Development requires unit testing and code review to ensure the robustness of the product.
Interface testing: The changes in the interface layer are relatively small, which is very suitable for comprehensive automation and rapid product regression; --- testers
UI testing: UI layer automated testing + exploratory testing; the UI layer has changed a lot, and although everyone wants to automate it, the effect is not good; --- tester
Based on the existing situation, improve product quality:
1. Sort out the R&D process and let everyone perform their duties.
2. From the beginning of the requirements, testing should be involved and understand every detail. Design detailed test cases based on product requirements documents and product design documents (outline design, detailed design), and let product personnel and developers participate in the review together. Let the team work to supplement the test cases, which can greatly reduce the possibility of missed tests.
3. The application of bug prevention, testing framework, and exploratory testing in test case design can reduce the occurrence of missed tests.
4. Let the relevant personnel of the project do some random tests to test the system from different angles.
5. Work together.
Test Interview Topic 3: What are your personal short-term and long-term goals?
Someone might answer something like this: "My goal is to make sure I don't get left behind, and I believe it's important to face reality. I read somewhere that we are a further generation behind in American history than the previous generation. That makes me I'm worried, so my goal is to make sure I don't fall behind. This may sound a little pessimistic, but I'm a realist and I believe it's important to face reality."
Such an answer can only highlight that you are a person who follows the crowd and has no personality or characteristics of your own.
reasonable answer
My personal strategy, both in the long and short term, is to evaluate where I am relative to my current goals and then modify my plans accordingly. For example, every five years I create a personal plan that contains an overall goal and a series of short-term goals. Every 6 months I review my progress and make necessary changes. Obviously, my current plan is to make a career change, which means finding a more satisfying job. In addition to this, I have achieved my recent personal goals.
Goals that are realistic and evidence that you are working towards or have achieved them.
Test interview topic 4: Given a testing team, how would you manage it?
This is a topic of test team management
1. Custodian
a. Recruit new people and find suitable people. New people need on-boarding training. Let new people quickly integrate into the team and get involved with development and testing.
b. Communicate more effectively with team members, understand each person’s real demands, and strike a management balance based on the demands and the company’s requirements.
c. Set KPIs, provide reasonable incentives, and have clear rewards and punishments.
d. Team building to enhance understanding.
2. Director
a. Do a good job in daily project management, monitor all aspects of the project, and ensure the company's project development and quality requirements.
a1. Team members often take on different test projects under the name of the test group, and need to grasp the overall progress of the project, for example: whether the requirements are fully understood, whether the test cases are designed sufficiently, and whether there are any risks during the project execution.
b. Arrange everyone’s work reasonably according to each person’s demands and characteristics (those who like challenges are given some challenging work; those who don’t like challenges are given some daily tasks).
There is no real right or wrong in management. If everyone can work happily and achieve a balance, it will be considered a success.
Test interview topic 5: Thank you for every interview opportunity
Every interview is a spiritual practice! They are all opportunities to understand your shortcomings, discover your shortcomings, re-understand yourself, and improve! Every interview is another fate. We can quietly listen to each other's stories and suggestions, think about and compare our own lives, constantly revise, and learn from each other! Self-motivation!
The ups and downs of job hunting, the various situations of life, and knowing whether you are good or bad! I also reorganized the testing industry and revised my personal development goals. I hope to share my experiences, insights, methods and methods with everyone, help each other, encourage each other, and get through the temporary mid-life crisis together!
What should you pay attention to during the interview process?
1. Answer the questions at the pace of the interviewer
After so many interviews, I found that speaking speed is very important. Since I usually speak very fast, during the interview process, I generally speak faster . However, some interviewers prefer to speak slowly and slowly. Something between the lines will also reflect a person's personality. When an interview lasts for more than 10 minutes, you can " adjust " your speaking speed based on the interviewer's feedback . Ability is important, but the interview result is still It's all in the hands of the interviewer, right? Even if you pass the subsequent interview and it's time to talk about an offer, the previous interviewer's evaluation of you is still very important.
2. Let the interviewer ask questions at his or her own pace.
This is also a very important point. Although your interview may last 4 to 5 rounds, there is still no way to completely dig you out. When the interviewer asks a certain question, if you have a deeper understanding of a certain question, Then you " can throw out more knowledge points for the interviewer to ask questions "
For example, when you answer the question of lock upgrade, you can expand to the lock flag yourself. Through the lock flag, you can also expand the memory layout of the object. Through the memory layout, you can also expand to the storage size of the memory layout of different operating systems.
By presenting in-depth knowledge points one by one and asking the interviewer's questions, you can let the interviewer find out that you are a person who usually studies in depth (be careful every day)
3. Avoid the important and take the light and escape quickly
This is also very important. If you encounter a question that you don't know, pass it immediately without hesitation, because the entire interview time is fixed. It is not a wise choice to stay too long on a question that you don't know. You must amplify your own strengths so that the interviewer’s questions can hit your knowledge system as accurately as possible.
4. Learn to guess
Learn to guess, how to understand this, let me give you another example
For example, if the interviewer asks you a question, what should you do if you don’t know it?
At this time, you have to learn to guess. You can "tell the interviewer other content related to the question " and what questions there are, and then guess how it is answered based on the characteristics. In this place, " even if the answer is wrong It doesn’t matter ”, because “ the interview is never to test you, but to see what you know and whether your own characteristics are suitable for this position. ”
5. Don’t be nervous, relax
In testing positions, communication skills are very, very, very important.
How can I not be nervous? " Practice more, speak more ", there is no shortcut
6. Interview small companies first
Put your favorite company at the back, " first interview with a small company to learn literacy skills ", and find out how to get started, " or ask friends with better skills around you to help you do more mock interviews ", and try to broaden or deepen your knowledge system. Even though I haven’t had an interview for a long time, I still need to practice my communication. Fortunately, I can perform normally or exceptionally in subsequent interviews~
After the interview
1. Record the questions asked in the interview and written test questions
Record all the questions encountered in the interview, review and summarize the technical points examined by each question. These questions will also be encountered in subsequent interviews. Furthermore, the questions asked in the interview are generally encountered. If If you don't answer well, he may think that you haven't encountered it or have insufficient experience. This is a big pitfall.
2. Summarize your own performance and find room for optimization.
Put yourself in their shoes. If you are the interviewer, evaluate your answers to see if there is room for improvement in language expression and logical organization.
3. Follow up the interview progress in a timely manner
No matter you are interested in someone or someone you are not interested in, you should take the initiative to find out the progress. Some are recruited by headhunters, and they will follow up on your interview progress. After the interview, you can tell them about your experience and results, and they can be the first to do so. Time to obtain feedback from the interviewer and follow up on the follow-up process.
Content screenshot [with answers]
1.Basic questions on software testing (250 questions)
2.Linux (55 questions)
3.MySQL (80 questions)
4.Web test (10 questions)
5. Interface test (36 questions)
6.APP test (12 questions)
7.Python (100 questions)
8.Selenium (40 questions)
9.LordRunner related (80 questions)
10. Computer Network (26 questions)
11. Human Resources (55 questions)
How to obtain documents:
This document should be the most comprehensive and complete preparation warehouse for friends who want to engage in [software testing]. This warehouse has also accompanied me through the most difficult journey. I hope it can also help you! All of the above can be shared, click on the small card below to join the group and get it for free.