This article was first published from "MOOC" (www.imooc.com). If you want to know more about IT dry goods and hot news in the programmer circle, please pay attention to "MOOC" and "MOOC Official Account"!
Author: Shuangyue | MOOC famous teacher, front-end technology expert
My 1-1 Communication Services
Before entering the text, let me introduce the background, so that everyone can know the source of the case in this article.
Some time ago, I launched a 1-1 private chat communication service. Chat with me 1-1 WeChat voice (or Tencent meeting), and I will answer questions on the spot.
I want to use my personal experience and lessons from so many years of work, interviews, and lectures to help those who have technical skills but can't write, and help them express themselves better. By the way, appease their anxious and impetuous mood.
My strengths in this regard are as follows:
- I have relatively solid front-end technology, work experience in large factories, and open source experience, which can help them improve their technical capabilities
- I have many years of training and teaching experience, and I know how to express in an orderly manner-this is exactly what pure technicians lack, they will only do it dully, and will not speak
- I have read some books on history, psychology and philosophy in my spare time, plus my many years of work and freelance experience, I can look at problems beyond technology and help psychological counseling
It was a trial run for one month, and then it was officially launched. At present, we have chatted with 20 people in total, mostly for reviewing and revising resumes.
I am very happy: everyone's feedback is good, saying that they have provided them with unexpected help.
The resume really needs to be changed!
There are two types of people with poorly written resumes: 1. Fresh graduates; 2. Those who have not changed jobs to find a job after graduation.
This kind of resume basically needs to be restructured, and it must be rewritten from the format to the content.
For those who have experienced job hopping, the resume format is acceptable, but there are also many problems, even low-level problems.
First, typos, or wrong words.
This mistake may seem simple, but its repercussions are serious.
You think, your resume is the most important personal document for you. If you don’t write it carefully for such an important document, I don’t believe how carefully you can write documents and codes at work.
Second, professional skills are chaotic and fragmented.
Write what you think of, write as much as you can, and more than ten skills to show that you are very skilled.
You are messed up yourself, and the interviewer has finished reading it, and he doesn't know how many skills you have, so he is also messed up.
Third, the role is still positioned at the grassroots developers.
The ass determines the head. If you position yourself in grassroots development, then every detail of your resume is written with this thinking.
If you have been working for more than 5 years, please consider whether you will be a front-end leader or team leader.
This one was particularly prominent among the 20 people I talked to. I was already in charge, but I didn't realize it.
Fourth, personality and highlights cannot be written in the description of project experience.
The "personal responsibilities" of each project write some public content, what is responsible for development, maintenance, and performance optimization.
These descriptions also apply to another project. To put it bluntly, this is a bunch of nonsense, and it is worthless to write it.
Everyone Has Their Own Highlights
Earlier, I thought that my personal highlights were amateurs (blogs, open source, etc.), and there were very few people who could have highlights.
Later, I found out that the highlight is in your daily work, and everyone has their own characteristics and highlights.
I talked to these 20 people, and everyone would say: I feel like I don’t know anything, I don’t do anything, I just write business every day, add, delete, modify and check...
Then I ask: Do you have some complex functions in your project that take many days to develop? Have you encountered any problems that keep you working overtime in the middle of the night?
Asked and asked, and it came out. The projects developed by everyone are different. As long as these projects are actually running, they have their own characteristics and complexity. These are your highlights.
- Someone made a very complicated table report, and I dug it out
- Someone has done a very complicated system-level permission configuration, and I dug it out
- Someone made a dynamic form, and I dug it out
The way I discover my personal bright spots is simple and crude: I just ask questions out of the casserole, and you just rack your brains... After tens of minutes of painful thought struggle, the bright spots will be filtered out.
So, for me, this 1-1 communication is also a labor-intensive job, which takes a lot of brains.
Classmate A
Beijing, 6 years experience. I graduated in January and have not found a suitable job.
professional skill
The above are professional skills written by himself. The main questions are:
- Too much content to focus on
- Information is scattered and not systematic
- Word capitalization is confusing and unprofessional
- jQuery git fetch, etc. can not be written, it is too basic
The above are my modification suggestions. After the modification, the content has been streamlined and the key points can be highlighted, but its core value has been retained.
- Front-end basic knowledge is exclusive to one line
- Vue takes one line alone, React takes one line alone
- Echarts he uses a lot, and also occupies a line
- Nodejs exclusive line
in addition
- He is not familiar with algorithms and data structures, otherwise this item should also be written
- He is not familiar with Vue3 , otherwise it should be written in the skills
Role
He positioned himself at the beginning: front-end development.
Later, after my consultation, he actually started to be the front-end person in charge later, although there is no leader position.
But it doesn't matter, others don't know the situation of your company, nor your position.
As long as you have really been in charge of a project yourself, you are the front-end person in charge. Speak with facts, without considering those false positions and titles.
Project experience
There are many projects, let’s take one project as an example
The above is a project written by himself. The main problem is that the part of the responsibility description has not written any personality and value at all.
Let me ask, as a developer, which project you are in is not all about "page display, routing construction, component packaging, front-end and back-end interaction, optimizing front-end page response speed..." These tasks, is there a difference? Writing is equal to not writing, and has no value.
Then, I asked him about the project situation carefully, and asked him to think and talk over and over again. After about 20 minutes, I gave suggestions for modification:
After the modification, it will be completely different, with content, personality, highlights, and technology:
- Have technical scheme design and project management, and show that you are the role of the person in charge
- Find out the highlights of the project (the underlined part in the above picture)
- If the content is not enough, add some general methods such as "performance optimization", but write a specific optimization plan
Note that in the responsibility part, try to write technical terms for each item. You are a developer, you are not a product manager.
You can refer to this template 使用 xx 技术，实现了 xx 功能，达到 xx 效果.
mentality adjustment
When he first started chatting with me, he was in a very bad mood. I haven't worked for several months, and I can't stretch myself.
So while I was talking about my resume with him, I was doing psychological counseling (it’s definitely not chicken soup, who still listens to that now, if you are honest, the atmosphere is very cheerful), and he calmed down after the chat.
Classmate B
Shenzhen, 5 years experience. After graduating in January, I interviewed several companies, but the results were not good. There were few interviews.
His professional skills are still well written, and there are relatively few places that need to be revised
work experience
The above is his own work experience, and there are two main questions:
- The role has always been a Web front-end development engineer , and it should be considered whether there is also the role of the person in charge
- The job description is too cumbersome to write, just briefly describe your role and responsibilities, and write technical things in the project experience
After the above consultation, the modification suggestions I gave
- The most recent job role was changed to front-end team leader (this was confirmed after consulting, not hard-written)
- Plan responsibilities and write out the main work that fits the current role
- Two jobs, with changes from roles to responsibilities, reflecting personal growth
Project experience
There are many projects, take one project as an example
The above is a project written by himself, and many problems can be found
- There is no project introduction, so I don’t know what to do
- The technology stack is not extracted separately. The most important thing in a technical resume is the technical terms, which must be seen at a glance
- The project responsibilities are written without any personality, and any project has cross-component communication and performance optimization-this is the main problem! ! !
After detailed consultation and asking him to explain the project in detail, I gave the above modification suggestions. Just look at the responsibilities section:
- I helped discover the complex functions of the project business: form linkage + authentication
- Write the features of WebApp : mobile terminal adaptation + js-bridge
- Add a general technical capability: performance optimization
Classmate C
A second-tier city, working for 5 years, on-the-job, small R&D team, informal process.
professional skill
The above are the professional skills written by himself, and the problem is similar to that of student A.
- Too much information, too fragmented
- jQuery git Don’t write these, it will reduce your technical vision
The above is after my suggestion and modification
- After induction and integration, the skills are clear at a glance, from the foundation to the framework
- Vue and applets are his main skills, both in one line
- React TS is an accessory skill, written later
- Write down if you have used Ruby, after all, full-stack talents are more popular now
Similarly, algorithms and data structures, according to his personal situation, have not been written yet.
Project experience
The above is the project experience written by himself. The problem still lies in the description of responsibilities, without any personality, and it can be adapted to any project.
Moreover, the project introduction and technology stack are mixed together, which is not easy to distinguish at a glance.
The above is after my detailed consultation and revision. The technology stack is separated separately, and the project responsibilities also have personality and highlights. Can reflect their own unique value in this project.
Classmate D
Shanghai, working for 5 years, is about to graduate.
professional skill
The above are the professional skills written by him himself, which is very confusing, and it has not been sorted out at first glance. For example, Vue React is written together; for example, there are also wrong words...
The above are my revision suggestions, mainly to summarize the skills to make people look more systematic and not chaotic.
work experience
He wrote three work histories, each of which was true. The main problem is: too much technology-related content is written here, and the subsequent project experience cannot be written anymore.
Therefore, don't write your work experience in such detail, just briefly express your role and responsibilities without writing any technical terms. Technology-related content should be written in the project experience.
The above are the revision suggestions I gave, specifying the main responsibilities, and writing the rest on the project experience.
Project experience
Since he has written too much technical content in his previous work experience, he cannot write other content in his project experience, which is very unreasonable.
But after simplifying the work experience, the project experience can be enriched. After detailed consultation, I finally gave the following suggestions:
After supplementing the project responsibilities, the content immediately enriched. And with personality and highlights, it reflects its own skills and technical value.
About Counseling
With a good mentality, everything can be done smoothly, with confidence and motivation. With an impetuous and anxious mind, you will be hindered in everything you do, and it will not work well if you force yourself to do it.
Whenever I communicate with a person 1-1, I will chat to assess their mental state to see if there is some negative emotion.
If he finds out, or he himself says yes, I will actively guide him to express and pour out his inner thoughts, and then I will give you some of my opinions. The final effect is very good.
In fact, psychological counseling does not have any miraculous tricks, nor is it pouring chicken soup, blood, or continuing to sell anxiety. Just do the following:
- as a listener. Let others (or guide others) speak out, listen carefully, and try to feel his emotions;
- Based on his confusion, let me share my opinion, and I know other people's experiences. Different people have different experiences and different environments, so they will have different opinions. Guiding others to think about problems from another angle is a kind of guidance in itself. Everything has multiple sides, and there is no pure good or pure bad.
- Find out what his problem is, analyze the root cause, and give solutions. Let him see how he should go in the future, no matter whether he can succeed or not, take the first step before talking, and do it first.
Finally, I wish everyone can get out of the circle with their resumes and find the job they want. If you are also confused about your resume, welcome to interact with me, teacher Shuangyue.
Welcome to pay attention to the official account of "MOOC". We will always insist on providing high-quality content in the IT circle, sharing dry knowledge, and let's grow together!
This article was originally published on Muke.com, please indicate the source for reprinting, thank you for your cooperation