Essay

The interview mainly looks at a few points: project experience + basic technology + personal potential (that is, whether it is worth cultivating).

Regarding the project experience, I think that the founder of Concurrent Programming Network, Mr. Fang Tengfei, said a very good sentence:

When introducing the product, the interviewer will examine the communication ability and thinking ability of the candidate. Most of our cases are a function of the product or A module, but even so, have you figured out the entire system architecture or product, and can introduce it clearly, why do you make this system? What is the value of this system? What are the functions of this system? What are the advantages and disadvantages? If you were asked to redesign this system, how would you design it?

I think that's enough of a generalization. Maybe you only work for one year, maybe you are doing insignificant modules in the project, of course, these must be your disadvantages and cannot be changed, but how to make up for this disadvantage, I will summarize a few points from the words of Teacher Fang:

1. What exactly does the project do and what functions does the project have

2. Clarify the overall structure of your project, and clearly draw it to the interviewer during the interview and clearly point out where to call from and how to use it

3. Make it clear that you The position and function of the modules in the whole project

4. Make clear which technologies are used in your modules, and better, you can learn more about which technologies are used

in You can't change your working years and your own In the case of persuasive project experience (this must be a deduction item), this way can make up for and improve the interviewer's favorability to you to a certain extent.

To add, when talking about your project in an interview, there is one question that cannot be avoided 90% of the time: talk about the more complex problems you have solved in the project. This requires constant discovery and exploration in your work, not much, as long as you find one or two questions in your own current project that you can talk about. A little trick is that even if the problem is not solved by you but by someone else, but you understand and thoroughly understand the problem, you can still treat the problem as if you solved it yourself during the interview- --After all, who cares if this problem was solved by you at the time?

http://www.cnblogs.com/xrq730/p/5260294.html