primary
Newcomers to the workplace are generally at this level. There is no distinction between a bachelor’s degree and a master’s degree. For example, when I graduated from my first company with a master’s degree, I was considered as a junior engineer, and when I graduated from my first company, I was an assistant engineer. The company has a similar level definition for new graduates, namely, undergraduate T1-1 and master T1-2. The big ones are all T1, and the breakdown at the small ones is probably just a slight difference in starting pay (don’t ask me by how much, I don’t know, but it’s probably not much).
The intermediate
What is the most essential distinction between intermediate and primary? I think it is reflected in independence. When junior students just enter the company, one-on-one tutors are usually arranged to help them get started quickly. Therefore, many junior students depend on tutors at work. After working for a period of time (1 or 2 years), they have become quite familiar with various development process specifications of the company, familiar with part of the business, products and codes involved in the project, and can complete the development of business functions as required.
As a result, mid-level engineers are often able to take on development work on their own, and some can even mentor newcomers, growing into the backbone of the “action execution” side of the company. The basic requirements of this level are: complete action, achieve quality and optimize efficiency. But the observation is that most engineers at this level can do it, but the quality may be flawed, and even the efficiency may be defective. Efficiency and quality are always improved through continuous iteration and improvement, and they are also growing towards the next step in this process.
And many people are stuck in this stage, because although they are constantly completing the work, they do not reflect, precipitation, iteration and improvement, resulting in constant repetition.
senior
This level basically belongs to the ability to be independently responsible for subsystems or modules in a small project or a large project, as the backbone member of the project, and as the largest individual contributor in the team or project.
Compared with intermediate engineers, senior engineers are the “action execution” level of the breakthrough force, not only can independently complete high-level difficult development tasks, but also can make a more comprehensive consideration in user experience (quality improvement) and performance optimization (efficiency optimization). Not only do development tasks get done fast and well, but they can clearly define how fast and well.
senior
Some of these levels are called “senior engineer” and some are called “architect”, and the different terms represent two different directions of development. Senior engineer in basic R&D, algorithm or specific technical complex area, depth is preferred. In business-oriented development areas, where business complexity is higher than technical complexity, the trend is toward “architect”, which is breadth first.
Whether in depth or breadth, this level indicates a proven track record in a specific area, serving as a technical backstop on projects and teams. In addition to the accumulation of professional knowledge, skills and practical experience, I can also summarize and settle effective methodology from it, guide and organize team members to promote and apply it together. Proactively share experience and provide technical support for cross-team projects.
Many senior engineers who have worked for a certain number of years are stuck at the threshold of entering this level. I think there are two reasons. On the one hand, although they have rich practical experience in various fields, they have not systematically combed their accumulation for many years and failed to form a good system. The so-called system is the precipitation of effective methodology mentioned above. The biggest role of effective methodology is to help rapid decision-making, and the probability of correct decision-making will be relatively high. On the other hand, although there is a chest block, the abdomen can not pour out thousands of words, there is an obvious bottleneck effect, resulting in the negative effect is difficult to make an effective assessment of its “senior” degree.
experts
Technical experts typically lead major technical projects in the company and have a recognized influence in the industry in their respective technical areas. Having a name like “home” can make people feel out of touch and out of reach. In reality, “families” are different in size. Ordinary “everyone” is actually a rare treasure, which is rare throughout the country and indeed far away. But there are also “small families” that are relatively not so far away.
And experts are linked to influence, influence sounds very empty, then change a relatively real point of view to say influence. As a Java programmer, there are always a few people in the process of learning to use Java, and you not only have to read their books, but you also have to see and use their code. So that’s the real impact that they have in this area, and certainly experts in this area. So, an expert is probably someone you can’t get around in this field.
Evaluation of
Given the definition of rank, how do you evaluate a person’s rank? This is relatively easy to assess at lower levels, and harder to assess at higher levels. For different levels of evaluation criteria, some large companies have defined the evaluation criteria covering multiple dimensions, and give detailed explanations. For high-level promotion, the expert review panel of the company will organize the promotion debriefing defense, and the judges of the review panel will make a comprehensive judgment according to these multidimensional standards.
Technology is not a system, become the architect to master the technical system:
These are the knowledge and technology systems that architects need to master to see how far you are from being an architect.
1. Those with 1-5 work experience do not know where to start in the face of the current popular technology and need to break the technical bottleneck.
2. I have been in the company for a long time and have been comfortable, but I hit a wall in the interview when I changed my job. Need to study in a short time, job-hopping to get a high salary.
3. If you have no working experience, but have a solid foundation, familiar with Java working mechanism, design ideas and common Java development framework.
4, feel very good B, general needs can be done. But without systematization of knowledge points learned, it is difficult to continue to break through in the field of technology.
5. Group Number: Advanced Architecture Group 685167672
6. Ali Java senior bull live explain knowledge points, share knowledge, sorting out and summarizing years of work experience, with everyone to establish their own technical system and technical knowledge in a comprehensive and scientific way!
Concern public number has surprise!!
