Recently, I have seen a lot of software testers who need to re-apply for jobs due to company layoffs. They generally have 4 years or more of work experience. But job search results are often not ideal.
In the process of talking with some software testing job applicants, I found that many people have unclear work ideas, poor skills, and no habit of continuous learning, but they have high expectations for the future.
Due to the longer working years, they generally believe that wages should continue to increase with the increase in working years. But the fact is: your salary is not proportional to your working years, but proportional to your irreplaceability.
a story
A test friend of mine entered a company to do software testing after graduating from university.
Six years ago, when he first joined the company, the company was very profitable. He is very clever, and the seniors of the project team are willing to give him advice, so he gets started quickly.
In the second year of working, he is already familiar with the business of his project team, and he can even make some suggestions for improvement. In increasingly familiar environments, his skills have been greatly improved. In the third year of working, he jumped to join a large Internet company. His original position as a junior developer became a Team Leader, and his salary also increased a lot.
Last fall, the company adjusted its organizational structure due to poor efficiency. The boss personally talked to him and told him that the company's business structure adjustment only retained one core business line, and the original business was temporarily suspended. There is no way, he accepted the company's resignation compensation plan.
When he came out to look for a job, he found that many old testers like him with many years of rich work experience had achieved the position of project team leader. With his current strength, the job he can match is nothing more than an intermediate development engineer. But for this kind of work, many companies require the age to be under 30 years old. After repeated setbacks in interviews, he was demoted and lowered his salary to enter a small company.
some emotion
I can't help but sigh: the best way to measure the value of your experience is whether it can be replaced.
In a rapidly changing workplace, your core competitiveness depends on how high the cost of replacing you is.
You can try asking yourself a question:
What have I gained in my past career? What is the product of my work? What proof do I have?
If it's just a fading professional experience without any valuable experience, then you don't have any valuable abilities. You are easily replaced by others, and you have little bargaining power with your boss.
this is the truth.
Why are some programmers who have only worked for one or two years but have more than three years of ability?
Keep a Beginner's Mindset on the Job
Learn to conduct a self-reflection at each stage
Customize long-term plans and learn to split goals into small goals to achieve individually
As far as the programmer industry is concerned, I personally think that the core competitiveness of this industry is not how many lines of code you have written, nor how familiar you are with a product, but your understanding of this industry. The real core technology is the key. The ground work is to type some repetitive codes, build wheels, and there is not much difference between working for three years and working for one year.
Some people reject new technologies. The so-called working years are very long, but it takes five years of work experience for one year. It is necessary to understand new technologies in order to better apply and transform them.
No wonder some people joked:
"I have three years of work experience" "No, you just used one year of work experience for three years!"
How should programmers who have just entered the workplace learn to grow quickly?
I think that in addition to improving my own coding skills, my design insight, fast reading and deep thinking skills should also not be ignored. My road to automated testing is inseparable from the plan at each stage along the way, because I like planning and collecting summaries, so my friends and I spent a period of time organizing and writing the following "Learning Route for Automated Test Engineers", Hope that will bring you help and direction.
Station B tutorial: Python automated testing: teach you how to practice these 60 practical projects
[Automated testing improvement route]
1. Essential Python programming content for automated testing
2. Basic content of Web UI automated testing
3. Web UI automated testing content
4. Basic content of APP UI automation testing
5. Practical content of APP UI automation testing
6. Basic content of API interface automated testing
7. Practical content of API interface automated testing
8. CI/CD continuous integration special technology
9. Practical technology of automated testing framework
The above is a technical roadmap for automated test engineers that I compiled. I hope everyone can benefit a lot from this growth process. Improve the testing technology in an all-round way and establish a set of own technical system. Helping everyone to continuously learn and optimize the technology stack, follow up with advanced and mainstream testing technology, bring you not only the improvement of technology and salary, but also change the status and mentality of testers in the field of IT technology, and improve Test the technical depth of the industry.
Finally, I would like to thank everyone who has read my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it:
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey, and I hope it can help you too!
Information acquisition method:
