face to face

1.
Resume The content that needs to be included in the resume should be academic qualifications, your own technology stack, and some projects you have done. Your resume doesn't need to be too long, just two pages. It should focus on writing some of the frameworks you have used, some of the projects you have done, and your own gains, concise first. Generally, the interviewer will not have a lot of patience and look at the detailed description of your project, so try to be concise and clear.
2. Resume
delivery There are several delivery methods, I believe everyone knows it. Generally, it can be delivered on the programmer's vertical recruitment website, such as Maimai, BOSS direct recruitment, pull hook and so on. Zhaopin is not suitable for us programmers, you know. In addition, since I am not a big cow, if there is a headhunter hooking up, I will try my best to ignore it, because I have learned a lesson from blood. Therefore, it is more reliable to submit your own resume as much as possible, or to recommend it.
3. Interview
Since I am a cross-city, the interviews I receive are generally phone interviews + video interviews. If the conversation is almost there, there are also on-site interviews, and I will not be restricted by the form.
Generally speaking, the interview process is very similar. First of all, introduce yourself, focus on some of your work experience, and some of the content that you are mainly responsible for. This piece can be prepared in advance, but it does not need to be specially prepared. Don't make it like an endorsement, but it feels unreal.
3.1 Technical Interview
Generally , companies will have two to three rounds of technical interviews, and there may be more rounds of technical interviews in large factories, but the content of each round of inspection is not very consistent. Here are some problems that I encountered.
3.1.1 Java Basics
At this point , some basic knowledge of Java is generally asked, such as
• What is the difference between synchronized static modified classes and methods
• The principle of HashMap, the underlying data structure, the process of rehash, the problem of pointer collision
• The thread safety of HashMap , why does such thread safety issue occur
• Data structure of ConcurrentHashMap, underlying principle, whether put and get are thread-safe
• Some contents of Java IO, including NIO, BIO, etc. 3.1.2
Advanced Java features
It is recommended that you look at the source code, which is roughly as follows:
• The construction method of the Java thread pool, the meaning of the parameters in it, and the principle
• What problems do volatile and ThreadLocal solve
• The specific implementation of CAS in Java
• The composition of the Java virtual machine, and The life cycle of a Java object, as well as the contents stored in the stack and method area
JVM's GC process, including analysis of some practical problems, such as explaining a phenomenon, allowing you to analyze what may cause such a problem and how to do it Tuning JVM parameters
• Difference between synchronized and Lock, and underlying implementation principles
• Conditions triggered by Full GC and Minor GC
• Selection of GC Roots
• Usage scenarios of jmap, jstat, jstack, etc., MAT, etc.
• Loading process of ClassLoader
• CountDownLatch, CyclicBarrier, Semaphore, etc.
• New features of Java 8, etc.
3.1.3 Databases
There are two kinds of databases, one is MySQL, the other is NoSql database, including Redis, MongoDB and so on. Commonly asked questions are:
• The difference between inner join and left join, etc.
• SQL tuning, explain, profile, etc.
• The difference between InnoDB and Myisam
• ACID
• The transaction isolation level of the database and what problems they can solve respectively
• Several data structures
of Redis • Is Redis single-threaded or multi-threaded
• Redis persistence 3.1.4 Framework
3.1.4.1 Spring Because Spring is our commonly used framework,
this The content of the block will be asked more and will be more detailed. • Two major features of Spring (IoC and AOP) • Spring's bean life cycle • How does Spring solve the bean circular reference problem • Two implementations of AOP, and their differences (in fact, dynamic proxy is used here, There are two types of dynamic proxies, one is JDK's dynamic proxy, which mainly uses JDK's reflection, and the other is CGLib, the difference between the two can be searched by yourself, there are many articles) • AOP general usage scenarios • Spring's Transaction Principle 3.1.4.2 MyBatis This question is relatively simple: • The difference between $ and # • The difference between MyBatis and Hibernate • Source code, generally less asked 3.1.4.3 Dubbo















Because I usually use Dubbo, this section will ask:
• Principles of RPC
• How Dubbo completes remote calls
• How Dubbo is tuned
• Communication protocol
of Dubbo • How does Dubbo achieve load balancing
3.1.4.4 ZooKeeper
• The usage scenario
of ZK • The election mechanism
of ZK • The node type of ZK
• Consistent Hash principle 3.1.5
Data structure and algorithm
, such as tree traversal, quick sort, etc.
3.1.6 linux
usually asks about the use of some commands, and then gives an actual scene, allowing you to use commands to troubleshoot problems. This part is not very familiar and needs to be strengthened as soon as possible. 3.1.7
General Questions The interviewer usually asks more in-depth questions.
For example, how to design a snap-purchase system, String to Integer, etc., this part needs to test a person's ability to respond on the spot, the accumulation of system design ability in normal work, and the thoughtfulness of considering problems. It is also possible to make detailed inquiries about the design of the system written on your resume, so when you write your resume, you must not write the content that you are not familiar with, and you can't explain it clearly, so you will usually be passed directly. Lose.
Of course, some common maven commands and design patterns are also asked (this part is mostly about singleton patterns).
3.2 HR interview
This section generally asks some reasons for leaving, and of course, some problems encountered in the usual work, how to solve them. If you have a good conversation, HR will talk to you about salary at this time. When asked about the current salary, I am currently telling the truth. Here, there may be many people who report higher. If it is similar, the problem is generally not big. If it is too exaggerated, there may be problems in the follow-up, such as asking you to provide bank statements. If the difference is too large, there may be integrity problems.
In addition, there is the issue of salary increases. My principle is to consider the scale of the company in advance, and then set a range based on the current salary (later found that this is very bad and will be passive). In the current salary It looks like a 30% increase on the basis (it may vary from place to place, but this will be safer). If you're good at talking about this, ignore it.
In addition, the most important thing may be the payment of five social insurances and one housing fund. Generally, small companies will let you choose whether to avoid tax or not to avoid tax. There is still a bit of knowledge in this. If you avoid taxes, your provident fund may be very small. At present, I have encountered two types. One is to pay you a provident fund according to a fixed amount every month. Whether your salary increases in the future or not, it has nothing to do with the provident fund; the other is to pay you according to a certain amount, usually 7% of the salary is paid to you, or according to the minimum standard. In this case, please carefully consider whether you need to accept the offer.
Finally, you can also ask about benefits, such as asking about year-end bonuses, annual leave, overtime, etc.
Fourth,
finally let me say a few words.
The most important thing in an interview is honesty. If you don’t know it, say no, and then you can try to express some of your own ideas. If you don’t have ideas, just say it straight. No one is perfect, and it is impossible to cover everything. Just exposed.
Be sure to prepare well before the interview. For example, half a month or a month in advance, you should start reading some basic content, make a summary of your current work, and find your own highlights. Highlights are very important. In general interviews, with highlights, you will be able to take the initiative in the interview process.
Finally, when the dust of the new job is about to settle, I wish you all to find the job you like.