Successful interview skills of programmers

Programmers' successful interview skills, programmers are very popular positions in recent years, because in the eyes of many people, programmers have high incomes and want high salaries when interviewing. How about sharing the successful interview skills of programmers?

Successful interview skills for programmers 1 1. Write yourself a very professional resume.

My suggestion is that if you want to increase your chances of being selected, you'd better spend some money on a professional resume. Compared with the huge income you may get in the future, this is really just a small investment.

Step 2 study the interviewer

When I contact a programmer for an interview, I always send him an email with my name and blog address on it in advance. But to my surprise, when I interviewed him, he still knew nothing about me

To give another positive example, I met this kind of developer during the interview, and I can even talk about a blog or a teaching video I wrote before, Kan Kan.

Which one do you recommend?

Interviewers are also human beings, and they also have human weaknesses and characteristics. Dale Carnegie once said that the easiest way to make others interested in you is to express your interest in each other first.

Whether this method is unfair or not, if you want to succeed in the interview, then I suggest that you should study the company and the interviewer well in advance (if you know it).

Information in today's society is so developed that we can find anyone's information on Facebook, Twitter, Weibo and blogs. Even if you just skim it, you will benefit a lot.

Step 3 Get internal recommendation

Do you know the easiest way to find a job? That is to get internal recommendations.

This will not only increase interview opportunities, but also increase employment opportunities by 40%.

I found a favorite company a while ago. And then directly submit your resume? Nuo Nuo, guess what I did?

First I found a developer who shared my thoughts and opinions, and then I began to pay attention to his blog.

Then I left a message on his blog and made suggestions, showing great interest in his work and company. Finally successfully obtained this valuable internal recommendation qualification.

Many programmers will say, "But I don't know anyone in the company." . If you want to give up, forget I said anything. If you are willing to try, I bet you can always find a way to achieve your goal.

But there is a secret, that is, first of all, you should create your own "business card" online-let others have a chance to know you, so do it now.

4. Learn to solve algorithm problems

This is an important skill that every developer should have, and it is not that difficult to master it.

In many interviews, you will be asked to solve programming problems on the whiteboard or computer, but many programmers, even very good programmers, will suddenly have a blank brain and can't figure out their own ideas at all.

If you can take the time to learn how to solve this type of interview problem, you will not be so nervous next time you encounter this kind of scene.

Our nervousness has nothing to do with stage fright, mainly because we are not familiar with these problems and are not confident that we can solve them.

After you build up your confidence in this area, you will never be nervous again.

5. Answer questions energetically.

Answering questions in one sentence or one sentence may be technically correct, but you forgot to seize this opportunity to show your passion-this is the greatest positive energy that a developer can bring to the team.

For example, if I ask you what polymorphism is, I don't want you to repeat it to me according to the definition in the textbook. I hope you can elaborate on this topic, and then we can talk more deeply.

6. Beware of the "trap" problem

Why did you change your job?

Tell me your greatest strengths and weaknesses.

How did you resolve the technical differences with your colleagues last time?

Before answering questions, you'd better understand the purpose of the interviewer asking these questions and master the skills of how to answer such questions.

Let's start with the first question, "Why did you change your job?"

In most cases, what the interviewer wants to know is whether you are a gossip who is used to slandering and attacking your employer. So don't be fooled.

7. Never lie.

The worst thing is lying in the interview.

What you know knows, and what you don't know doesn't know. If you really don't know, don't make up the answer to the question.

On the contrary, you should honestly say that you don't know or you are not 100% sure, but you are willing to try and then talk about your own ideas. After you finish, you can also ask the interviewer what the correct answer is to show that you are very interested in it.

To tell the truth, most interviewers ask questions they know, otherwise you just fill in the blanks for you, and they look like fools. So don't take any chances. Once you are caught lying, the interviewer will immediately question your character.

8. Don't be too honest

Many programmers will reveal their information too much. Don't think that honesty and complete transparency are the best policy, but they don't know that this is too much.

Rule 7 says "don't lie" is true, but we don't need to tell the interviewer all the details and shortcomings in our lives.

It is good to have personality, but it is bad to expose personality defects.

Imagine if you say that you like gambling or are addicted to World of Warcraft, I bet the interviewer will re-examine you. So be careful when you say your information, because it will not only expose your defects, but also show your lack of due judgment.

9, master the basic knowledge of computer science.

Yes, many programmers even confidently said during the interview that they didn't know the linked list and stack because they had no formal education or had returned them to the teacher.

I also admit that we don't need those advanced computer science concepts in our work, but as a professional software developer, you should at least know some basic knowledge.

For example, you ask an electrician to rewire your home, but this electrician doesn't know the basic knowledge of electrician. Do you still want him to do it? Similarly, so do we.

10, about experience

This is the last point, but not the least. Many developers, especially those who have just entered this field, often lack relevant experience and don't know how to increase the so-called work experience.

It's a bit like the chicken or the egg.

So how can we increase our experience?

The key is to be creative. There are many ways to gain work experience, but you don't have to work in a company.

I'll give you a hint:

Participate in open source projects

Start an open source project

Make a mobile app and put it in the App Store.

Write a small Web application

Participate in code exchange and user groups.

These methods can be written into your resume as work experience, as long as you have ideas and no experience.

I hope these skills will help you. If you have different ideas, please tell me.

Successful interview skills of programmers 2 What is the midlife crisis of programmers?

Middle-aged programmer crisis

Recently, Ou Mou, an employee of ZTE Netcom, jumped from the office window on the 26th floor and ended his 42-year-old life.

At present, there are different opinions, some say that the share transfer price is different from the personnel department, some say that they are suspected of being resigned because of internal struggles, and some even report that there are mental problems in Europe.

Although the specific reasons need further research, it has triggered a wave of discussion about the crisis of middle-aged workplace, especially the crisis of middle-aged programmers.

Generally speaking, the contraction of an industry leads to the adjustment of the number and structure of personnel, which can be roughly described by a simple model: the scale of the industry is reduced, the number of employees in the industry is reduced, the number of companies is reduced or the scale is reduced, which in turn leads to the reduction of management positions, and the original management is forced to drop.

This mechanism of reducing posts is transmitted layer by layer. The top level is reduced to the middle level, the middle level is reduced to the basic management post, and the basic management post is reduced to the front-line employees. At the same time, due to the shrinking scale of the industry, the number of front-line employees is also decreasing.

Leading to the unemployment of front-line employees and stopping recruiting fresh graduates from the industry. Under this model, generally speaking, even if the industry shrinks, middle-level personnel do not have to worry about employment and can still stay in the industry. In the worst case, they will only be demoted.

The learning ability of middle-aged people has obviously declined.

However, in the programmer industry, there are some special factors that make it different from the general industry.

Middle-aged people aged 35-45 have a marked decline in their learning ability. At the same time, this is an era in which new technologies are constantly emerging.

Twenty years later, a person's skills and concepts are completely different when he first enters the workplace. The programmer industry has taken this feature to the extreme.

In addition, the energy is obviously reduced and it is impossible to stay up late. In addition, due to housework, it is difficult to put high-intensity work into action even if you have the will.

If the middle-level personnel in other industries can still live comfortably after demotion, then the middle-level personnel in this industry are not as good as their colleagues in their new positions after demotion.

Therefore, many middle-level employees are in an awkward position in the IT and communication industries where programmers are intensive. Even if you reluctantly accept it, you will face the psychological adaptation problem of sharp drop in income.

If we consider the high mortgage ratio in asset allocation, when the capital chain breaks, it becomes unbearable.