Resume the tone
The programmer’s resume should be concise, not too complicated in design, and if there is a photo, there is no color other than the photo.
A template for your resume is also provided below
A one-page resume is enough for school recruitment, and a two-page resume is enough for social recruitment.
Some schools recruit students say they have too much experience, resume to write two or three pages, after reading the basic is not too much content, is too wordy, for example, a lot of campus activities since they are interviewing technical positions, the rest of the brush over.
The resume template
You can follow my wechat official account “Code Whim” and reply to “resume template” in the background to get the WORD version of the resume
You can fork to his lot in warehouse, or git clone https://github.com/youngyangyang04/Markdown-Resume-Template.git can then be downloaded to a local according to their own situation to change.
This template allows you to modify your resume from time to time
Use the word mastery carefully
Fresh graduates or just graduated programmers in writing resumes, remember not to write proficient language, if really learn very well, recommend writing familiar.
However, some students may only use some languages such as go or python to write some small things, or understand some language syntax, directly write familiar with C++, JAVA, go, python, this is also a big no-no, if C++ is more familiar, it is recommended to write familiar with C++, JAVA, go, python
Proficiency > familiarity (recommended) > understanding (recommended)
Also, be prepared to write that once you are familiar with C++, inheritance, polymorphism, encapsulation, virtual functions, some of the C++11 features, STL will be asked.
So the language you’re familiar with on your resume is important when you’re preparing for an interview. You can forget about other languages, and interviewers are usually looking at just one programming language in an interview.
If in doubt, never put it on your resume
Don’t overload your resume with content just to make it look rich. The more content you have, the more points you will cover in the interview. Highlight just a few of your skills, not everything.
Think about how the interviewer is going to start the interview with your resume and ask questions. If you put everything on your resume just because you want to show that you know a little bit more, you’re opening a big hole for yourself.
For example, if you have only deployed an Nginx server and you are familiar with Nginx on your resume, the interviewer may start to ask a lot of questions about Nginx. If you are overwhelmed, you may say that you have only deployed nginx server, but I do not know the underlying implementation. Imagine how awkward that must have been.
At the same time, try not to write 100,000 + lines of code on the resume, which will excessively raise the expectations of the interviewer, first is 10W+ lines of code, it is impossible to verify.
And it certainly raises the interviewer’s expectations and the range of questions they can ask. It’s like telling the interviewer I can write code, just ask.
Then, if there is no focus on the resume, the interviewer will start to ask a lot of questions, and I’m afraid that students will not answer well.
How should project experience be written
Highlight your contribution to the project experience. Don’t just describe the project once. Highlight your contribution, whether it’s features added or performance enhancements, and finally talk about the benefits, such as how many people used the feature, such as how many times performance was increased.
In fact, a common problem of many students is that they cannot tell the difficulties of their projects in the interview. They have written a lot of project experience and the use of various framework databases, but they cannot answer the difficulties in their projects.
Some students will say in mind, their own projects do not have any difficulty, is to do according to the function, encountered can not configure will not adjust, baidu.
In fact, most people are like this when they are working on projects. Not every project has any difficulties, but why others can say one, two and three on the difficulties of the same project experience? Let’s talk about it
When doing projects, we always keep sensitive to the difficulties. Many of us solve a problem with great pains and then forget it without taking notes. At this time, if we record our thinking process in time, it is an important material in the interview, and it is very important to develop this habit
Many students complain that their project is not difficult, in fact, it is not, find a point in the project, dig deep, you will encounter difficulties, solve it can be used in the interview, for example, using Java to complete the project, in the deep dig Java memory management, see if it can reduce some virtual machine memory pressure.
Therefore, most of the time, it is not their own projects without difficulties, but their own inadequate preparation
The interviewer will certainly ask about project experience, so not every interview is to take the initiative to ask about the highlights or difficulties in the project, at this time we need to take the initiative to talk about the difficulties in our own project.
For example, our project is a set of distributed system. When introducing the project, we take the initiative to say that the difficulty of the project is the consistency of distributed data.
You know the interviewer is going to ask you how do you solve data consistency? If you have a good understanding of how data consistency protocols work and how they work, you can talk to the interviewer.
We highlight the difficulty of the project in the resume is the consistency of the data, and we have carefully prepared the consistency agreement, data consistency related knowledge, waiting for the interviewer to ask, this is a good resume, not a resume that talks about everything and knows nothing.
The interview lasts for 30 minutes or one hour. We will talk about the difficulties in two projects, which not only highlights our technical depth, but also the difficulties in the project are best controlled by ourselves, because this is the key to change passivity into initiative.
A really good resume is when you hand it to an interviewer, you know what the interviewer is going to ask you, and then you can lead the interviewer to the area that you are most familiar with, so that you can take the initiative.
You don’t let the interviewer ask you a lot of questions that you don’t know. A resume with a lot of content, a little bit of everything, will magnify the range of questions that the interviewer will ask, and if you go a little further, students will not be able to answer, you may not have a chance to interview, I hope you know that.
The Importance of Blogs
You can add your blog address, Github address, or even Twitter (if you post a lot about technology)
Through blogs and Github interviewers can quickly judge students’ enthusiasm for technology, as well as their learning attitude, so that interviewers can quickly understand students’ technical level.
If there are a lot of high-quality blogs and beautiful Github, the interview site will not perform well, and the interviewer will know this through the blog. You can see the importance of recording and summarizing.
You don’t have to be a technical genius to write a blog. Everyone can write a blog to record their gains. You can write a technical blog for every knowledge point (the questions you have brushed, the knowledge points you have prepared for the interview, etc.).
If you have never written a blog before, I suggest you register for a blog now, either CSDN or Blog Park.
It is not very recommended to build their own blog website, because the traffic will be particularly low, it is not easy to expose themselves, improve their popularity.
The interview only lasts for 30 minutes or an hour. How can you better present your skills to the interviewer? Blogs and Github are all good choices
conclusion
The key of good resume, and colleagues also try not to spend too much energy on a resume, a good resume and interview skills are the icing on the cake, really get experience offers by or, hope that through this article, we can review in your resume, find where is insufficient, more ready to practice before the interview.
I believe that many of you feel at a loss when facing nearly 2,000 questions. I spent half a year sorting out the Github project:Leetcode brush problem guide. There are 200 classic algorithm topics brush topic sequence, with 60W words of detailed illustrations, summary of commonly used algorithm templates, and difficult video explanation, according to the list of a brush can be! Star support a wave!
You can follow my video on B
Look for me on station B
In addition, I have arranged the algorithm articles of “Code Random Thoughts” in accordance with the order of brush questions from shallow to deep, sorted into a book, and sorted out the PDF version successively
First above:
Download it and you’ll find it too late!
BAT programmer’s algorithm learning manual open download!
If it helps, give it a thumbs up.