Implications after analyzing the layoffs of 1,011 programmers

Hello everyone, I'm Casson.

Everyone should be able to clearly feel that the job search environment has not been very good in recent months, but how bad is it? What is the specific situation?

In order to analyze the current situation of programmers' workplace, I conducted a survey on layoffs, and a total of 1011 programmer friends participated.

This article will bring you some inspiration based on the survey results (if you don’t want to see the analysis process, you can skip to the end of the article to see the conclusion).

Welcome to join the human high-quality front-end framework group , with flying

How much are layoffs really?

In terms of job rank , among the respondents, junior engineers have the least percentage of layoffs (possibly because the salary is relatively low and the benefits of layoffs are not large), while experts and above are the most, but the overall difference is not large.

On average, 19% of respondents experienced layoffs.

The size of the company is defined by the number of technical teams in the company. Small companies with only a few technical teams have the most layoffs, while other larger companies have little gap.

It may be because too small enterprises have not run through the logic of business realization, and the boss's ability to resist risks is even worse.

The inspiration for us is that in order to have a stable job, it is not necessary to go to a large factory (after all, the proportion of layoffs is not low), but should try to choose a company with stable business .

Do you think this rate of layoffs is high?

What work do you all do?

Many programmers who do business will feel that the architecture is higher. From the perspective of job rank , with the improvement of rank and ability, there are indeed more and more programmers engaged in architecture work:

From the perspective of the size of the technical team , the first-tier factories (more than 1,000 technical teams) have the highest proportion of programmers engaged in architecture work, but the overall difference is not large.

On average, about 17% of programmers work in architecture.

The inspiration for us is that when applying for an architecture position, you can inquire about the proportion of programmers who are engaged in architecture positions in the company. If it is higher than 17%, there may not be much room for you to use your skills .

At the same time, from the above two analyses, architecture work is both difficult (the higher the rank, the higher the proportion of architecture work), and the scarcity (on average, only 17% of the company's programmers are engaged in architecture work).

It's not hard to understand that programmers value architecture work -- because it's harder, and less so.

If the business does not make money, the business line will be cut off, and the programmers who do the business will be fired. This logic is well understood. The architecture is generally universal.

So, in the face of the wave of layoffs, does architecture really have a higher anti-risk ability than business ?

Architecture or business?

Looking at the proportion of layoffs in architecture work by job rank , we will find that as the rank goes up, the proportion of layoffs in architecture work increases significantly.

For programmers who are determined to develop long-term in terms of architecture, they definitely do not want to be at a higher and higher risk of being fired as their rank increases.

Correspondingly, as the rank increases, the proportion of programmers who do business will be gradually reduced.

Although the proportion of layoffs in architecture is lower than in business at different ranks, as mentioned above, only 17% of the company's programmers are engaged in architecture work on average. Obviously there are far more job opportunities in business than in architecture .

The inspiration for us is that during the economic downturn, when programmers plan their career development, they should try their best to develop in the field that is close to the money (doing business) .

Dachang is a life-saving straw?

Is it possible to reduce the risk of being laid off by going to the big factory as much as possible?

Looking at the proportion of layoffs in terms of structure and business work according to the size of the company, the risk of layoffs in companies with only a few technical teams is indeed the greatest. However, the proportion of layoffs in first-tier factories (with more than 1,000 technical teams) is also very high.

The risk is relatively small, and it is a company with dozens of technical teams . Such companies may have their own stable businesses and do not expand blindly, so the scale of layoffs is relatively small.

There is also an interesting situation from the table - as the company becomes larger, the proportion of architects who are laid off increases significantly.

Everyone wants to go to the big factory to do the structure, but the big factory structure is the most laid off. Does this prove from the side that the tall wheels made by many big manufacturers are of little value?

Do you think so too?

Many of the above analysis results are not friendly to architecture students (especially large factories). So, is this what everyone heard?

I counted what you heard about what the fired programmers in your company do , and the proportion of them engaged in architecture positions is as follows:

It can be seen that not only the data of the parties involved in the investigation are summarized and displayed - don't go to the big factory to do the structure .

This view is also confirmed by the summary of the company's situation that everyone has heard about .

So everyone realizes that it may not be a good choice to do architecture in a big factory ? The following is the proportion of programmers who have not been laid off and think they have good development prospects who are engaged in business and architecture :

Regardless of whether this perception is correct (feeling good prospects for yourself). From the perspective of proportion alone, whether it is a small factory or a large factory, the cognitive proportion of students who do business tends to be the same.

And the classmates who do the structure of the big factory obviously have extremely high expectations for their own prospects (I don’t know if they know, they also have the highest percentage of layoffs?)

Why is there such a big gap between the expectations and the actual situation for the students who are doing the architecture in the big factory ? What grade of students would think that the proportion of corporate structure positions being laid off is more?

The following is divided by job rank , who has heard that there are many layoffs in the company's structure positions:

No junior engineer felt that the company's architecture positions were laid off more, while 56% of experts and above felt that the architecture positions were more laid off.

Young people are still too young to believe the truth. Experts have long seen through the reality.

Summarize

The survey brought us several insights:

1. The proportion of layoffs in large factories is not low. In order to work stable, you should try to choose a company with stable business
2. When applying for architecture positions, you can inquire about the proportion of programmers who are engaged in architecture positions in the company, preferably less than 17%
3. Don't be superstitious about technology. In times of economic downturn, you should try to choose a business that is close to money
4. Don't go to a big factory to do the architecture. The actual situation is completely different from what most programmers expect

Whether doing architecture or doing business, we must understand that technology is to create value. So what is value ?

In good years, an architecture that empowers the business is valuable. In bad years, the value is directly equated with how much money can be made. The closer the business is to the money, the greater the value.

And all of this has nothing to do with the difficulty of the technology itself.

Therefore, in order to develop a stable career, we should focus on the business itself rather than the technology.