Dear readers, I haven’t updated it in a few days. On the one hand, because these days busy work, take up the writing time. On the other hand, I am preparing various materials for this article. This year is the most difficult year to find a job. I hope this article can help you to provide a high success rate of job hunting.

This article is divided into resume, interview and salary talks, and includes tips and tips for all aspects of the job search process.

Article 1. The resume

If you think of yourself as a product, your resume is an instruction manual.

Writing a resume may seem simple, but writing it well is not. A good resume can help you stand out from the crowd.

I’ve condensed the best of my resume writing tips for new readers and added some new content. Regular readers of previous articles can quickly scan this section.

1.1 Personal Photos

The debate about whether or not to include a photo on your resume never ends. Programmers don’t live by their faces, but I tend to show photos.

Usually when I’m looking at a resume, if I see a picture of a young guy looking good, I might think: His code is probably neat.

Yes, photos are the first impression people make of you. Normal people like beautiful things, and a photo that makes people feel good, even bright, can make people feel good about you.

So my personal advice is, as long as you look good for the audience, it’s ok to put a photo on your resume. It’s ok to have some beauty, but don’t be a photo cheat.

1.2 Basic Information

Basic personal information, such as name, education background, email address, telephone number, etc., should be written normally. I just remind you not to omit the following points in the eyes of the interviewer.

• Most people only put their degree in their personal information, not their university. If your school is famous, you can write the school you graduated from in this section.
• If you have a blog, Github, or account related to the position, don’t hesitate to include it here. It shows that you love learning and sharing.
• Another tip, take the public account for example. If you are more productive, add a sentence after the name of your public account, for example: 50 original technical articles. Don’t take that statement lightly. It’s icing on the cake.

1.3 Self-evaluation

Make sure you take the time to write carefully!

This is a comprehensive statement of who you are, a way of rediscovering yourself and letting the other person know your strengths, goals, and values. And it’s worth it, so you can introduce yourself later in the interview process.

I see that most of the self-evaluation is like this: “I am hard-working, responsible, steadfast and hard working, strong learning ability, and have team spirit… Balabalabala “.

Well, I really doubt it was a combination of words that I did an Internet search on. It’s not interesting, it’s not persuasive, anyone could write that. Can’t you give me more examples, more numbers?

Look at some positive sentences:

• I have 7 years of Java development experience and 5 years of Internet industry experience. I think I have reached the level of senior engineer. I hope I can grow up to be an architect in the future. (With goals and plans)
• A loyal fan of Minjian development, a practitioner of unit test driven development, will actively refactor code and have a code cleanliness obsession. (Good coding habits)
• I love reading technical books. I read about 10 books a year. Recently, I am reading Domain Driven Design and Enterprise Application Architecture Patterns. Love to learn and have completed 5 paid courses on Geek hour this year. (Love reading and learning)
• 2 years of team management experience, team size of 15 people, harmonious team atmosphere, member turnover rate is far lower than the average level of the company. Has been selected as the company’s outstanding team. (The team is not bad)

1.4 Skill Level

Once in an interview, the resume of the other person said “proficient in Spring, Redis…” “Is a long list of about a dozen mastery items. The results of the interview question, found too water, you are redefining the mastery of it.

Familiar with, master, master this kind of word, there is no unified standard, do not write disorderly, do not let a person think you are bragging.

If you are a newcomer, you are not sure.

Skills: Development language: XXX, XXX, XXX Back-end framework: XXX, XXX, XXX Database: XXX, XXX, XXX

Old programmer, you think you can write proficient write, if you know a lot of skills, don’t forget to highlight. What’s the point? 1. Highly matched skills that are clearly required by the position. 2. Skills with highlights, such as 3 years of experience in AAA framework; Read BBB source code; Publish 5 ccC-related articles.

1.5 Project Experience

Project experience is an important part of the interview process.

• Project experience here is two words, project and experience, and most people just write about project and ignore experience. An experience is what you do, how you do it, and what happens when you do it. For example: Which parts of the project did you do? Are you a key person? Do it alone or with a team? How did you grow? What happens after the project is delivered?
• If you’ve done a lot of projects, keep them to a minimum, or you’ll write pages of projects that will miss the point. Don’t write about projects that are too early or too small. Instead, write about projects that are large in scale. Write about projects that are more relevant to your position.
• Don’t write legible abbreviations for project names. You can understand them even if you write “ERP”. If you write “SCF”, it looks very foreign, but god knows what it means.

1.6 Resume Template

Keep your resume template simple and generous.

I’ve seen so many resumes, some of which are too loud, some of which have exaggerated covers that you want to close as soon as you open them.

Job seekers want to make their resume look good and stand out from the rest, but sometimes they overdo it and become zuo. Especially the new, easy to overexert in this respect.

If you can’t find a job, try this one.

1.7 other

The above parts are the most important, you should pay more attention to the rest of the normal writing. Don’t fake your resume. It’s too much to lose if it gets caught.

Resume pages, in my opinion: 1 page is a little thin, 2 pages is just right, and try not to exceed 3 pages.

A little extra talk about how to write a resume. Newcomers, especially graduates, feel they know too little and have nothing to write about. In this case, you need to collect more information about the requirements of the position, use this information to strengthen yourself, and then include it in your resume. For example, if you find that git or Maven is required, take the time to do so if you don’t know it. In addition, you can write in the resume during the school awards, practical activities, highlight their love of learning, aspirant these advantages, let the interviewer feel that you are a potential stock can also add points.

In conclusion, the resume should be more facts, less empty talk, show your strengths. If you want to write a good resume, you need to have some user thinking, HR and the interviewer are users, stand in the perspective of the user to consider the problem, find a way to let your resume impress users.

Article 2. The interview

The original interview is intended to write technical interview questions, and then thought about it, different levels, positions of programmers on the opposite test requirements are not the same, difficult to adjust. So I decided to write about the basics of the interview process, how to answer common questions, and a few things you might not know.

Halfway through, I regret it. The more generic, the harder it is to write. Write too fine, everyone looked wordy; It’s too rough to write, and I’m afraid I can’t say it clearly.

2.1 Basic

One of the basics is punctuality. If you’re late for something so important, how can the interviewer trust you to manage your time?

The other thing is basic politeness. As an interviewer, I’ve seen a lot of people sitting in their chairs when I walk into the interview room, not even moving their hips. Shouldn’t you get up and say hello?

And, just in case, bring along a few printouts of your resume. Especially in a round of interviews where you’ll be facing multiple interviewers, your resume will come in handy if you have more than one.

These are the phenomena I often encounter in interviews, so I remind you to pay attention to them. As for what clothes, not to say, most people know.

2.2 Self-Introduction

General interview has this link, good preparation, practice in advance, do not answer when hemming and hawing, or long-winded for a long time to say the key point.

The time for the introduction should be controlled within 3 minutes and the words should be clear. As for the content, you can refer to the self-evaluation in the resume, which should include at least the following parts:

• Who am I? My name is XXX, and I am currently working in Jingxi Company as a senior Java engineer.
• My skills — I have been engaged in Java development for 6 years, and have 3 years of development experience in e-commerce industry. I participated in overseas e-commerce project of Jingxi Company, in which I was mainly responsible for AA and BB functions.
• I’m the best fit — I heard from HR that your company also wants to do overseas e-commerce, and I think my experience can be used. Moreover, I also hope to experience the whole process of overseas e-commerce from zero to one, which is also a challenge and an opportunity for me to grow.
• Other strengths – I usually like to read technical books, and recently I have been reading XXX.

It’s important to make a good impression in the first few minutes of an interview, so prepare your introduction.

2.3 Don’t pretend to know what you don’t know

Don’t pretend to understand the nouns and questions you haven’t heard in the interview. Do you think the interviewer is stupid? You can’t fool him or her.

What if you don’t want to say you don’t understand?

Once I interviewed a new employee and asked him if he had ever used Git. He thought for a moment and said he had not, and then asked me to introduce him. After the introduction, he said he had been using SVN and explained the operation of SVN. So far, I think he answered the question ok. But before that was over, he asked me how Git was better than SVN. After MY brief talk, he said that Git sounded good and would give it a try.

You see, a problem has been solved. I was satisfied with his answer, and the subsequent interview process went smoothly. Finally, I hired him.

Here are some of the most frequently asked questions.

2.4 Why did you leave xx Company

The question of why you left is almost 100% asked.

After being asked, do not complain about your former company or boss, no matter what you have experienced, no matter how many grievances you have, do not make fun of, the interviewer can not give you a reason, only worry about whether you will say the same about him in the future, do not provoke.

And don’t say that a low salary might raise doubts about your stability or loyalty to the company.

The reason for being laid off, it is best not to mention, the large-scale layoffs are easy to explain, otherwise why not you lay off others?

Reasonable answers, such as: want to move to a bigger company; Company direction adjustment, and personal development direction does not match; The company moved its r&d department to another city.

2.5 Can you work overtime

Faced with this question, some people do not hesitate to say “yes”, as if this answer will prove that they can endure hardship and not afraid of fatigue. If you ask if you can make a company your home, someone will probably say yes. I agree!

You should ask the company how many hours and how often they work overtime. If the job requires reasonable overtime, it is acceptable. If the company prides itself on working overtime, working overtime for its own sake, why should you accept it?

Of course, I admit that overtime is common in Internet companies these days. If this is a company you really want to work for, and it has an overtime culture, just do it for the money, or for the gold plating.

2.6 What are your weaknesses

First of all, this is a pit question, which I will not ask.

When answering, you don’t need to package strengths as weaknesses, such as “MY weakness is that I pursue excellence and always strive to be the best at my job in my spare time.”

Not to mention any weaknesses that might be considered bad for an interview, such as “I’m boring and I’m not good at communicating with people.” Well, I can see that you’re not a good communicator.

I’ll tell you what to say:

• Talk about weaknesses they know about — If you’ve been an engineer for five years, say something like, “MY development experience is ok, but my product thinking is lacking and needs to be strengthened.” There will be no penalty for answering that.
• Say weaknesses you’re working on — for example, “I’m only a year out of school and I’m not technically strong, but I’m taking technical courses online.”

2.7 Do you have a career plan

I often ask this question, but most people can’t answer it well.

I ask this question for two reasons:

What kind of person do you want to grow up to be? Be an architect, be a technical manager, be an industry expert… If the goal is not clear, what are you striving for? If you think the future is too far in the future for you to understand now, ok, three years from now is ok.

Two, in case we become colleagues by chance, as your superior, I know your goals, I am willing to provide you with some opportunities to help you achieve your goals at work. I’m glad you’re growing up.

Not for the interview, for their own, but also suggest that we seriously think about this problem, think of the time to combine their interests and expertise.

2.8 Do you have any questions

First of all, congratulations. If you’re asked this question, you’ll probably have a shot at the interview.

“There are no more questions.” That’s a bad response!

Interviews are a two-way street. You have to choose the company as well as the company choosing you. Before others know you thoroughly, you don’t take this opportunity to ask the company’s situation, you will not regret after entering the job.

How to ask:

• Don’t be too specific about compensation and benefits — you haven’t got the job yet, so is it appropriate for you to ask how much food is covered? “More than a year salary” this kind can ask, big money to pay attention to.
• Don’t ask if you can find it online — Brother, don’t you do your homework before you come in for an interview?
• Don’t Ask if they can’t Answer — A candidate once asked me what the company’s strategy was and I had nothing to say. It was my fault I was too low.
• Ask about the job description, training, etc. These are important questions to show that you are interested in the job.
• One of the most popular questions I’ve heard so far asks, “Why do you like working here?” That’s a good question. Give it a good taste.

Then talk about the pit that you need to guard against during an interview.

2.9 Interviews are tricking you into helping them solve problems

Say an Internet joke:

The database of a company suddenly broke down, and no one in the company could handle it. The boss was very anxious, and called HR to the office and said: You quickly publish a DBA position with an annual salary of 1 million yuan. During the interview, ask them how to recover our database, and remember, whether he can answer it or not, he will be rejected!

It’s a joke, but it happens in real life. During the interview, I will ask a question, which is very detailed. In addition to asking your solution, I wish I could directly let you operate on the spot.

Other interviews tell you to build something, you work on it for days, then you hand over the code, and it’s over.

2.10 The interview is to extract secrets from you

This is pretty much the same thing as the one above.

I had one when I was making a game. The interview was normal at the beginning, and then the climax came, asking me the number of daily active users, income flow, how to buy the amount, buy the amount of cost, user characteristics……

You can’t tell me that. I didn’t feel right, so I made up an excuse and left.

2.11 Training institutions recruit students in disguise in the name of recruitment

Look at a netizen’s experience:

The general pattern of this pit is: 1. Publish a large number of recruitment needs, and the recruitment scope is very wide. 2, whether undergraduate, junior college or high school diploma, as long as the resume, will be notified to attend the interview. 3. During the interview, there will be someone posing as a department manager to knock down your skills and point out your many weaknesses. 4, brainwash you to attend “pre-job training”, and ensure that the training immediately after the job, training costs deducted from the salary. 5. Sign a “job training contract” (actually a registration agreement, often with a loan agreement!) . In your face mengbi situation, the name, the back of the debt.

Graduates and would-be programmers should be careful of this.

3. The compensation

If you regard yourself as a product, then the salary is the price.

To be honest, I am very bad at salary negotiations, and many of my previous experiences in salary negotiations were blood and tears. In order to write this part, I consulted several HR friends around.

3.1 The most basic

As usual, I’ll start with some basic knowledge.

First of all, don’t ask about salary too early. If you ask about salary before the interview results are complete, it will cause resentment. The right time is when the interview is basically successful.

Second, don’t overstate your current income. When you overstate your current income in order to ask for more money, you are blindsided when asked to provide bank statements and proof of your previous salary. When the lies don’t pan out, you may be tempted to falsify bank statements and salary statements. Again, the cost of counterfeiting is so high that once detected… You’re gonna have to pay me back.

A long time ago, I didn’t understand HR’s bargaining behavior. It was all the company’s money. Later, I understood that reducing human cost is an important responsibility of HR and also their performance.

3.2 Know the market in advance

If you want to negotiate a good salary, you have to do a lot of preparation.

Before negotiating salary, find out what the industry is paying for a position similar to yours. A few days ago, a map was widely circulated on the Internet: the grade comparison table of new employees in Dachang. This picture comes from the folk. It’s not very accurate, but it’s reliable.

Before talking about salary, it is best to know the company’s bonuses, dividends, benefits, etc., the more you know, the more helpful for the subsequent salary negotiation.

A lot of people are not good at salary negotiations, are the loss of unequal information.

3.3 I want how much fit

When asked about their expected salary, most people have a dilemma: if they want to raise their salary, they are afraid that they will think you are a big mouth. Want less, oneself again unwilling.

Before reporting your expected income, you need to know:

• Many companies have a rule that raises are generally limited to 30% without special circumstances.
• Don’t base your salary on your monthly salary.
• Increase the expected income a little, and then report to HR, leaving a negotiation space for both parties.

If your annual income is 200,000 yuan now, and you expect to earn 250,000 yuan based on the previous information, you can offer HR a minimum expectation of 270,000 yuan. After some bargaining, the two parties reached an agreement at 250,000 yuan, which not only reached your expectation, but also satisfied HR’s sense of achievement in price reduction. Perfect!

3.4 Stick to it

In the face of price pressure, many people cannot hold on. If you feel like you did a good job, believe you’re worth the money, and don’t regret missing out on the company, stick with it. After all, job-hopping is the best chance to raise salary, so if you miss it, you miss it.

If your current job is 965 and your new job is 996, you’re working 80% more hours, and you’re still making less per hour. Do you deserve yourself if you don’t insist in the face of price pressure?

On the other hand, HR not only has low prices, but also has recruitment targets, so it is not easy to recruit an ideal employee.

3.5 Is monthly salary divided into basic salary and performance

Our company’s monthly salary is divided into basic salary and performance salary. For example, 8000 is basic salary and 2000 is performance salary. It seems that the monthly salary is 10,000 yuan. But every month everyone has a performance coefficient, the real monthly salary is 8000 + 2000 * coefficient, if the coefficient is less than 1, the monthly salary can not reach 10,000 yuan.

When you’re talking about salary, ask what constitutes a monthly salary, and if performance is included, what do you pay attention to

• More on base pay, less on performance. Don’t wait until you get the job to find out what your monthly salary is, half base and half performance.
• Does the company have a habit of pressuring performance, or does a lot of people have a performance coefficient below 1?

3.6 Write it into the contract

HR has a common way to lower prices, saying “we pay 18 a year”. This means: a monthly salary may not pay you that much, but 18 months a year gives you the annual income you want.

That’s when you ask her, can 18 be written into the contract? If it can’t be written in the contract, there is no point in saying so, the company will send more or less depends on the company’s conscience and profitability.

Shares, options, bonuses, and so on are the same, no matter how the other side of the oral commitment, must require written into the contract. Don’t be shy about asking. Promises that aren’t guaranteed by a contract are empty promises.

3.7 Don’t increase the price again after the negotiation

There was a job seeker who, one day after negotiating his salary, said that he hoped for another increase of 2000 yuan, because he inquired about the salary of his colleagues in the company and felt that his salary was low.

First of all, ask about salary privately, this is the workplace taboo. Besides, did you get enough information? Is underpay accurate?

Secondly, after a good deal and then raise the price, this is not to push your luck. The pay didn’t go up, and the job went away.

Don’t do the penny wise and pound foolish thing.

The level is limited. I will write so much for the salary part for now. I wish you higher and higher salary in the future. If you think the writing is not good, you tell me, I will go to those HR friends to deal with.

4. Tease the interviewer

I’m the interviewer and the candidate, so I’m going to put myself in the position of the candidate and poke fun at the interviewer and the company.

• Interviewers are not punctual. The candidate showed up on time, only to have to wait a long time for the interviewer. It was literally “one hour wait, 15 minutes interview”.
• The interviewer is too pushy. Some interviewers ask questions and try to beat them down by making them unable to answer. Is it that good to run people over?
• The interviewer is disrespectful. Interview is a two-way street. The interviewer should not be arrogant and nosy. Remember, the interviewer also represents the company.
• Multiple interviews, repeated questions and answers. I wish I had been asked the same questions in three interviews. What’s worse is that I have to go to three companies in three interviews. Is it okay for you to focus on the interview, focus on the interviewer?
• Interview builds a rocket, work turns a screw. Recruit people according to the standards of architects, write add, delete, change, check, if else after entry.
• If it passes, give notice. Job seekers want to know the results of the interview, not through the notice also calculate, through the delay for a long time to notice. Improve efficiency, early notice early let others practical. Plus, if you wait too long, by the time you call someone, they may already be working for another company.

At this point, the article is almost over. I wish everyone can find a good job in the future, to a good salary.

Finally, advise you in addition to reading the article, there are more interviews, more experience accumulation. When looking for a job, don’t look too high only at the big factory, not only those big factories are good companies, not all small companies are very low. I know some small, quiet, profitable companies with great benefits, and some small companies are started by big business owners. If you can join these two small companies, you can really make a profit.

Finally, this article is very hard to write, I am not sure about some knowledge, online search, people to ask, spent a lot of energy, two consecutive days to write more than 4am. But after writing, oneself harvest is very big, oneself think quality is not bad.

If you feel that after reading the harvest, you are welcome to scan the code to follow my public number, see more interesting dry goods articles.