In the Internet field, Ali’s rank system and Tencent’s rank system are equivalent to industry standards, so technicians still need to learn/benchmark, so as to know where they are currently and where is the direction of their efforts? So, what capabilities does Ali P7 level need? As shown in the mind map below:
To dismantle the capability model of P7, it is actually technology, business, general, and others.
1. Technology
According to the above mind map, the technical part is refined into the following three points:
1. Be responsible for the technology in a field, be able to define the core issues in the field, have the ability to think and plan and iterative evolution, provide technical solutions with industry competitiveness, and have a certain technical depth and breadth.
Interpretation: Let me interpret this article as "a certain technical depth and breadth". How can this be precisely defined? For example, if you are a P7 business backend, you must be familiar with MySQL (table design and index design and optimization), JVM principles, JavaSE foundation, design patterns, Spring family bucket series, correct use posture of cache and MQ, distributed Principles, various middleware such as configuration centers, microservices, etc., and even need to understand the three principles of architecture design (proper, simple, and evolutionary principles), DDD, CAP theory, Docker, K8S, and Byzantine generals’ problem, etc.
As for the depth, such as JVM, you need to understand various garbage collection algorithms. When you encounter outofmemory, YGC, and FullGC, you can quickly locate the problem. When encountering a certain SQL that suddenly does not use the index, you must be able to analyze the specific reason. The CPU load of the application server suddenly increases to dozens of times, and you need to have the ability to locate the problem in the first place.
2. Can design a good technical architecture for complex problems and diverse environments, have good scalability and robustness for a class of business/technical problems, and have a strong awareness of data analysis.
Interpretation: There are several methodologies for dealing with complex problems: abstract commonality, simplification, modularization and componentization, running first and then optimizing, etc. The so-called robustness refers to the robustness and robustness of the program. The big ones are the multi-active architecture. If a computer room is down, it will not affect the normal business operation. The small ones, such as the cache cluster down, the system will not be down, and the failover will be immediate .
3. Think about technical strategies and insight into technical requirements from the back of business development, form a corresponding technical product support system, and drive the sustainable development of business.
Interpretation: As far as I know, most of the company's technology is to support the company's business development, and the technology-driven company's business is very small. If there is one, the company I have worked for, such as the VR house inspection of Shell, is a scene.
Let's talk about technology first, let's continue...
2. Business
1. Responsible for a small business line, able to disassemble product requirements and carry out platform precipitation, and at the same time have the ability to reverse drive business development.
Interpretation: Let me focus on "reverse driving business", that is, technology evolves from supporting business to pushing business forward. I believe technical people are very proud of this scenario.
2. Have structured thinking and the ability to define indicators, fit the big business goals, clearly understand the positioning and core focus of your team, have the ability to evolve architecture and plan implementation, and achieve business results supported by data (positive/ reverse).
Interpretation: Structured Thinking refers to a person who can think from multiple sides when facing work tasks or problems, deeply analyze the causes of problems, formulate action plans systematically, and take appropriate measures to make work possible Develop with high efficiency and achieve high performance. A simple example. Our database field type is structured thinking. For example, when we measure whether a structure is excellent, we need to think in terms of stability, robustness, and scalability. This is structural thinking.
3. Possess the technical PM ability to coordinate multiple businesses, have strong technical integration capabilities, have the ability to identify technical risks in the upstream and downstream links of the responsible business, and can provide a reasonable overall solution that meets the demands of all parties, and can obtain to business results.
Interpretation: The technical PM here is not the business PM we usually talk about. He is mainly engaged in the design, promotion and implementation of technical projects (such as unified service transformation, multi-product line access to unified SSO system).
It is not enough to only understand the targeted technology and business, but also some general technical knowledge, please continue to read below.
3. Universal
1. Ability to develop and design solutions across 1 to 2 technology stacks, with good technical self-driving force and business thinking ability.
Interpretation: As a back-end, we need to have some front-end knowledge. With multi-field knowledge, our ideas and methods for solving problems will be much broader. As for the business thinking ability, we need to understand the business very well, go to the business site to practice more, and think more to have this ability.
2. Understand the whole system, have the coding ability of core modules, have a strong ability to analyze and solve problems, and are the key problem killers.
Interpretation: To put it simply, all technical problems of the system we are responsible for can be quickly resolved.
4. Other
1. Focus on human potential, self-drive, initiative and curiosity
2. Ability to lead small teams
Interpretation: According to the strategic direction of the business, you can point out the technical direction for the team, and at the same time lead the team to complete the set goals. At the same time, you can give guidance according to the characteristics of each subordinate, so that subordinates can earn money while improving their own capabilities. Of course, for those who do not meet the team's values or fail in performance, they must be cut quickly.
3. Ability to cultivate technical backbone
Interpretation: I have seen a lot of technical managers or P7 friends. They can do a difficult job well by themselves, but they lack experience in cultivating newcomers and technical backbones (P6), but as P7, this ability is must have.
How to do it?
The first is to give him challenging projects, and the second is to help him solve various problems encountered in the project (such as system planning, cross-team communication, etc.), which I call "helping him on the horse and sending him another journey".
In order to systematically solve the problem that many readers are difficult to be promoted from P6 to P7 and do not know how to break through.
LZ shared with you a learning route from Java zero foundation to architects, which was relatively popular in the architect community some time ago, against Ali P5~P7, and I hope it will be helpful to you.
Interested friends, check at the end of the article
Benchmark Ali P5~P7Java programmer system learning route
P5 (Independent execution of established tasks) (20~40w)
P6 (operation and landing) (annual salary level 40~60w)
This part needs to be understood. There are many contents for proficient operation. Just look at the picture.
-
Pre-knowledge
-
underlying foundation
-
concurrent programming
-
RPC principle
-
The principle of message middleware
-
Fundamentals of Software Design
-
Distributed Architecture Practice
-
Microservice Architecture Practice
-
Mass data storage, search and processing
-
ServiceMesh theory is implemented in practice
P7 (principle and design) (annual salary benchmark 50w120w)
Understand the design theory of the architecture, the underlying support algorithm, the foundation of distributed networks, and the principles of commonly used middleware. Make your own design and implementation of the general architecture of ultra-high traffic, multi-level cache, and elastic expansion
-
Theoretical basis and algorithm support
-
Source code analysis
-
High Performance Architecture Design
-
case-driven design
Interview for promotion
Memorizing stereotyped essays, resume construction, interview expression skills, and post-interview review are all indispensable
Advanced Architect
On the basis of practice and design, stand at a higher height and expand a broader technical vision. At this stage, it is often driven by a sense of mission. Salary is one aspect, but not a decisive one.
at last
Many details in the route are actually not fully developed. It can be said that this learning route covers all mainstream technologies in the Java field. Whether you are just entering the industry or planning to improve yourself on the job, you can learn supplementary technologies according to the route. If there is a small partner who needs a complete learning route, click on the small card below`