Interview Book (1) Essential interview soft skills for programmers
Let’s talk about the front: Although it is said that the future is worrying, the recruitment is lost, the BOSS refused, 58 failed, the hook hangs, and a hundred years of mismatch has become a post-dinner talk for the majority of workers, but for programmers who are unemployed or ready to change jobs, they But I can't laugh, especially in the winter of the Internet. So in this case, how should we adjust?
1. Resume optimization
When they hear the word programmer, many people can certainly portray such a lifelike character in their hearts: science students, with high IQ, touching emotional intelligence, careful thinking, more money, less death early, no hair, The more bald the stronger...
I believe that many of our programmers are science students, and almost all science students are afraid of one thing: writing materials. Although text expression skills and page aesthetics are our weaknesses, the resume is our stepping stone. The first goal of our resume is to make HR and interviewers feel pleasing to the eye. So what kind of resume can achieve this effect?
Under normal circumstances, resumes are screened by HR for the first round, and only after HR is satisfied will they be sent to the interviewer for second screening, so we must think about what kind of resume is from the perspective of HR when writing resumes A good resume.
1.1 Grab HR's attention
First of all, the resume must be on the page to make HR feel that you are doing it with your heart, so that he feels that you are a serious candidate. The programmer can use the simple style for typesetting, which looks clean, tidy and generous. Secondly, the information that HR cares about must be clearly reflected, such as your graduation school and education, working years, age, skill list, project experience, etc. I hope that the salary writer recommends not to write it up, because this resume is to be pushed to the interviewer (self-recovery).
1.2 Catch the interviewer’s attention
After HR feels OK, your resume will flow to the interviewer. Imagine yourself as an interviewer, what would you look at?
1.2.1 Skills
Skills items must be classified. For example, we know the three skills of Spring, Redis, and Mysql. Don't mix them together, which is very unprofessional. We can use the list method to merge framework classes, database classes, cache classes, etc., to describe the degree of mastery of each technology, and according to our own actual situation, we must be relevant, whether we can only use it or can use it skillfully, or say You can use it and understand the underlying working principle, or you are proficient in this technology.
Skills items have primary and secondary relationships. For example, if you are applying for a Java engineer, don't write about front-end and operation and maintenance skills first, otherwise the interviewer will think that your Java skills are not as good as your front-end skills. Then you are joking when you come to interview a Java engineer.
Are some other techniques (optional). You can appropriately add a sentence at the end of your skills: Have a certain understanding of HBase, Hodoop, Sprak, Streaming and other big data technologies. Of course, this is based on the actual situation, if you really understand it. Let the interviewer feel that you are an applicant who is willing to specialize in technology and is eager for knowledge.
1.2.2 Project experience
We can think from the perspective of the interviewer. What information does the interviewer mainly want from your project experience? Is it how familiar you are with the project business you do? No, what the interviewer looks at is what you learned in the process of doing this project, what aspects of your ability have been improved, what technology you used to solve the difficulties in the project, and whether you are responsible for the project Core function development, where are you in your project, so in your resume, when describing project experience, you should focus on your position in the project, what functions are you responsible for in the project, and what projects have you solved? The difficult problem, what you have learned through this project is reflected.
Of course, with regard to project experience, many programmers may do traditional projects without using distributed or microservice architecture. Some students will say that the only project I do is CRUD, and I have never used distributed or microservices. There is no technology to solve any problems, so the project experience is very lacking, so what should I do? This requires resume packaging. For example, you can combine the technology you have mastered with the projects you have done, and you can think about whether certain functions in the projects you have done can be changed to multithreading, and whether you can use messages Queue, SpringCloud, etc. Of course, after you have changed your resume, you have to prepare some questions. For example, you do not use SpringCloud in your project, but after you add SpringCloud to your resume, you have to design some questions and answers, such as yours If the project uses a gateway, what do you do with the gateway? For example, load balancing is used, what load balancing strategy is used, etc., design some questions to deal with the interviewer.
1.3 Re-optimization of the finished resume
1.3.1 Footer
Before sending the resume to HR, we can add the full name of the applicant company to the footer of word. Each resume is unique, and each HR and interviewer is treated specially.
1.3.2 Resume file naming
The professional title will definitely increase the opening rate of your resume. Programmers suggest using this form: "name + male and female + application position + working years + mobile phone number".
1.3.3 Resume format
After we finished shooting the document, we thought it was very beautiful. Why did it become ugly when we sent it to someone else's computer? We all know the environment well. Therefore, you must not send the resume file in word format to HR. It is recommended to convert it to a pdf version to retain the original format.
2. Resume delivery in a rhythm
You must be cautious when submitting your resume, and you must not send it overseas.
When we meet our favorite company and position, we must optimize our resume. The optimization is to make our resume more targeted, and revise the resume according to the recruitment requirements of the company you like. You have to know that after you send out a non-optimal resume, if your favorite company is not satisfied after reading it, it will only waste two minutes of her time for the HR of your favorite company, and for you, it will be a waste I have an opportunity to interview my favorite company, and only with the opportunity can I create unlimited possibilities.
So when should I deliver my resume to my favorite company?
Looking for a job is like finding a girlfriend. Don’t meet a beautiful woman and ask for WeChat without saying a word, otherwise others will only treat you as a hooligan. You should be well prepared before going up to talk to her and give yourself your favorite The same is true for the company's resume delivery. You should also fully understand the company, understand the technology required by the position, and see if your current skills can meet the requirements of the position, if not, you should step up to improve your ability.
One more thing, for some programmers, due to their personality, they may not perform well due to tension in the process of communicating with the interviewer. For this situation, then at the beginning of the job search, they should not At the beginning, you should invest your resume to your favorite company. You should invest in a company that you think is ordinary. Get familiar with the interview process, practice your hands more, find your own problems, and finally invest your resume to your favorite company.
So when submitting your resume, you must take a good measure and prepare in a planned way. Don't be too casual. Too casual is a waste of your interview opportunities.
Three, interview skills
Also need to pay attention to some interview skills during the interview.
1. Confidence
I am born to be useful, it is better to rely on others. In the process of communication between people, self-confidence and positive attitudes can infect others. During the interview, if you are very negative and pessimistic, then the message to the interviewer is very negative, then it may be If it affects the interviewer's opinion of you, you may feel that your work will not be very active.
2. Have skill
When answering the interviewer’s questions, be skillful. For example, you don’t know Kafak, but you know RabbitMq. At this time, if the interviewer asks you about Kafka, then you can tell the interviewer that Kafka is not familiar, but based on my understanding of RabbitMq...
3. Negotiation psychology
The interview is a negotiation, a process of mutual understanding and mutual concessions between you and the company. After completing an interview, you can ask the interviewer what he thinks of you. On the one hand, you can express your importance to the interview, and on the other hand, it can also reflect your humility and learning. You can also ask, if I enter your company, what will I be responsible for? A plan for your company's future? Are there any promotion mechanisms within your company? Wait, this can reflect your motivation.
Don't underestimate yourself even if you haven't been accepted by the company you like. Don't be afraid of failure. When a person fails, he can hope for success as long as he advances bravely. Come on, hit the workers! Let us work quietly, and then surprise everyone.
Follow the public account: about Java, share more Java knowledge.
