Every March and April is the golden season for job hunting. How to write a resume? How can you improve your interview success rate? This article teaches you how to write a technical resume that the interviewer likes and is authentic. If you are a current student, you should read this article carefully. It will allow you to graduate with the best technical resume possible.
Play a little game first. If you encounter the same situation when writing your resume, please Choice:
1. I don’t know what recruiting companies value most, academic qualifications, technology, or projects?
2. It is customary to write long working years. For example, if you graduate in 2016, you need to write 2 years of work experience. For skills such as
3.php, Java, Python, C/C++, no matter whether you are familiar with them or not, you must write "proficient".
4. Project experience and work experience have been mentioned briefly or in a long way.
5. I feel that there is no difference between a technical resume and an ordinary resume. Just follow the template and write it.
6. Every time the interviewer says "Do you have anything to ask" at the end, I feel very embarrassed.
Which one did you choose?
Select 0-1, please click the cross in the upper left corner to close this page.
Choose 2-3 items. Your previous resume may have been self-indulgent and needs some antidote.
Choose 4-6 items. For severe patients, please digest the following content carefully.
In fact, most people will encounter the above situations when writing resumes and applying for jobs.
Some people do not understand the interviewer's needs and want to write a comprehensive resume, but after writing it, they have no focus and do not know it. In the end, the resume falls into the sea;
Some people want to write it in a comprehensive way. Present a better version of yourself in your resume, regardless of whether this "self" is real: extend your working years and write all your skills as proficient. This kind of self-promotion can only lead to embarrassment during the interview;
Some people are skilled and willing to work hard, but their talents are not recognized and they cannot find a more effective channel to let more big companies know about themselves. Many opportunities for advancement were missed. In fact, this can also be improved.
This article will teach you how to avoid these common "pitfalls" in resumes. Write a technical resume that the interviewer likes and is authentic.
If you are a current student, you should read this article carefully. It will allow you to graduate with the best technical resume possible.
01“This article is not suitable for experienced drivers...”
Today’s topic is programmer’s interview skills. For this topic, we target readers who are looking for jobs in the Internet industry or software industry, and they are mainly fresh graduates and job seekers within three years of graduation. Because for experienced job seekers, their approach to hiring can be very different. For example, he will pay less and less attention to resumes and rely more on reputation in the industry and recommendations from senior engineers within the company.
##02"Is the basic information that simple?"
First is the basic information, everyone will definitely write it down. Include:Name
Age
Working years
education
##cityContact information: mobile phone + email
There are a few more things to note here :
First of all, in the basic information, we will see that many students will deliberately write down their working years very long. For example, if you graduate in 2016, you will selectively write down two or even three years of work experience. What I'm saying is that this is completely unnecessary.
Because first of all, this will make the recruiter very confused, where did your previous work experience come from? Of course, most of them may count internship experience as work experience, but in fact, this part will be discarded during the interview stage.
So the principle we hope is to be as realistic as possible and not make false statements. Don't deliberately advance your graduation date to increase your working years. Even if this will help you get through the automatic screening process of resumes, there is still a high chance that you will be screened out during manual screening or interviews.
In addition, for some friends who have changed careers, if you are not originally in the computer industry, and it is very different from the computer industry, such as car maintenance, then you can simply summarize it in one sentence. Just to let your recruiter know that you were not engaged in the computer industry in the first few years after graduation, and then clearly write down your work experience and working years in the computer industry.
As for contact information, there is no need to mention your mobile phone number. Use a commonly used email address as much as possible. If you have your own personal website, you can also choose to use the email address of your personal website. However, the name of the email address should be as short and easy to recognize as possible. For example, the email address with 1 and L mixed together looks very painful.
03“Work and internship experience are very important”
The second part of the resume is work and internship experience.
Company Name
Position
##Time
Detailed work
This part is very important. Whether you are a fresh graduate or someone who has worked for several years and has experience, in fact, this part of the content is what recruiters value most. In this part, at least you must prove that you have gained a lot from your previous internship or job and have experiences that are very helpful to your personal growth. Such experiences are the most valuable. In addition, work experience should be avoided as much as possible. If there is a gap, you will definitely be asked during the interview and you need to have a more reasonable explanation. For example, if you go abroad to study, or something like that, and then take a break of one or two years, there is no problem with this. The second point to note is that a company only needs to write one column. Under this column, you can list items one, two, three, and four to describe in detail what you are doing and the technologies you have learned in this company. But avoid writing many columns for a company. Even if your position in the company has changed, you can only write one most important position, or one most senior position. For the job description, you need to introduce in detail the products you have developed, as well as some technologies used in developing this product, the tasks you are responsible for, and indicate whether you have led a team and what the size of the team is. As an individual, whether you completed the project independently or as a collaboration between two people, this is a very detailed matter, but it must be written clearly. There is no need to be too wordy, but every point must be in place. The last point is what I mentioned just now, mark each item with a short entry one, two, three, four. This will allow the other party to see very clearly some of the key points you have gained and catch their attention. When describing the project, use as many keywords and technical keywords as possible. For example, in this project I used Mango DB, Laravel, or some frameworks commonly used in the front-end and back-end, and then wrote it in the project description. For fresh graduates, if they have no work experience, internship experience is very, very valuable. Because most companies currently are relatively utilitarian, they hope that the fresh graduates they recruit can get started directly and integrate into their teams as quickly as possible to form combat effectiveness. The company that really wants to take it over and cultivate it for one to two years should be a very large enterprise, which is a relatively rare situation.04"What kind of project experience is convincing?"
The third part is usually project experience, divided into:
Project Name
Project Description
Responsibilities
Technology used
Achieved effect
Project experience, generally include your previous work or internship, as well as experiments in school I did some extractions from the project that the teacher did in the room. Choose the best projects among them, the ones that best represent your true level. For example, there is no need to post big assignments in some courses. Of course, it is also possible if the code volume of this large job is very large and it has a certain degree of popularity. In some cases, project experience and work experience can be combined. For example, if you have very rich work experience and the projects of each job are very clear, you can definitely combine these two contents. And for fresh graduates, if they have no work experience or internship experience, the project experience must be written very carefully. In the description of the project, there are three points that we value most. The relevance between this project and the position you are applying for. The popularity of this project in the entire technology circle. The last thing is whether this project has some data that can prove that you have done it and let you gain something. Going back to the project experience just now, we actually need evidence, and the best evidence is your GitHub code link, or an online version of your project—maybe a website, Maybe a demo you showed. As long as there is such an effect, for the person reviewing the resume, he can see the technical level of the project at a glance, which is a bonus that can add a lot of points.Choose familiar projects. Be sure to choose familiar projects. If you enter the interview for a project that you should write yourself, it is very likely that the interviewer's questions will come from the content of the project you wrote, so don't write those projects where you are ambiguous or just a bystander. If you have only seen it, or if you are unable to go into it in depth, it will be embarrassing to be asked.
The last thing to note is that your project description must be written in very standard technical language. Even when talking about some technical keywords, they must be capitalized where they should be capitalized, and lowercase where they should be lowercase. This actually reflects a person's level of professionalism.
05" Proficient in PHP, Java, Python, C, = Haha"
The fourth part is usually a list of skills.
Notes:
Seek truth from facts
Adjust appropriately according to the target position
Number proof:30000 lines of code, 3 projects-PHP
Project evidence:thinkphp frameworkdeveloped its own set of cms
We are introducing it after After experiencing your own projects, you usually write a list of skills. This skills list is usually modified based on the position you are applying for. If you apply for a job as a PHP development engineer, put your PHP-related skills at the forefront as much as possible. These key points can catch the attention of potential interviewers.
The first thing you need to pay attention to is still seeking truth from facts. Try not to write the word "proficient" as much as possible. You can write "familiar" or "understanding".
The skill list could also add some evidence of digital assistance. For example, after Php, write: I once had 30,000 lines of code experience; I have worked on three projects, and the three projects can also be verified in the previous project experience. In addition, there is some other evidence. For example, I developed my own set of cms using the thinkphp framework. These are actually very good jobs that can reflect your skill level.
06“Things to avoid in educational experience”
There doesn’t seem to be much to say about this part of educational experience. Basically, you just have to write clearly the associate degree, bachelor's degree, and master's degree, as well as the school, major, and time.
Be sure to seek truth from facts, there is no need to make lies in this regard. Although many companies may look at schools and academic qualifications, from my understanding, they are just choosing a faster screening method. And this is something we don’t pay special attention to at the PHP Chinese website. We don’t really care about academic qualifications, or schools. What we value more is your previous work experience or your own project experience, and other things that prove your strength and ability.
In terms of educational experience, everyone should try not to emphasize self-taughtness. Because even if you didn't go to college or college, or graduated from high school, but you are very interested in computers and work very hard, you can prove it with projects. But don’t emphasize self-taught here, because the probability of self-taught is very, very low. It is very difficult to become a very capable individual by working completely on your own. Many companies are very afraid of this small probability. Basically Filter will be selected.
The last point is, try not to write about your training class experience. Because most of the current offline training is relatively rough, the improvement in skills that can be obtained is also very limited.
07"Don't underestimate additional information"
The sixth point is basically the last part of the resume, which will introduce a lot of other additional information, such as Talk about a personal website or a link to GitHub. There are many things to pay attention to here.
First of all, if your own personal website or technical blog is not rich enough in content and only has one or two logs, there is actually no need to post it.
The second point that needs to be emphasized is that GitHub is very, very important. At least when our PHP Chinese website is recruiting, we will first look at some records on GitHub, such as original code projects, and even some specifications of the code, including some submitted records. If your GitHub repository is empty and most of it is forked other people's code, then don't put it there, which can avoid a lot of waste of time.
If you have download links for other original project codes, you can actually put them here. However, if it requires the recruiter to spend a lot of time looking at it, no one will usually look at it.
When listing any additional information, append its highlights. For example, on your own technology blog, you can write 150 technical blog posts, and the number of visits that month reaches 1 million. This is to attract others' attention to your technology blog through numbers.
In technical resumes, do not include non-technical related information, such as volunteer activities and club activities that you have participated in, unless it is a technical club. However, unless technical societies are well-known, they are generally of little value.
Finally, don’t write your own personal description. Technical resumes are relatively simple. We only value your technical level and your project experience. Other personal hobbies of yours, such as what sports you like, are really not particularly important.
The last point is, if the position does not require you to write down your expected salary, don’t write it down. You can go to the site to negotiate. It is possible that if you write, you will miss some interview opportunities.
08"Private information - technical social networking!"
Finally, I will introduce some things other than resumes, which I personally call " "Technology Social". In fact, it is a way for you to get some job opportunities without a resume. You need to increase your visibility in the technology community through the following channels.
When you become famous, many companies will take the initiative to contact you. I know that many HRs in large companies will hang out on GitHub, and then crawl to users with very high local star rankings, and then proactively contact them by email and invite them to come to the company for interviews.
This part of the content requires investment of time and personal energy. For example, in college, you can choose to maintain your own GitHub repository starting from your sophomore year. You can create more projects on it, and then publish some of your original code, including PRs submitted in open source projects you participate in.
You can also use GitHub to build your own technology blog, and put all the technical accumulation and gains from your sophomore, junior, and senior years on it. When you actually graduate and find a job, In fact, you basically don’t need a resume. The hundreds of commits on GitHub are the best proof for you.
There are also technical communities like Stack Overflow. My personal suggestion is that after you have some very in-depth technical understanding, you can try to answer some novice questions. This will also improve your personal reputation and skills.
The other content is nothing more than some technical documents you have translated, which are very famous foreign technical documents. In fact, on GitHub, you can join many translation groups. There are also content you contributed to some online education websites, such as php Chinese website, where you contributed some text tutorials, or posted some self-recorded videos on some online education video websites, such as Publishing your own courses in the online courses of PHP Chinese website is actually a very good proof.
09"Frequently Asked Questions!"
The content of the third part is some common questions that I can think of.
The first thing to note is that your resume must be short. Streamline your most important content to one page; streamline your most important keywords to the most prominent position.
Never add long paragraphs of content. Long paragraphs of text are a taboo on your resume. Don’t include too many words about personal feelings and experiences, as no one will really read them. When HR or engineers receive many resumes, their time is very limited. If you can't catch their attention in a short period of time, you're wasting a great opportunity.
The second point is about the order of information. First of all, if you are a fresh graduate, you need to highlight the school and just combine your educational information and personal information. If you are not a fresh graduate, the most important thing is your work experience - your previous work, the length of time you worked, whether the core content of the work is related to the position you are applying for, and some data evidence from your work. You can put some work experience directly under your personal information.
When submitting your resume, you should make some adjustments based on the position you are applying for. For example, adjust the order of some desires, the order of technical skills, and the description of key keywords in previous work experience, and try to focus on the application requirements as much as possible.
The format of the resume should be pdf as much as possible, so that the versatility will be better. Then don’t post photos unless you are very beautiful or the position requires it. Basically, the positions I have seen do not require photos.
Finally, if you submit to a foreign company, try to have one page of English resume and one page of Chinese resume, because the person interviewing you is likely to be a foreign engineer.
In addition, if you choose a company, you can conduct some appropriate research on the company's products, including the technologies used. You can also prepare a brief technical analysis of the company's products and put it in your resume. . Of course, it is basically not used, and more may be used in the interview process.
This is some of the content I will share with you today. Because it is relatively concise, it may not be particularly comprehensive in many places. You can raise any questions you want to ask or topics you want to discuss.
10"User Question"
Question: After learning the basics, how do you find a good project to do?
Answer: After learning the basics, you can start with some small projects. If you want to have a project that can be taken out and proven, it is best to go to GitHub to find some open source projects, take a look at the issues raised by others, then find some that you can fix, and then try to raise some PRs, even if they are rejected. Rejected. I think after these few exchanges, it will basically be accepted. This is a very good opportunity to train yourself.
Question: What aspects do companies value most among fresh graduates? Internship experience or something else?
Answer: Our company, for example, values more internship project experience and learning ability for fresh graduates, including their ability to truly solve problems. What is not particularly important is your current technical aspects. Because after coming here, it takes a long time to get in touch with the team. During the run-in process, there will also be senior engineers who will lead some and share some experiences.
Question: It feels like the interview is over. The interviewer said: I have finished asking my questions. Do you have anything to ask? This is the most embarrassing time.
Answer: In fact, the interviewer is also very embarrassed at this time... He may not have anything to say, but just wants to find a way to end the interview. In fact, at this time you can politely ask some questions about the company's products or R&D technology. If the interviewer happens to belong to this product line, or is very interested in this technology, you can discuss it with him in depth, but don't presume to make some suggestions that you don't particularly understand.
Related articles:
2017 Recruitment Season: Super summary of PHP interview questions!
2017 Recruitment Season: How are the salaries of high-end PHP talents?
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
