After working for many years, the author interviewed many companies, interviewed many people as an interviewer, and read many resumes. Many small partners encounter the following two situations in the process of finding a job:
I have invested in many companies, and very few invited interviews; during the
interview, I was dumb when asked by the interviewer.
A large part of the above reasons are due to the problem of the resume. This article will discuss with you how to write your resume based on your own interview and interview experience. Let's analyze some resume materials first.
Video analysis: engineer skills, interviews, how to shape resumes, and get offers easily
Tencent T2.3 personal experience sharing, the way to get Tencent offer
Resume One
This is the resume of a graduate. What are the problems with this resume?
analysis:
In the resume, I wrote a project that I did. In the project description, the project was described as RPC and distributed network framework. From the project description, where does it reflect that the project uses RPC framework and distributed? Not to mention that it is useless, even if it is used, it is generally difficult to withstand the interviewer’s questioning on distributed issues during the interview according to the experience level of most freshmen. This is very easy to dig into the interview. The general school recruitment or the project requirements for the corresponding students are not too high, but I write these "distributed", "RPC" and other high-level terms in my resume. If I don't actually master it, I can only bury myself mine.
In addition, the job seeker’s project is a network communication library, but the communication protocol is not its own (Protobuf), and the network library is also someone else's (Muduo). Does this project have its own things? Generally, as an interviewer, it is understandable that the graduates do not have much project experience, but if you use other people's things to add a shell and write them in your resume, it will not make much sense. If the student tries to design a communication protocol by himself, even if the final implementation is not very good, the interviewer may like it very much, because it integrates his own creation and thinking; stepping back, it is also possible to use protobuf, if you can It is OK to make it clear about the principle of serialization and deserialization of protobuf and the structure of the library.
interview result:
The student was beaten by the interviewer during the interview because of this project, and he returned home unscathed.
Resume two
analysis:
After I first saw this resume, I guessed that very few HR or headhunters contacted the student for an interview. Later, I confirmed with the client and it was not. The problems with this resume are as follows:
There are many technology stacks listed in the resume, such as Linux, Shell, Python, C++, Golang, Django, Flask, Bootstrap, JQuery... Does the interviewer really master so many technologies? In addition, the job search goal is "back-end development". Although HR may not know that Bootstrap, vue, etc. are front-end technologies, does the technical interviewer know? You are a back-end job hunter, why do you write a lot of front-end technology? Reflect your full stack? According to the author’s age and work experience, many techniques are only understood or used, but not necessarily mastered. Not to mention that the interview is easy to be asked and cannot be answered. The most important thing is that this resume makes people think that the job applicant does not The field of his expertise. To put it bluntly, I know everything possible, but I have not mastered everything. So most companies just pass it when they see such a resume.
The job search goal is written as "back-end development", and the location is not conspicuous. Secondly, the term back-end development of the job search goal is too general. This student originally intended to apply for C++ back-end development, but in this way, php, Java, golang, python, etc. Doesn't it count as back-end development? Therefore, it is recommended to narrow the scope of the job search slightly.
interview result:
There is basically no interview invitation.
[Article benefits] C/C++ Linux server architect learning materials plus group 812855908 (data including C/C++, Linux, golang technology, Nginx, ZeroMQ, MySQL, Redis, fastdfs, MongoDB, ZK, streaming media, CDN, P2P, K8S, Docker, TCP/IP, coroutine, DPDK, ffmpeg, etc.)
Resume Three
analysis
Classmates wake up, you have graduated and worked for three years, and you also posted your master's thesis to your resume... The problem is, you still have the word "demo" in your graduation thesis. Maybe your graduation thesis won an award, but most HR Neither the interviewer nor the interviewer can understand the industry terminology in it, but they must be able to understand the word "demo". The demo makes everyone feel as if they can't get up to it...
This classmate has transferred to the computer industry as a non-science class (animal science) I have successfully entered the industry for three years. Why should I put my undergraduate major in such an obvious position? Is it to emphasize that it is not easy to change careers and work hard? --! If you are not from a major or graduated from a prestigious university (Tsinghua University, Peking University, Fudan University, Wuhan University, etc.), especially if you have graduated for a few years, don’t put your degree and graduate school in such a prominent position, you can put it Before "Hobbies".
The job search intention is also the same problem; the
description of technical expertise is not good. Generally, we look at the recruitment information of employers, and write general technology first and then write professional field technology, so general technology refers to algorithm data structure, operating system Principles, network programming, etc.; professional technology refers to languages such as C++, Java, golang, python, various frameworks, and open source software.
In addition, if you are not particularly handsome, it is not recommended to put your own photos...
Resume Four
analysis
I was really drunk after reading this resume.
Brother, I know you don’t have the project experience and technology that you can get, but you are looking for a development position. You don’t want to write your experience of raising pigs in your resume. Although some large factories feed their employees themselves, the procedures After all, development and pig raising are two different things...
Resume Five
analysis
The project description of this resume is too detailed, especially the business part, which feels like a project bidding document or a project pre-sales plan. . If you are looking for a technical development position, and the next company you are looking for is not the same type as the project in your resume, then write the project business content briefly, and write more technical content when describing the project experience... To be honest, this resume is suitable for applying for a project manager, especially a project manager of the Highway Bureau...
Resume Six
analysis
This is the resume of a elder brother. The eldest brother has been working for 13 years. Please readers to see if the project experience description has the level of 13 years? The description of this project is too detailed. First of all, the company's commercial and technical secrets may have been leaked. . . . . Secondly, like the resume 6 above, can’t you write more technical content and less business content? Resume 6 can apply for project managers, and this resume can apply for product managers... The requirements are too detailed, you are sure you are looking for Back-end development...
Resume Seven
analysis
It is often said that the cleanliness of a copy can reflect the meticulousness of a person. There are two problems with this resume:
The classification of personal skills is very confusing. For example, what is the relationship between the underlying principles and C++ applications in "Mastering C++ applications, understanding the underlying principles, and some of the features of c11". It can be written separately. In addition, C++11 has been widely used. Don't write if you are not familiar. How much is familiar with the familiar part? Do you tell the interviewer that you don’t have a good grasp of this aspect? In the original interview, the interviewer might not ask. When you see this, you may not help but ask a few C++11 things; the "synchronization" in "multithreading, synchronization, ipc communication, etc." is not about multithreading Is it? Isn't the strategy mode, singleton mode, and factory mode in "familiar with design mode, strategy mode, singleton mode, and factory mode" one of the design modes? Why are they juxtaposed with design patterns?
The punctuation in your resume will be a comma in Chinese, a comma in English, and specific nouns like C++ and Linux, capitalized for a while, and lowercased for a while, resulting in messy layout.
Conclusion
The methods for success are the same, and there are many odd ways to make mistakes. Due to the length of the article, no more resumes will be posted. After reading the above seven resumes, do you have a similar situation? Here is a summary of the precautions for sending your resume and how to write a technical resume.
1. When sending your resume, if you send it to the mailbox of the company or HR, you must clearly write your intention in the subject of the email, usually [XXX job application or job application XXX position], such as [Zhang Xiaofang application back-end C++ development position], otherwise the email is very Easily ignored or filtered by the email spam filtering system, the resume cannot reach HR or the interviewer at all; try to write clearly the content of the attachment in the file name of the resume attachment, such as [XXX Job Search XXX Position].pdf/doc/docx resume , Such as [Resume of Zhang Xiaofang's application for ByteDance senior developer].pdf. Remember that the file should not be named like "New Folder.pdf", "New Compressed Package.zip", "1111.doc", "Resume.pdf". After being downloaded by HR, it is difficult to find on the computer and give it to others Reading your resume causes inconvenience.
2. If you send your resume to others through IM tools such as WeChat, QQ, etc., in order to facilitate communication during job hunting, you must not set your WeChat nickname, QQ name, and avatar into non-mainstream names that are not easy to identify, such as WeChat name settings A blank or blank avatar or a name that is hard to search or at. For example, the author once saw an interviewer set his avatar to be a sow head. I originally planned to chat with the job seeker a few more words. I felt uncomfortable seeing this avatar and had to give up. Everyone is very busy, especially when there are many candidates, no one wants to spend too much time on you because of this kind of problem. Of course, if you have a special hobby for those special IM nicknames, it is recommended to change them to normal ones during the job search, and then change them back when you find a job.
In the adult world, no one will deliberately accommodate you. To facilitate others is to give yourself opportunities.
3. Do not include ill sentences or wrong punctuation marks in your resume. In particular, do not write some important technical terms incorrectly. There should be a space on the left and right sides of English words or numbers that are not at the beginning or end of a line.
4. Write your contact information clearly in the first part of your resume. Don't write too much non-important information. Generally, write your name, phone number, email address, gender, age, and job application intention. Don't write anything like height or weight. No one is interested in your height and weight... In addition, don’t leave some contact information that creates a split impression. For example, your name and email address obviously do not feel like a person. If your name is yourself, your email contact address is like yours Wife's...
5. If you are not from a major or from a prestigious school, especially non-graduate students, do not put your educational experience in a prominent position on your resume. It is generally recommended to put your educational experience at the end of your resume. Educational experience must not be faked.
6. Position the position you are looking for clearly. For example, do not write the words "software development" and "back-end development" in your job search. This kind of job search intention description is too broad, which is not conducive to corporate screening and reduces your gains. Opportunity for interview invitation. It is recommended to write specific job descriptions such as "C++ software development", "JAVA back-end development", "Linux C++ back-end development".
7. When writing your own technology stack, you should distinguish clearly according to the type of technology, and try to divide unrelated technologies into different items. First write general technology, then professional technology, and finally business technology. Here is an example:
- Familiar with commonly used algorithms and data structures;
- Familiar with multi-threaded programming technology, familiar with common thread synchronization and process communication technology;
- Familiar with network programming, familiar with TCP/IP communication principles, familiar with common protocols such as HTTP and FTP;
- Familiar with C/C++, familiar with C++11, good object-oriented thinking and coding style;
- Familiar with common operations of Linux system, proficient in using gcc/gdb and other development tools under Linux;
- Familiar with database principles such as mysql and redis, and familiar with common database tuning techniques;
- Familiar with message middleware such as kafka and RabbitMQ;
- Familiar with financial trading systems and have experience in block trading system development.
8. Work experience is recommended to be divided into work experience and project experience. Work experience clearly writes in which company you hold a position from a certain month to a certain month. The project experience introduces your specific project experience. If you deliver The business of your next company and your project is a peer or similar industry. You can write a little more project business introduction. On the contrary, you can roughly explain the background and business content of the project. Write more technical description and write clearly that you are in this project. What kind of technology has been used to solve or achieve or achieve what effect, or what benefits the company or team brings, or write about the process of tackling the technical problems you encountered in the project. Do not write something like "through this Project, I learned XXX", the company recruited you to work, not specifically for you to learn, you work for the company and the company pays you salary, do you want to pay the company tuition without taking the salary?
The technical description in the project should be converged according to the job search position, and try to write technical terms that you have mastered or familiar with, so that to a certain extent, you can introduce the interview topics to the technology stack you are familiar with during the interview; fewer things you are not familiar with Technology stack or technical terminology, so that it is easy to make mistakes during the interview, or even be at a loss.
If your work experience is not long, your role in the project may be responsible for a single service or some modules in a single service. At this time, you can write more technical details when writing project experience, such as network communication protocol details, queue data exchange The design details of the program, the details of the data processing of the program, etc.; but if you have been a senior developer for three years or more, when describing the project experience, you should rewrite your understanding of the overall framework or architecture of the project. The circulation process in each service, the role of each service, the structure of the core service, technical difficulties, etc. Never explain every technical detail like a running account.
When describing the technology stack, write about the company position or job intention you are looking for. For example, for a job search and development position, you should weaken some of the job descriptions of some tests, operation and maintenance or project managers you have done; don’t write something like the back-end development of your job search. It is based on technical terms such as MFC, QT, and VUE; when applying for a job in Java development, don’t capitalize your resume in C++, Python and other language projects or module experiences. In particular, don’t write about experiences that are not related to your position. If they exist, you can take them all over.
Do not disclose the confidential information of the previous company in the project description.
For the company you like, you should prepare a special resume instead of sending a resume everywhere.
9. If you have some outstanding open source projects or product displays that have been released and can be seen by the public, you can include the GitHub address, technical blog address or project online address in your resume. Some job seeker blogs rarely have high-quality originals, or GitHub's project engineering organization, code style is chaotic, and even only has a README.md. Don't write this in your resume. Most interviewers will open a technical blog or GitHub address when a job applicant has posted it.
10. Self-description or self-evaluation suggest to write something positive, work and study-related, such as optimism and learning, communication skills, organizational skills, teamwork skills, do not write insignificant, or self-exposing shortcomings description, such as love to play League of Legends, there is obsessive-compulsive disorder, love and people more real, etc.
Pay attention to the official account and share more Internet technology content you are interested in!
