How can a technician enhance the interviewer’s impression of you before the interview?

A resume is a personal statement that reflects your personality in relation to the role of the target position. The purpose is to praise yourself, but not to blow your own horn.

As the head of r&d of the company, in the past six months, I have seen a variety of developers come to interview every day, including some experienced developers and interns who just stepped into the society. I can really feel that people pay attention to the interview process, but not too much attention to their resume.

So, after reviewing nearly a thousand resumes, I decided to create a guide based on my own experience to help you grab the attention of an interviewer before a job interview with a programmer.

In “fine” not “many”

A lot of people are confused about the range of skills they have when it comes to resumes.

In fact, personal skills show in the “fine” not “more”, so much writing, will only let the interviewer feel that you “know a lot but not proficient” after reading, because after all, the interviewer is from this stage. It’s not absolute, but it certainly has more disadvantages than benefits when it comes to writing several technologies, frameworks, or programming languages that you’ve mastered.

If you still think more is better, be sure to categorize all skills, not by skill category (e.g., database, framework, or Web), but by your level of mastery (e.g., mastery, understanding, etc.)

Avoid spelling and grammar mistakes

An obvious spelling or grammar mistake on your resume can make an interviewer think less of you.

While a technology-related position may not have anything to do with a typo, it can change the way an interviewer sees you:

1. You don’t pay attention to details.

2. You are not proficient in programming languages.

If you have misspellings on your CV, you’re more likely to have misspellings on Slack messages, in emails and in everyday work. Whether you’re writing your resume or writing your programming, you should always check to see if you’ve made any mistakes. In addition to autocorrect, use Grammarly. The devil is in the details.

The sequence and detailed layout of experiences should be reasonable

Your resume is the only way the interviewer can get a glimpse of you, and it’s important. Whether you’re a recent college graduate or an experienced programmer, if you don’t get the details right, you’re less likely to land your dream job.

If your project experience is not enough, don’t try to fill the word count with a long, long-winded list of the few project experiences you have. This will make people feel that you don’t grasp the core of what you say and your logic is not good enough. Don’t just include the name and date of the company and project, either; a project history without data and content to back it up is unconvincing.

So, there are a few things to note about the project experience

1, it is best to choose the main project brief introduction;

2. How to join the project, what to do in the project, and what role to play in the project

3. It’s best to provide some statistical support

The project experience is simple and eye-catching.

Moreover, it is worth noting that many people who just started their internship will be used to putting their education experience in the first place because they have less project experience. In fact, the correct order of introduction should be experience (professional experience and personal experience), skills and language ability, and education experience.

Optimize visual experience, concise and accurate

In the last year or so, I’ve looked at all kinds of resumes, and you wouldn’t believe some that are six pages long and typeface 7 won’t last more than three minutes in an interviewer’s eyes, let alone the next few pages.

A good resume should not only give the interviewer enough information about you, but also be visually concise, informative, and easy to read.

If you’ve been working for less than 10 years, stick to one sheet of paper.

If you have too much work experience to fit into a single page, focus on experiences that are relevant to the position you’re interviewing for, skipping internships if necessary;

If you’re interviewing for a technology-related position, keep your resume visually simple and it should look like the README on Github.

A great resume may stand out from the rest, but at the end of the day it has to match your experience, skills and side projects to get the interview you want.

I have collected some excellent resume templates for programmers, and now I share them with you. I hope they can help you get a job offer in the upcoming “Golden Nine silver ten” interview season. Background private letter “resume” directly for free!