Talking about the things you must pay attention to when interviewing for programmers

Hello everyone, my name is Yi Yang. I have always been an interviewer at Ant. I am in charge of recruiting regular employees and interviewing partners. You can come to me for interviews, internal promotions, and school recruitment related to large factories!
​

This is a series of live interview articles, one is updated every week, the next one will demonstrate how to write a resume through a case, in order to win the favor of the interviewer. Remember to follow me, and you will receive a push after the update!
​

How to write a resume

1. Three principles of resume: clear, short, necessary, and leave a good impression on the interviewer
2. Technical ability matching: meet the requirements of the recruiter, and the technical level must reach the standard
3. Highlight the highlights of the project: within 10 seconds, let the interviewer find the highlights and have the motivation to ask questions

​

1. Three principles of resume

A good resume should meet the following three characteristics: clear, short, necessary

1) Clarity : The resume is easy to understand, the typography is simple and not ambiguous
For example, the school and graduation time, how many years of work, work experience in the corresponding industry, job positions, etc. need to be clearly defined.
​

In social recruitment, some people will count the internship time, and this working time will not match. If you are recruiting, you don’t need to write internship-related content unless the content is particularly good.
​

Some people will put the graduation school at the end of their resume, and some will not let the interviewer guess when they graduate, which is really a honey juice operation. This kind of resume is generally not accepted by default, job seekers are not confident themselves, and the interviewer is not in the mood to continue reading resumes.

2) Short : In a work report or job-hopping in an interview, "highlighting the key points" is a very important ability, which is helpful for the interviewer to understand the key content you want to express. Very important parts can be appropriately bolded, and then the resume should not exceed 2 pages.
​

If you don't know how to do this part, I recommend everyone to read the book "The Pyramid Principle", which is very good and a must for professional people.

3) Necessary : Only necessary information is required on the resume, which can help each other maximize time saving and improve efficiency. Make sure that the content in your resume is of interest to the interviewer.
​

Basic information includes basic information such as name, email address, mobile phone number, working years, intended city, etc., such as the place of origin, which are not important to the interview, do not need to be written.
​

Some people will put GitHub or blog links in their resumes. If the blog content is substantial, they can be put on it. If there is no content, just a few face-to-face notes, such links will not be put, but the score will be reduced.
​

If the blog link is posted, the interviewer will usually take a look, so the content of the blog should be prepared to avoid embarrassment during the interview after forgetting it.
​

Some people will list all similar projects in the project experience, such as A management background, B management background, in fact, there is not much difference in the content of these work, just write a representative one.

​

2. Technical ability matching

This part highlights the in-depth fields and core skills mastered, such as experience in performance optimization, monitoring, engineering, etc., mastering Vue / React source code, mastering the principles of networking, browsers, etc., familiar with data structures and algorithms, etc., highlighting these contents It can guide the interviewer toward the battlefield you preset, so as not to suddenly throw a few interview questions that you don't know and cause panic.
​

​

3. Highlight project highlights

It is necessary to write a project experience very concisely. It is recommended to use the [STAR] rule to improve the introduction of the project. The STAR rule is the situation (situation), task (task), action (action), result (result).
​

Simply put, it is [S] what is the background of this project, it can be the project introduction or the problems and difficulties encountered, [T] what work needs to be done, what responsibilities do you have in it, [A] in what way To solve these problems, [R] and what metrics are measurable results.
​

From some points in the project, it is worth writing your own value into your resume.

Project preparation

There are two types of work, one is business-oriented and the other is infrastructure-oriented
​

If your team itself is an infrastructure team, you only need to sort out your project system, from why you do it, how to do it, technical difficulties and business value.
​

If your team is business-oriented, you need to actively explore technical points in your usual work. This depends on the support of the team. The best way is to push the team to explore technical points and make some business value enhancement points.
​

There are still many directions that can be done. Find a direction to do it for more than a year, and then consider changing jobs after getting the results.
scaffolding system, marketing configuration platform, publishing/publishing platform, micro-frontend, low-code, efficiency tool , etc. are all available. It is best to do it in combination with the business. After completion, it can bring business value, which is of great help to performance and interviews.

​

Preparation for brushing questions

Although many people complain about this, but there is no way, the market is like this. During the interview, the regular questions cannot be answered, and it is difficult to enter the following links.
​

There are actually so many regular questions, including HTML, CSS, JS, asynchronous, browser, network, security, framework, data structure and algorithm, performance optimization, and handwritten questions.
​

Now many companies will arrange programming ability tests at the same time, so programming questions and algorithm questions need to be well prepared, you can go to https://muyiy.cn interview website to learn.
​

Review the knowledge points and items listed on your resume. The knowledge points on your resume will be very frequent interview questions in your next interview. These must be firmly grasped.
​

For knowledge that is not written on your resume, then there is no need to prepare. For example, if you haven't been exposed to Mini Programs, you don't need to read them. For example, if your project is React, then you don't need to prepare Vue. It's all about your resume.
​

If you come across a knowledge point that you didn’t write about during the interview, just tell the truth that you haven’t touched it much. The interview is to tap your potential and your highlights, not to embarrass you. The answer is no problem.
​

Several frequently asked questions

formatting issues

Unified use of PDF format, many people like to send Word format, but it will be messed up when viewing on different devices.
The layout should be concise and clear, with black text on a white background, using common tables, headings, and lists, without being too fancy.
​

work stability

The interviewer usually asks the reason for leaving. If there are frequent job-hopping recently, you need to pay attention. If the goal is to enter a large factory, it is best to stay in the most recent one for more than 3 years, and it is best not to exceed 3 in 5 years, otherwise it will be more dangerous.
​

interactive answer

Some people like to ask questions and answer them, which is actually not good. Questions and answers will be paced by the interviewer, and it will appear that you are not thinking and look like you are reciting.
​

Here you need to highlight the thinking, framework principles or technical details related to the problem, and show how you are different from others. Throw out your main technical highlights and lead the interviewer to ask.
​

If you encounter a problem that you won't know, just tell the truth that this technology is not good, and have not understood it in depth, then tell your own understanding, and remember to make random guesses.
​

don't gossip

Some people like to talk nonsense and answer a lot of questions, but there is no focus and no primary and secondary, which will make the interviewer feel that your thinking is not clear.
The interview is actually looking for fellow travelers. In addition to the technical level, the communication level will also be examined. If the logic is confusing, such people are generally not suitable for recruiting and training.

answer too fluently

This is very bad. Too fluent is not in line with normal people's situation. The interviewer knows that everyone is prepared, but reciting large paragraphs recklessly will give people a feeling that they just memorize but do not understand the essence of the problem.
​

This piece needs to have appropriate pauses and thinking. During the process, it is best to look at the interviewer's eyes and have eye-to-eye interaction.
​