The definition of the level of Java programmers: check the number of seats, at which stage you have to know a little bit

The definition of the level of Java programmers: check the number of seats, at which stage you have to know a little bit


Newcomers who have just entered the workplace are generally at this level. This point does not distinguish between a bachelor s degree and a master s degree. For example, my first company graduated with a master s degree and entered as a junior engineer, while a bachelor s degree is an assistant engineer. The company's definition of the level of newly graduated students is similar, T1-1 for undergraduates and T1-2 for masters. The major levels are all T1, and the subdivisions at the lower levels may be slightly different from the starting point of the salary (don't ask me how bad I am, I don't know, but it is estimated that the difference is not big).


To talk about the most essential distinction between intermediate and beginner, I think it is reflected in independence. Junior students who just joined the company usually arrange one-on-one tutors to help them get started quickly. Therefore, many junior students are dependent on the tutor in their work. After working for a period of time (1 or 2 years), they are already quite familiar with the company's various development process specifications, familiar with some of the businesses, products and codes in their participating projects, and can complete business function development as required.

Therefore, intermediate engineers can basically undertake development work independently, and some can even guide newcomers, and grow into the backbone of the company's "action execution" level. The basic requirements at this level are: complete actions, achieve quality, and optimize efficiency . However, it has been observed that most engineers of this level can do it, but the quality may be flawed, and the efficiency may even be flawed. Regarding efficiency and quality, we are constantly improving through continuous iteration and improvement, and we are constantly growing in this process and moving towards the next step.

Many people are stuck at this stage because although they are constantly completing their work, they have not reflected, precipitated, iterated and improved, which has led to staying in continuous repetition.


This level basically belongs to the ability to independently be responsible for the subsystems or modules in a small project or a large project. He is the backbone member of the project and belongs to the largest individual contributor in the team or project.

Compared with the intermediate level, senior engineers are a tough force at the level of "action execution". They can not only complete advanced and difficult development tasks independently, but also make more comprehensive considerations in user experience (quality improvement) and performance optimization (optimization efficiency). Not only the development tasks are completed quickly and well, but also how fast and how good can be clearly defined.


Some of these levels are called " senior engineers " and some are called " architects ", and the different names represent two different development directions. In basic R&D, algorithms or specific technically complex areas, they will develop in the direction of "senior engineers", which is a depth priority. In the field of business development, business complexity is higher than technical complexity, and it will develop in the direction of "architect", which is breadth first.

Regardless of depth or breadth, entering this level means that you have already had considerable accumulation in a specific field, serving as a technical backbone in projects and teams. In addition to the accumulation of own professional knowledge, skills and practical experience, we can also summarize and precipitate effective methodology from it, and guide and organize team members to promote and apply together. Actively output their own experience and provide technical support for cross-team projects.

Many senior engineers with a certain number of years of work are stuck on the threshold of entering this level. I think there are two reasons. On the one hand, although they have rich practical experience, they have not systematically sorted out their years of accumulation. Well formed system. The so-called system is the precipitation of effective methodology as mentioned above. The greatest function of effective methodology is to help rapid decision-making, and the probability of correct decision-making will be relatively high. On the other hand, even though he has a block in his chest, he cannot pour out a thousand words in his belly, and there is an obvious bottleneck effect. The negative effect is that it is difficult to effectively evaluate his "senior" level.

The technology is not a system, and it becomes the technical system that architects need to master:


Technical experts generally lead major technical projects in the company, and they also have recognized influence in the industry in their subdivided technical fields. Naming "home" can make people feel unattainable and unattainable. The actual "homes" are also divided into big and small. The average "everyone" is actually a rare treasure, rare in the whole country, and it is indeed out of reach, but there are also "small homes" that are relatively not so far away.

And the total of experts is linked to influence, and influence sounds very virtual, so let's talk about influence from a relatively solid perspective. As a Java programmer, there are always a few people in the process of learning to use Java. Not only do you have to read their books but also read and use the code they wrote. You can't get around in the Java field. So this is their real influence in this field, and they are naturally experts in this field. Therefore, the expert may be someone you can't get around in this field.


With the definition of level, how to assess what level a person belongs to? This point will be relatively loose in the low-level evaluation, and the more difficult it is to evaluate the higher the level. For different levels of evaluation standards, some large companies have defined evaluation standards covering multiple dimensions and gave detailed instructions. For high-level promotion, the company s expert review team will organize the promotion report defense. The review team s judges make a comprehensive judgment based on these multi-dimensional standards.

Welcome to join the Java architecture development: 692845439, Java engineers and friends who have worked for one to five years, you can get this set of architecture data worth 18,000.