Prepare a technical resume
Resume is your stepping stone into the interview, but also to the first impression of the company, so this is very important, must be done in this article, a good interview resume is the success of the entire interview among the most important, we should carefully prepare resume to ensure that the resume is not brushed.
A resume usually consists of the following parts:
- Basic information
- Professional skills
- Work experience
- Project experience
- Education background
1. Prepare a resume template
If starting from scratch takes a lot of time, the quickest and smartest way to start is to find a good resume template and then just fill out the information.
Resume templates are carefully selected, and some resumes are simply brushed off without reading the content. These resumes are visually offensive to the interviewer, making the first impression of the resume offensive to the interviewer.
There are two types of resume templates that are offensive:
-
One is the classic resume template, which is really classic, magic color scheme, plus the form type is the bottom of the resume type, basically throw it away at a glance, this kind of resume can be thrown into the trash in three seconds.
-
At the other end of the scale is the stylized resume template, which is designed to dazzle an interviewer with its colorful colorscheme. It’s also a 3-second resume that will sink to the bottom of the garbage heap.
These two types of resume templates are killer recruiters, and if you use them, you won’t be interested in giving them a second look. Interviewer to screen resume is efficient, clear, content, whether it’s HR or technology the interviewer wants to see effective information in the case of the most rapid, in your eyes of the so-called “visual effects” in others’ eyes is “visual noise” or “junk” vision, seriously affect the mood of watching your resume and looking for the rate of effective information.
2. Prepare personal information
The personal information section mainly includes name, telephone number, email address, and job intention. Of course, these four are mandatory, and the others are optional.
Here’s the point:
1. The blog: If there is no update for a basic blog or without making any contributions, then give the interviewer a feeling of in order to put up and put up, it’s basically with the interviewer said “the candidate usually don’t have a habit of”, so if there is a lot of long-term maintenance or blog must put up, It’s very useful if it’s of good quality. If it’s not, don’t put it in.
2 education: if your education is junior college, high school graduation and so on, but also write in the resume head to emphasize again, which increases the chances of the resume brush, if it is a graduate or 985211 degree can write, highlight the educational advantage, undergraduate degree in the field of technical interview basically stepping stone level, there is no need to write.
3 age: if it is an older programmer, especially in the pursuit of a low-end post do not write, an older programmer in the job search for a low-end post, that these years basically in place, can not work overtime, here basically this resume on the cool half.
4. Photos: good image can be posted, especially good image of the female program yuan, the other had better not stick, if you want to stick, it is best to stick the kind of PS over the very professional documents.
3. Prepare professional skills
For programmers, expertise is actually a technology stack. How to describe one’s own technology stack is a difficult question. For example, what is mastery? What is understanding? What is familiarity?
There are many different descriptions of technical skills, but here are just three:
- Understanding: Skilled in a particular technology and able to work under guidance, but unable to perform complex tasks or solve problems independently.
- Familiar with: used a certain technology, can complete the work independently, and can independently complete a certain degree of complexity of the work, there will be no big problem in the application level of technology, even understand a little principle.
- Proficiency: not only can use a technology to complete complex projects, but also understand the principles behind the technology, can re-develop the technology, and even be a contributor to the technical source code.
Take Vue framework as an example, if you can write simple pages with Vue and independently complete the development of some pages, but can not get rid of the scaffolding work of the company, nor can you independently complete a project with a certain complexity from 0, it can only be called understanding.
If you have extensive experience in using VUE, have the ability to independently complete a project of a certain complexity from 0, can completely develop without scaffolding, and have a certain understanding of the principle of VUE, you can call it familiarity.
If you have completed a highly complex project with VUE and are very familiar with the principles of VUE, have been a major contributor to vUE source code, or have made magic changes based on VUE source code (such as MPVUE), then you are proficient.
So there are two pitfalls that candidates often commit: the hybrid and the hybrid. These two pitfalls, which are heavily concentrated on new graduates and novices less than two years out of college, are characterized by overconfidence caused by a rush to express oneself and ignorance of the depth and breadth of technology.
First of all, if you want to apply for a Java backend, honestly write your Own Java technology stack, emphasize what you are good at, it is best to specialize in a certain area such as high concurrency, high availability and so on. At this time, some resumes must give themselves a play, they will not pile up, what reverse, cryptography, graphics, driving, AI should be reflected, the more mixed the better, this resume gives a person the impression is a don’t know anything.
Besides, a fresh graduate, out of the resume on all kinds of proficient, proficient in Java, proficient in Java virtual machine, proficient in Spring bucket, proficient in Kafka and so on, this resume is not careless cast over, This kind of genius who is proficient in all kinds of things in the university has been introduced into the big factory or foreign company by his seniors to do a certain Star focus on training, often see this is also half-skilled.
4. Preparation experience
The work experience itself doesn’t have to be written in ink. The interviewer is looking for length of experience, responsibilities at different companies, and experience with big companies.
So what resume is giving the interviewer negative marks here?
-
Frequent job hopping: four different companies in three years with no more than a year at each;
-
Perennial junior position: for example, after working for five or six years, I still finish some simple project development;
-
Sink company experience: in the recruitment technology, highest priority, such as a consortium BAT, TMD, even Microsoft, Google and other foreign companies, famous unicorn second, general Internet companies came in third place, is the work of small and medium sized Internet companies generally everybody doesn’t know by name, came in the last is the outsourcing and the experience of traditional enterprise;
(1) So, what if you’ve been job-hopping a lot? Wait an honest year in this company before jumping ship.
(2) If perennial junior post how to do? Look for promotions or work on high-profile projects in your industry, or write a personal project with some complexity.
(3) What should I do if I have experience in a low-ranking company? If it is a long time ago in the bottom of the company experience can directly not write, no one cares about your long ago work experience, if you are now in the bottom of the company, hurry to find a way to change jobs, not to go to a large factory, to an unknown Internet company is also a great victory escape.
5. Prepare project experience
Project experience is the most important for both social and school recruitment. In many cases, the success or failure depends on project experience. An ordinary undergraduate can overcome 985 through excellent project experience, and an employee of a small factory can also get an interview opportunity from a large factory. However, it is important to note that your project experience is well written. This is a great way to prepare for the interview portion of the interview, and it is also an important area for your resume to focus on.
Let’s start with the project gaps in your resume.
(1) Do not write a running list of project experience writing a running list is a common fault of most resumes, the whole thing down to tell the “what I did”.
Most resumes look like this:
Use Vue, Vuex, VUE-Router, AXIOS and other technologies to develop the front end of e-commerce websites, mainly responsible for the development of homepage, store details, commodity details, commodity list, order details, order center and other related pages. Cooperate with designers and the back end to restore the design draft.
What’s wrong with this description? In fact, it seems that there is no problem, but this kind of running account writing method is too much, completely unable to highlight their own advantages to show their ability. Project experience is the focus of investigation. The interviewer wants to know the candidate’s role, responsible module, problems encountered, solutions, results achieved, and the final summary and precipitation in a project experience.
The above description only shows what I did, so this kind of project description is almost meaningless because there is no valid information for the interviewer. Without valid information, the project description is basically worthless. If you haven’t had a big factory experience or an endorsement from a famous university, it is basically cold.
(2) Avoid stacking items
Accumulation project is no outstanding project experience this kind of phenomenon often appear in resume, candidates with Numbers hide quality disadvantage, but often backfire, the best project through column put two or three projects, excellent project might put a is enough, an extreme example, if one day the rain especially stream to write a resume, In fact, only one line of Vue. Js author is needed in the project, of course, he does not need to submit a resume.
Some items should not be included:
- Demo level project: many resume actually still put some imitation xx official website demo, this is full subtraction, some are pieced together some framework source code to make a toy project, there is no value.
- Rotten street project: the vue technology stack, for the most, because the popular video website of a certain course, cause a lot of fakes hungry yao, imitation qq music, Meituan, where to go, the same Java classmate is imitation e-commerce sites, copy the public comments, etc., ten resumes 5 copies of the same project, the interviewer will think you are.
- Low quality open source projects: a general rule of thumb is to keep low star projects to a minimum (except for projects with high quality code that are not popular), and to keep low quality projects to a minimum.
If you only have two projects, the best match is an in-house project with an open source project in the community. The latter gets a place because with your open source project, the interviewer can see your entire process through the commit. Things like engineering, commit, code, collaboration, coding, communication, etc. These are even more useful than interviews, and there’s no better way to show your portfolio than with open source projects.
(3) Do not put false items
A project has not done as long as the experienced interviewer will know that if you really rely on fake projects cheat the interview, then the company will probably have problems, talent control is not good, you can imagine your teammates are what level, in this kind of company big growth value is not big. Ok, if you say that there is no project to write and I have to fake it, then you should think about this.
For example, if you say that you optimized the first screen performance of a front-end project to reduce the white screen time, the interviewer will dig into the performance optimization question to see what the candidate is actually capable of:
- How are your performance optimization metrics determined? How much shorter has it been on average?
- How is your performance measured? There are two main methods of performance testing which do you choose?
- According to what indicators are you optimized?
- In addition to these optimization methods you said, have you ever thought of solving them through XX?
- Have you encountered any practical problems with this optimization method? Have any further tests been done?
- Let’s say you have a situation like XXXX, would you optimize it this way?
The logic of the interviewer’s multi-layer inquiry is as follows: understand the background -> understand the scheme -> dig the scheme -> simulation scenario
Must first understand how your performance optimization index, then need to know you are such a test index, how to optimize the again, then put forward some other solutions to investigate your knowledge reserves and scheme of optimization scenario decision-making ability, and then simulate a other business scenarios, to examine your skills migration ability, See if you know something about an area, not just a project.
If you’re going to be able to respond effectively in an interview, it’s going to be someone who has a certain amount of knowledge in a particular area, not someone who can just get by on a random project.
(4) Qualified project experience
Qualified project experience must include the following:
- Description of project
- Personal responsibility
- Project the difficulty
- The work
If you are not afraid of too many words, you can also selectively add solutions and selection ideas, but due to the space limitation and preparation for the interview, it is not recommended to write too much.
The purpose of a project summary is to make the interviewer understand the project. Not everyone will have done the kind of project you did, so you need a brief summary to make it easier for the interviewer to understand.
Personal responsibility is to tell the interviewer about your role in the project. Are you a leader? Dominant? Be a follower, assess your role in the team by what modules you are responsible for and how much work you are doing.
The purpose of project difficulties is to show the interviewer the technical difficulties you have encountered so that you can have a series of discussions about the project later in the interview. The interviewer needs to see what you accomplished with the work described above, and it’s best to talk about it in numbers, such as visits, screen time, etc.
This time also long of avoid by all means, write down all the technical details, even wrote a journey is a no-no, on the one hand, too much space can cause visual clutter, on the other hand, the interviewer wants to see is a resume, not a technical summary, the interviewer will face hundreds of resumes don’t have that time to see your long, long can in the interview.
The best way is to write a simple and clear line, anyway, when the project will be asked, then tell the prepared content to the interviewer, master the initiative of the interview is to start from the project experience column.
6. Other
(1) Educational background
This year’s unripe can write a bit more detailed, for instance grade point rank how, have outstanding course, the society enrol do not write too much, simple enter a school time, school, major can, and write highest record of formal schooling can, do not have to begin to write record of formal schooling running account from junior high school, no one sees.
(2) Matters needing attention
Technical questions are often considered “talk is cheap show me the code.” Your self-assessment takes up little or no space and is a distraction for the interviewer.
Resume cover don’t: This is one of the most common ways resume creators try to trick their users into paying for a cover, and I’ve never seen one in any industry, not just the Internet.
Certificate is not recommended to write: fresh students can consider getting a six certificate, for social recruitment, list a pile of certificates or even subtracting items, you also know all kinds of domestic certificates, is how not confident to reduce to rely on a pile of certificates to prove their value.
Don’t use skill charts: In the first place with 90 points, 80 points to evaluate their own have no persuasive technology itself, and it can’t be that accurate, and what is 90 points, what is the public opinion doesn’t have a 80, with the comparison of general so familiar, proficient in general description, don’t play, the interviewer or HR is not so much free time to understand your chart, Honestly describe your technology stack in the most generic and efficient way.
One-page resume: Programmers, not designers, sometimes need to show their work. If a resume is longer than one page, something is wrong. Too many descriptions of projects and technical stacks take up too much space.
Because I want to express the content is too much, so this article is divided into two parts, the second part of the interview preparation, is constantly updated ~
Front-end learning is a long way to go, and if you choose the front end, you have to work hard and don’t give up halfway. There are a lot of things to learn at the front end, but interest is the motivation to stick to it. Come on together.
Front-end learning content is complex, online information is intermingled with good and bad, it is not easy to sort out on their own, in order to help want to go all the way to the black friends on this road, especially sorted out the “front-end engineer learning advanced information”.
Content includes HTML, CSS, JavaScript, ES6, computer networking, browsers, engineering, modularity, Node.js, frameworks, data structures, performance optimization, projects, etc. (The data in this paper are suitable for 0-2 years)
It includes questions asked by first-tier Internet companies such as Tencent, Bytedance, Xiaomi, Ali, Didi, Meituan, 58, Pindoduo, 360, Sina, Sohu and so on, covering the primary and intermediate front-end technology points.
The full PDF is free to share, just like it,[Click here to get it for free].
Front end test summary
JavaScript
performance
linux
Front-end data summary
