How to write personal core competence? In this competitive society, job hunting is a very intense thing. In order for the company to choose us, we must highlight our abilities. I hope the following content can help you.
First of all, I don't know the position you are applying for, and I don't know whether you have work experience or are a fresh graduate. Secondly, in fact, the personal core competence in the resume is not important, because it is too subjective, and the time for HR to read the resume is very short, and subjective expression will not add points. The focus of your resume is still on your work experience. Make sure that all the work experiences listed in your resume are related to the position you are applying for, and are concise and clear. Let me make some suggestions:
1 is related to the company you are applying for. For example, a pragmatic company is different from a company that pays attention to innovation and individuality, and a large company with a sound system is different from an entrepreneurial small and medium-sized company. If it is a big company, pay attention to its corporate culture and history.
Don't write empty words, but highlight your abilities and achievements with examples, facts and figures. If it is a result-oriented position, you must speak with numbers. For service-oriented positions, you can also talk about the decline in employee turnover rate and the increase in satisfaction rate during your last term. If not, don't fake it. Just describe your most proud job-related skills and experiences and highlight your outstanding points. For example, if you are a fresh graduate, you want to say that you are proficient in operating data analysis software and various computer software. You can say that you have participated in several social research teams and are responsible for data analysis. In short, don't talk empty words, but have facts.
How to write personal core competence 2 In fact, the personal core competence in the resume is not important, because it is too subjective, and the time for HR to read the resume is very short, and subjective expression will not add points. The focus of your resume is still on your work experience. Make sure that all the work experiences listed in your resume are related to the position you are applying for, and are concise and clear. Let me make some suggestions:
1 is related to the position you are applying for, for example, sales emphasizes communication and service awareness, and administration emphasizes meticulousness and so on.
2. It is related to the company you are applying for. For example, pragmatic companies are different from companies that focus on innovation and individuality, and large companies with sound systems are different from entrepreneurial small and medium-sized companies. If it is a big company, pay attention to its corporate culture and history.
How to write personal core competence 3. Digging the needs of enterprises-need to understand the reasons behind enterprises looking for this position;
1, according to the company name Baidu search to understand the company profile (main business, establishment time, revenue, team size, company future planning, etc. And then judge the company's current development status and bottlenecks?
2. What is the general situation of subordinate departments and subordinate groups?
3. Leadership style (report directly to the target, the previous company background of the leader, the time when the leader joined the company, whether it was internal promotion or airborne, etc. ), and combined with JD, what kind of abilities do candidates need? If you can enter the interview later, you can judge more accurately;
Second, self-evaluation-refining your actual outstanding advantages (need objective evaluation,: (For example, according to specific positions,
1, academic advantages (enterprises value academic qualifications, and candidates are 985 or 2 1 1, and professional advantages (professional counterparts, the scarcer the profession, the more precious it is;
2. Company background: Top 500 companies in the world, top three companies in an industry or foreign capital background (provided that the company just needs job seekers with foreign capital background,
3. Language ability: If this position requires the language communication ability of a certain country, the advantage of language ability must be outstanding; For example, TEM-8, IELTS TOEFL score, small languages, returnees background, etc.
4. Career stability: the continuity of the industry, the continuity of the position direction, the time for each company to join the job, and career planning (current career direction;
Iii. Ability or experience in special projects:
1. In terms of personal performance, if you have management attributes, you should also highlight team performance and whether you have won a professional ability award in a certain aspect of the company. Team management ability;
2. Internal promotion route;
3. If the recommended position is a startup or a new team needs to be formed, does the candidate have experience in starting a startup or forming a team from 0- 1?
4. Whether there is any listing experience such as leading A shares or GEM, mainly for key positions such as CFO, auditor and CEO;
5. Have you ever experienced any internal reform or major blood changes?
6. Resources: social resources, government resources, commercial resources and customer resources. (depending on the job properties,;
7. Comprehensive quality: communication and coordination ability, pioneering and pressure-resistant ability, innovation ability, etc.
(It is best to combine certain professional evaluation results, which are relatively objective and convincing.
How to write personal core competence 4 The importance of high refinement
The projects are all owned by the company, and the product manager only works part-time, but what we learn from the projects is our own wealth. Constantly summing up skills from large and small projects can improve our efficiency and make it easier to complete the follow-up work.
While supporting the company's projects, we should always pay attention to the role of the projects in our own capacity building, otherwise it will be easily kidnapped by specific businesses. Once we leave this company, or leave our familiar projects, we will be at a loss.
Summing up experience and skills from the project is the first step, which helps us to find laws and refine experience from scattered and repeated projects. But when we experience more and more projects and these skills and experiences become more and more, it is difficult for our brains to remember them.
At this time, it is necessary to refine the experience and skills again to form a highly cohesive, extensible and versatile ability. You can call it capability model, capability map, etc. When it is concise enough, there may be only a sketch or even a few words. When you encounter problems at work again, you don't need to consider too many details, but find the normal direction from the highly refined ability model in your mind.
This bottom-up highly refined way can also be transplanted to other fields, beyond the work of product managers, extending to the understanding of life and constructing personal philosophy.
Establish a framework of career goals and abilities.
To extract the ability from the work content, we must first make clear the professional objectives and what is the ability model of the product manager, otherwise the extracted things will only be scattered and cannot be highly summarized.
For the competency model of product managers, Tencent's competency radar chart is well-known in the industry, which lists in detail the abilities and degrees that product managers at each rank need to master.
But its disadvantage is that it is somewhat general and does not distinguish the dimensions of ability well. For example, the contents of "mentality and emotional intelligence" and "ownership spirit" do not seem to be a dimension of ability, but belong to professional literacy, while "knowledge inheritance" and "talent training" are somewhat divorced from the ability model and focus on career development and enterprise construction.
There is also Wang Shimu of Netease Cloud Music's summary of the product manager's ability model, and puts forward different abilities to focus on content for product managers with different working years.
However, the disadvantage of this model is that it focuses on C-end products. For example, there is no mention of the very important technical understanding ability of B-end products, and it is obviously unreasonable to put the bottom content of "thinking mode" in the corresponding module of senior product managers for 3~7 years.
There are many competency models on the Internet, and we will find that the focus of competency of product managers in each field is different, so it is impossible to apply the models established by others. I think a qualified product manager should give full play to his subjective initiative, establish his own competency model according to his product direction and understanding of the product, and constantly improve it.
The following is my own pyramid product capability model. The thinking and quality of the bottom layer, the bottom layer is the basic layer, the middle layer is the core competence layer, and the top layer is the rich cognitive layer.
This pyramid applies regardless of the qualifications of the product manager. Product managers with deeper qualifications and more experience will have a higher pyramid and higher content richness at each level. But no matter what stage, the structure of the pyramid will not change, and it is built from the bottom up. If we pay too much attention to the upper level and neglect the infrastructure construction, the whole capability model will become unstable and flashy.
The two layers in blue belong to the ability layer, but I classify those who emphasize practical operation as the skill layer and those who emphasize analysis and decision-making as the insight decision-making layer. To improve the ability of these two levels, in addition to reading and communicating with people, I think we should rely more on ourselves to summarize and refine from practical work, which is also the main content of this paper.
Summary of project resumption
After establishing the capability model, we need to extract skills and experience from the actual project, and only in this way can we extract skills and experience from the project resumption. I summarize the project's resumption of work as follows:
First, the time rhythm of the resumption.
Large projects can resume work after a period of data feedback, and small scattered projects can resume work once every quarter or half a year.
Second, does the product go online to meet the real demand?
Users first, whether the online products have solved the real demand is the first thing to be re-provided.
1, real user feedback
You can communicate directly with users, or the feedback center of the platform can find out the usage of users. I personally do a lot of background products, and generally collect feedback from business parties directly after going online.
2. Feedback of data analysis
User feedback is mixed with many subjective factors, and there is survivor bias. It is necessary to understand the use of functions through more objective data statistics. The granularity of data analysis can be large or small. There are many buried points in C-end products, and the data of user's operation path can be analyzed, while the data of B-end products is less, which is mainly evaluated from the aspects of function utilization rate and work order.
Third, is the product design reasonable?
Since I am mainly responsible for B-end products, the following summary is more suitable for B-end design.
1. Is the product function simplified enough and the design excessive?
B-end products mainly improve efficiency and meet business needs, so we should avoid too many fancy designs and solve the core needs first.
2. Is there any missing abnormal flow?
Abnormal flow should be fully considered in the planning process. But if it was really omitted at that time, it would be exposed in the process of product operation. You should seek feedback from the business side and customer service in time, find this missing abnormal logic and fix it in time.
3, the influence of the associated system
For platform products, there are many callers, and each party has different needs. After the product goes online, it is also necessary to confirm the influence of other related systems on a regular basis, such as data call and authority distinction.
4. How about the expansibility design of the system? Is there reservation logic?
The expansibility of the system sounds like over-design, but there are essential differences. Extensible systems can quickly adapt to similar demand access, and reservation logic generally does not consume too much development alone. In the process of rewinding, we can carefully examine the scalability of the initial system by combining the iterative contents of multiple versions. Overdesign is to do a lot of useless functions, with heavy workload, low value or difficult to use later.
5. Whether the rhythm of functional iteration is reasonable and whether there is repetition.
For a long-term upgrade iterative system, when reviewing its iterations, we can review whether our decision on the content of each iteration is reasonable and whether the content of dependencies is completed before the development of dependencies. Are there many iterations at the same point? Why didn't you solve it once? These problems can only be evaluated by looking back.
Fourth, the project process review
In the process of project development going online, we can review the following contents. This process can invite demanders and developers to participate together, and it is also a good way to improve the efficiency and execution of teamwork.
1. Is the communication between demanders clear, is there any major revision, and why?
Whether the requirements are clear enough before the project starts, what are the major requirements changes during the project, what are the reasons for the changes, and whether the requirements documents are recorded.
2. Have the requirements been reviewed once, and which ones were adjusted after the review?
If the core process is not well considered or needs to be greatly changed during the requirements review, the meeting will be embarrassing and the product manager will lose face. This process usually happens when you first start making products. It is more useful to look back on your own setbacks, sum up your experience and get the affirmation of development next time than to look at the methodology of countless others.
3. Is the development progress delayed and which one caused it?
The process is important, but the result is more important. Generally speaking, it is not allowed to extend the online time of the project in advance. However, if there is no online requirement, the project can easily be postponed. If the demander, product, design, development and testing are all delayed 1 day, the project will be delayed for more than one week. By reviewing the time schedule of the whole project, the specific links and reasons of the delay are discussed seriously and objectively, so that the team can pay more attention to the concept of time.
4. Is the external cooperation smooth, and what causes affect the progress?
When it comes to cooperation projects with external companies, variables and uncontrollable factors become more and more, and the promotion efficiency of such projects is generally low, especially when docking for the first time. However, by reviewing the projects I have taken over, sorting out some subjective and controllable contents, and remembering the pits I have stepped on, I can improve my project cooperation ability.
4, the establishment of capacity induction table
After the project is resumed, we will sum up our skills and experience. The following is a summary table of my ability, which can fill in the content and experience summary of each project and find the corresponding position. You can also record the work content in this form first, and then fill in the corresponding content at the back regularly.