I think if you are in a stable pit, the step through social recruitment should be
1, the first position of self localization should be self reflection under the current environment. General thinking of the students to change jobs, often also have a lot of dissatisfaction with the current environment. Then it is better to think about where the problem is and if it is possible to improve on your own. When you joined the company, did you fully learn the company's technology, if not, also do not rush to leave. Each period of professional experience, must have a harvest, so as to go to a higher position, if in each environment is a muddle, basic jump a few times to the bottleneck. Then think about what the next job want to do, stick to technology or turn to do technology management, since the decision to change a job, then do something you want to do, is not it. Generally speaking, if technology transfer management, need some technology accumulation, may mean that you can achieve a certain level of technology to make it easier, because programmers are a little "arrogant", if you are very technical, it is difficult to manage the team, and not very good to do technology cost assessment. Of course, can be changed to do other things, after all, life is so long, if they do not like to do development, do not compete with bugs.
2. Long-term preparation-dry goods if you're in a position where you've decided not to do the technology, skip the rest of the section, and if you continue with the technology, this will be the dry goods for self-improvement and for interviewing. However, this content may be more suitable for Java-related Internet practitioners, which is the largest Internet technology practitioner. First, the programming language itself is related to the language ecology, Java here for example, the principle of virtual machines, you will find that the most likely to be asked is the issue of garbage collection, you can engage in a "deep understanding of the Java Virtual Machine" to study carefully; multi-threaded scene knowledge, thread pool, lock principle, etc., you can read the The art of Java concurrent programming, JAVA8 related issues, spring including IOC,AOP also various questions, recommend "Spring Technology Insider", of course nio,netty these are often out of the mirror. Internet technology is often used in a variety of middleware, you can read the official documents, you can also find some "xx Authority guide" and other books, do reading. If the company scene has the use, that is best, if not, these things do not have the trouble to build themselves. Here are some examples, such as the commonly used to solve the high concurrency scene of the reading problem of the buffer middleware Redis,memcache, etc. for decoupling Message Queuing middleware, Rabbit MQ, Kafka, etc. for the distributed environment of consistent data zookeeper MySQL sub-table Cobar, general search engine elastic There are many areas, every area has a lot of products. Storage itself is also a very deep topic, MySQL is representative of the relational database, NoSQL represents the Mongodb,cassandra. Their use of the scene, advantages and disadvantages. Architecture, in fact, feel the most mainstream architecture or SOA, recommended to read the "Distributed Service framework principles and practices", I did not see the book before the interview, many topics including the fuse, downgrade and so did not think about, resulting in the previous interviews mentioned related issues are a little hazy. Of course, it may take years if you think about it. Targeted understanding is important, if you are looking for a job right now, then pick the company's relevant technology to dig deep, so the interview is better.
3, Post delivery first talk about the position, regarding the position of the company to the staff, refer to our company's rating standard, for the p5-7 this level requirements are as follows: P5 (advanced development)-able to independently develop small modules P6 (senior development) without guidance-can independently design and develop a core module P7 (architect, Experts)-a product engineering of the overall design of a higher level is not within the list, because the core implementation at these 3 levels, this is the Ali line company P series level definition, the different company level difference will be bigger, but many companies in the recruitment, will be the Ali department do reference and superscript. So for their own job target delivery resumes, this will avoid some oolong, and later will mention different levels of interview.
4. Interview Process and content
4.1 Processes Many companies say that you rank after an interview, but there are many situations where you will be set up in any position. For example, mark for Senior/Senior XX engineer, that interview process is according to P5-P6 this, this level of the interview is generally just a group of technical interviewers, group boss (perhaps the director), HR side decided. If it is a face architect/expert (P7), the process will be different, usually within the group of architects/experts, and then the senior architect/expert, director, cto/Technology VP, HR side. So don't throw yourself into positions, if you position yourself as an expert, don't invest in senior and senior positions.
4.2 Content interview content is nothing but what you have done, what you will, what you can do about what you have done, of course, the projects you have done, the ones that have been achieved, the contributions you have made, and so on. These content, should be involved in the interview before they comb well, if the work is serious, the work process often think, and have the habit of optimization, this part of the content is easy to say, after all, do it yourself. Your resume can also include things that help you articulate your work, such as diagrams or forms, which seem simple and helpful for you to communicate with the interviewer and motivate him to ask questions. For example, the owner of their own business during the framework of the server background with color pages attached to the resume, a lot of interviewers are particularly interested in this architecture diagram, basically from the top to the bottom of the next, and then in-depth analysis of several technical points and scenes, a round of interview on the Happy end. This figure is as follows (some of the content is not professional enough, I gradually realized)
What you will do, is the technical level of the interview, the interviewer may be when you are talking about the project, from somewhere for the point of entry, 1.1 points of in-depth questions. For example, first ask if you have done concurrency, if you say yes, you may continue to ask if you have used a thread pool, and if you say yes, you may continue to ask, what is the core principle of the thread pool, and if you can explain a bunch, then you may continue to ask, how many thread pools are suitable for different scenarios.
This may buckle very thin very fine, ant Golden Service interview, the interviewer estimated to be 40-50 years old, bookish is very strong, Java really ask a lot of content. Only in peacetime in-depth accumulation may know, if only a general use, did not think how to optimize and understand more underlying principles, do not know what the interviewer said. This section can refer to the previous long term content.
What you can do, when this part is open question, this topic usually does not have the standard answer, examines you to solve the problem the ability. I encountered a relatively many problems is that the design of a second kill system to solve the problem of data consistency in distributed systems, especially the issue of distributed consistency, is the industry's problem, thrown to you should also be to see you in peacetime work has not thought about this problem, have not tried in the work, Avoid this situation as small as possible.
5. Talk about the offer here I do not have any skills, because I do not like bargaining with people, I may value the work content, the atmosphere of these, did not try to bargain with HR. But basically your salary is determined by the level of salary you are interviewing for, your previous salary, and your other offer's salary. So if you are planning an interview, you might as well look at the opportunities, at least other offers can be a reference for you to measure your own peace pay.
--------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------