Today we will talk about how to write a resume when recruiting at school. To be honest, different people may have different opinions on the way a resume is written, and different interviewers/HRs will be different in the selection process, so in my opinion, there is no absolutely stable resume. stencil.
I also asked a lot of people who came here about resumes when I was recruiting at the school, and I also knew a lot of big guys who had been interviewers. At the time, they were all asked to help revise their resumes. Today I will base on my own experience and big guys. Suggestions, tell you how to write your resume, and maybe it can bring you some useful references.
At the end of the article, I will also give my resume template when I participated in the school recruitment + the template when the big guys participated in the school recruitment
Let’s first answer a question: Is it better to write one page or two pages for your resume?
Regarding this question, maybe your senior brother and sister will tell you that it is best to write one page, and the interviewer does not have so much time to read the resume; some people will tell you that it is best to write two pages. After all, we have not won any awards. Can add more things that you know on your resume.
My answer is that one page or two pages is fine, as long as you express what you want to express, then it is fine, but it is not recommended that the first page cannot be written, the second page only writes 20%, and then other Leave it blank, personally suggest not to leave too much blank.
What should be in the resume?
For school admissions, the resume is nothing more than personal background, educational background, basic skills, project experience, personal honor, and self-evaluation. The most important ones are the two modules of basic skills and project experience . So this This time I will also focus on the writing of these two modules.
1. Writing of basic skills
For students who want to enter a large factory, the mastery of basic knowledge is nothing more than the most important point, because large factories value your future moldability, and a solid foundation is a very important proof. Someone may ask, what is the basic knowledge?
Basic knowledge is nothing more than the courses taught in our university, such as data structures and algorithms, computer networks, operating systems, databases, Linux, and so on.
I have seen the resumes of many people. When writing basic skills, many people basically write very "concisely". For example, when writing computer networks, the resume simply writes this line: Master computer networks.
To be honest, the knowledge contained in computer networks is too much. If you are not a great person, I suggest that you write a little bit more in detail when writing basic skills, for example, write down some of the agreements you have mastered:
Familiar with the OSI seven-layer model and the TCP/IP four-layer system hierarchical structure, master common network protocols, such as ARP, ICMP, TCP, UDP, DNS, DHCP, and https safe working principles.
If you list these, it feels like you really have mastered it, and it is also convenient for the interviewer to choose questions to ask. Under normal circumstances, the interviewer will pick the skills you know to ask if you really understand it, not I'm specifically looking for some unpopular knowledge that doesn't exist in your resume to ask you.
Therefore, when writing basic skills, I suggest that you write in more detail, and list the knowledge you want to be asked by the interviewer.
For example, if you understand data structures and algorithms, don't just write "Master Data Structures and Algorithms". You can write algorithms that you think you have a good grasp. For example, I wrote it like this:
Solid data structures and algorithms, such as mastering stacks, queues, linked lists, binary trees, graphs, sorting algorithms, recursion, dynamic programming, divide and conquer, backtracking, etc.
Because everyone has learned data structures and algorithms, most people probably have the words mastering data structures and algorithms written in their resumes. How much they master is different for different people.
So, on the resume of school recruitment, if you don’t have any awesome experience, then I suggest that you must work hard in the direction of basic knowledge, and be as detailed as possible when writing, and give everyone a screenshot. Written on my resume (my resume is 1 page, so I try to be concise)
When I was recruiting in the autumn, when interviewers asked about basic skills, most of them asked questions from the knowledge listed on my resume, and then extended them. What needs to be emphasized here is that you must understand what is written on your resume. Before I wrote some Linux commands on my resume, I was asked by the interviewer, so I just happened to have never used that command, which embarrassed me to death.
2. Project writing
I have seen some resumes of some friends who want to participate in the Spring and Autumn Recruitment before, and often see this situation:
1. When someone writes a project, they talk about a lot of project background, and then they have done what they have done, but it is a brief introduction. I can't find out what he has done from his project experience.
2. Many people also asked me, what should I do if I don't have an internship project or a real online project?
For school admissions, many other people have relatively little contact with projects, and many large companies will not be too demanding on you in this regard, so I think the most important thing for a project is not how tall the project is. in this project, but you yourself do, with what technology to solve the problem.
And for a project, we can also do some appropriate packaging, and then prepare the corresponding interview questions ourselves. For example, your project is done with the video. If you feel that you have a good grasp of it, you can actually package it into your own internship project.
When writing a project, the more important points are:
(1) Use technology: Write down the technology you use in the project, such as whether you use redis, or spring, springcloud, etc.
(2) Briefly introduce the project: I guess most people's projects are relatively simple, so in the introduction, you can briefly introduce the function and background of the project. Don't write too much in this area.
(3) My responsibilities: I think this is the most important thing, that is, what you did, what technology you used to solve what problems, and the interviewer will most likely ask you questions from these problems you solve. For example, in the project I said using redis as a message queue to solve asynchronous problems, and then I also prepared related interview questions. After that, the interviewer happened to ask a lot about this message queue, and then...
In other words, when writing a project, the technology used, what we did and what problems we solved, are the most important part, because the resume is used to show ourselves, so we must ask the interviewer See what we will and what we have done.
3. Personal honor
If you have obtained a good certificate or competition, you can write it in this column. For example, if you have a good score in CET-6, then you can write in the fact that you have passed the CET-6 exam. But if you, like me, only took CET-4, and the score in CET-4 is still poor, then it is not recommended to include CET-4, because the matter of passing English CET-4 , should most of the undergraduates have this requirement? So don't write it.
There are also those certificates that you have participated in some social activities and knowledge defense. There is no need to write them. The honor certificates written on it are recommended to be linked to your major. For example, if you get the advanced certificate of the soft exam (the intermediate level has no gold content, of course you can write it), you have participated in the ACM at school and won the award, and you can participate in the online competition to get it. Prizes and so on.
Many people will make a self-evaluation at the end, and most people write it or not, because he wrote it like this:
1. I love programming, learning, reading, and sharing.
2. Like to explore and challenge.
To be honest, I think that what has been written is the same as what has not been written, because all individuals have such characteristics, so in the self-evaluation module, if you have written, I suggest you write specific points.
For example, if you say that you like to read books, you can give examples of some books you have read by the way; if you like to share, you can tell how many articles you have written; if you like to learn, you can talk about the communities you often go to, such as csdn, blog garden , Stackoverflow.
If your resume has been written, then you can see if there is any improvement based on my article. If your resume has not been written yet, or if you want to find a resume for reference, then I have prepared two copies here. Resume, one is for a one-page Java background development position, and the other is a two-page Linux/C++ position. You can reply to the " resume " in the backstage of the official account of " Shuaidi Play Programming " to get the word version of the resume.
Finally, everyone is welcome to add in this aspect of your resume. After all, everyone’s opinions are different. The suggestions I gave are not the best. For you with less experience, you may be able to give you a reference. .
Author: Hello everyone, I am Shuaidi. I have come from university and self-study all the way. I know the importance of algorithms and basic computer knowledge . The author of the public account " Handiplay Programming " has 100,000 fans. I specialize in writing these low-level knowledge and improve it. Our internal strength, handsomely look forward to your attention, study with me, click to understand my four-year university study road reprint instructions : without authorization, prohibit reprinting