I have 4 years of testing experience, 211 undergraduate majoring in computer science, due to layoffs on the Internet, I recently submitted some resumes to bosss to test and develop positions to see the current market situation.
Although everyone is saying that the general environment is not good and there are many unemployed people, I have recently asked for a lot of interviews. Let me talk about my recent experience, hoping to provide value to everyone.
1. There are still a lot of test and development positions around 20K, and you need to understand automation, which is a must-have option
Have a deep understanding of the project as a whole, and after you have a certain code foundation, you can try the test development post. Test development positions are more comprehensive positions. Many companies recruit for testing, but they are actually recruiting for advanced testing. After entering, they rarely ask you to write test tools directly, and more are business testing and writing test scripts. And so on, the core of the market now must be to reflect business value, and there are very few pure writing tools.
2. Now the test is really getting more and more complicated, and senior testers are developing in the direction of the whole stack
Not only must you have basic computer knowledge, but you also need to understand functions, automation, programming, and front-end and back-end technologies. In the current market, the priority is to understand the knowledge of the back-end, and there are relatively few inspections of the front-end knowledge. In the future, I feel that front-end knowledge will be examined. The current test understands the development technology stack. The more popular ones are multi-threading, locks, springboot, redis, kafka, docker, k8s and so on.
3. Compared with my younger self, I started to pay more attention to the company's business direction and my own development direction
I interviewed several companies recruiting big data test development, game test development, hardware, and blockchain, and found that I didn't want to do big data and game testing. From the company's business direction, you can initially judge whether the company is a traditional conservative company or an innovative company, whether it has a future or not.
4. There are 3 interviews a day, which is quite tiring, mainly because of tiredness
Later, it was changed to one session a day to schedule interviews. much better. In fact, the best frequency is 2 games a day, not too tired, nor too slack. After so many interviews, I found that not all test and development posts will inspect algorithms, and only 20% of non-big manufacturers will inspect them. Almost all major factories have to be inspected. But if you do it, you may not pass the interview. It is still necessary to answer well in front, and the algorithm can also be made.
5. Compared with the situation a year ago, the current interviewers will pay more attention to the project
Do you have enough understanding of the project business and technology, and whether what you do can withstand torture. For example, if the project technology uses redis, you will be asked how to test redis, but if you can’t answer, the interviewer will think that the project test is not done well, but redis is used but not tested, the consideration is not comprehensive, and it is numb.
What will be asked about the project?
Many interviewers like to start asking questions from the introduction of business architecture and technical architecture, and gradually evolve. Therefore, when working on a project, it is recommended not to limit yourself to some small modules.
In terms of business, the project has a structure diagram for reference. Read more and understand thoroughly in case you are asked during the interview. The business structure and details of the project are very clear, which is definitely a plus in the interview. As for the technical architecture of the project, you can understand as much as you can. If you don’t understand it, you can go to the more general microservice architecture on the Internet.
During the interview, introduce the project, learn to predict the interviewer's questions, and guide the interviewer.
The difference between interviewing a big factory and interviewing a small company:
Small companies generally have 2 to 3 rounds of interviews, and the test team is relatively small. There is a high probability that one side will be the person in charge of testing, and the other side will be interviewed by the person in charge of development and R&D. Small companies pay more attention to what value you can bring, and they will ask them what they are more concerned about. For example, some small companies lack automated testing, so they will pay more attention to automated testing. Financial companies pay more attention to data and will examine SQL more. There are also some small companies that have basically no construction in the testing area, and would prefer to recruit talents who can help the company build a testing system to improve quality and efficiency.
Big factories usually have 3~4 rounds of technical interviews, one is usually your mentor-level person, the second is usually your direct supervisor, and the third or fourth may be pure management leaders. Interviewers from big factories are usually better at digging out the bright spots of interviewers. Ask until you can't. Many interviewers in small companies do not have enough interview experience, and the interviewers do not know how to ask questions, and some of them are also impatient, which gives the interviewer a bad feeling and sometimes makes the interviewer feel self-doubt. In this case, you don't have to doubt yourself. Naturally, the next interviewer from the next company will understand you.
Junior high school interview preparation?
For junior and intermediate tests, in addition to project preparation and automated testing, it is also necessary to prepare computer network, database, SQL, Linux, and programming language FAQs.
For advanced testing, in addition to preparing projects and automated testing, you also need to think about the testing system, and prepare more for multi-threading, locks, Redis, frameworks, and JVM. Instead, there are fewer stereotyped questions.
Practical case
Optical theory is useless, you have to learn to follow along, and you have to do it yourself, so that you can apply what you have learned to practice. At this time, you can learn from some actual combat cases.
If it is helpful to you, please like and collect it to give the author an encouragement. It is also convenient for you to quickly find it next time.
If you don’t understand, please consult the small card below. The blogger also hopes to learn and progress with like-minded testers
At the right age, choose the right position, and try to give full play to your own advantages.
My road of automated test development is inseparable from the plan of each stage along the way, because I like planning and summarizing,
Test and develop video tutorials, study notes and receive portals! ! !