Overview,

An excellent engineer must first be an excellent programmer, and an excellent programmer must first be an excellent person. This article is not about how to get the offer in a short time, but how I, as an ordinary technical person, regard the interview as a part of life planning and achieve my goal step by step. It’s one year, three years, five years, not one month, two months.

First, productized thinking analysis of self, build capacity model

Socrates said, “Know thyself.” What we do here is also “know thyself.” Certainly not to answer the question “Who are you, where have you come from, and where are you going?” “, but to use product thinking to analyze yourself as a competitive product in the talent market, so as to build a competency model.

  1. What to analyze

    In fact, it is to analyze their own bright spots, shortcomings. As technical people, analyzing is what we are technically good at, for example, is the framework familiar with React, Vue or Angular? How familiar is it? Can you answer most common questions? Do you have your own independent opinions and practice? How competitive are my competencies compared to others in the market for homogenization?

  2. Why analyze

    The goal of the analysis is to find out their competitive points, understand their own value, so as to build their own capability model. In the process of learning to strengthen the advantages, make up for the shortcomings. In the interview process, the strengths and weaknesses, grasp the advantages, avoid shortcomings and shortcomings.

  3. How to analyze

    • Make a list of your highlights
    • Find the weaknesses in your bright spots
    • Ability to list what the market wants that you don’t have or don’t have enough of (weaknesses)
    • List improvement plans or solutions for a, B and C above

🌰 : I think my highlight is that I am familiar with React, but I do not know the implementation principle of React. Then I can list an improvement plan about React, specializing in React, such as studying source code, to make this ability more scarce.

Disadvantages 🌰 : Network knowledge is often used in project development, but I can’t do anything but make axios calls. So I can make a study plan about the network knowledge, not this deficiency.

Second, the direction of engineering method planning, focusing on the strengths to complement weaknesses

In fact, after analyzing our capability model, we know what to do next, in four words, to complement our strengths.

To make a bright spot truly competitive in the market, it must increase its scarcity. To improve his scarcity, the first is to eliminate the lack of light.

Just like the highlights and weaknesses of 🌰, the highlights are familiar with React, while the weaknesses are not familiar with the principle of React. Then we can use the factory method of planning and implementing the implementation (the following is a 🌰) :

Three points to note:

  1. Set up milestones, that is, every fish bone, after reaching it, let yourself have a sense of achievement. 2
  2. Planning is on paper, practice is under foot.

Third, pay attention to resume maintenance, let resume sustainable development

Many people think of a resume as just a piece of paper for an interview, but in my opinion, a resume is a slice of your life at a certain point in time. A resume is a description of your competency model. You are what your resume looks like. So how do you maintain your resume?

  1. Every word in your resume should have meaning, content, and focus on your highlights, with practical support. React blog, React project, and React open source tools can be used as precipitation output

  2. Combine planning with updating your resume as you cross a milestone. For example, you are not familiar with the React principle, but when you make up for this deficiency, you can update the description of React

  3. Rather, less should not be more, should not be pan-fine. I used to like to list a lot of technical stacks on my resume to show that I had experience, but found that the more you list, the more you can cover a lot of ground. So “Learn about Spring Cloud, MySql, RabbitMQ…” I changed the description to “back-end development experience, understanding common technologies, back-end technologies”, turning a potential pitfall into an advantage.

  4. Update your resume after the interview. When we come out of the interview and find that some of the descriptions on the resume are misleading or don’t fit, immediately after the interview, fix it. Such as 🌰 of 3.

Iv. Preparation before the interview

  1. General questions

    In fact, the general question is to reflect the basic quality of the place. The so-called general questions are self-introduction, project introduction, career planning description, etc. It may seem like small talk, but the expedition has already begun. Every word reflects a person’s knowledge and accomplishment. So, it’s recommended to draft and practice, and remember to always build around your competency model and resume.

  2. Technical questions

  • Often meet test questions will
  • Technology should have its own opinion, practice and summary
  • Algorithms, design patterns and so on belong to the silicon step to thousands of miles, need to start with the first step, slowly precipitation

  1. Interviewers usually give you a chance to ask them some questions that you can prepare, such as:

    • Team situation
    • Project situation
    • Your position positioning
    • The company benefits
    • .

  2. The question bank

    Organize your test bank to include the three types of questions mentioned above

5. Expression in the interview

I’ve talked to some interviewers who say that some candidates are excellent, but they don’t know how to express themselves. My presentation in the interview summarized the following three points:

  1. Think for a few seconds before you answer

    What is the purpose of the interviewer’s question? Then make a short draft, preferably if you’ve summarized it before

  2. Answers are organized and can be summed up by total points

    Often the interviewer will take notes, so if your answer is too general and unfocused, you won’t know what to take notes. For example, I like to say: I have three opinions on this question: 1, XXX, 2, XXX, 3, XXX, where 1 says XXX, 2 says XXX and 3 says XXX. In a word. XXX.

    First the conclusion, then the details, and finally the conclusion. Improvisation is a bit difficult, but it can be done if it is a habit, or if you make a draft and practice deliberately.

  3. Always focus on your highlights, don’t bury yourself in a hole

    The most afraid of interview is to dig holes for themselves, for example, when answering questions, citing their unfamiliar technology, so that the whole interview to go to their unfamiliar field. That’s why we need to analyze our competency model, understand our strengths and weaknesses, and make a draft and practice of common questions. To keep the interview in your own territory, start by not digging holes for yourself, and then lead the interviewer to your territory.

Six, the interview after the review

Take notes during the interview and review them afterwards:

  • If you don’t do well on general questions, add them to your own bank
  • If the technical question is not good, then go into the technology, summary, precipitation, to ensure a good answer next time

Seven,

  1. failure

    Failure is the norm, success is luck, or it is accumulated through all the pits, just like the bug, re-check and solve, so that they will not step into this pit again

  2. To give up

    Giving up is normal, but it is not normal to insist all the time. I give up on life once a week, but I must find a way to get myself back up. For example, if I use planning to discipline myself and achieve my goals, it’s okay to give up a weekend.

Eight, summary

  1. Planning for the long term
  2. Intermediate precipitation
  3. Short-term preparation