1. Never nude
Go out for an interview without writing any resume, the probability of hanging up is as high as 90%, unless you are particularly good
2. Write your resume, don’t think that the description of your resume is clear.
For the same person, ordinary resumes and optimized resumes, the interviewer’s positioning of you and the questions asked are also different
This is my personal experience. Before I went out for an interview with an ordinary resume, the interviewer could only treat you as an ordinary three-year experience and ask some special basic questions. Even if you know a lot of things, the interviewer doesn't ask at all.
As for the optimized resume, when the interviewer saw that the resume is so awesome, you can ask a few questions first, and you can answer well.
Then, directly start to ask the relatively open questions of the underlying source code, architecture design, etc., so that your positioning and grade will be up.
3. Carefully prepare 2 projects you have done
For the items you write on your resume, you must sort them out repeatedly. The business boundary and technical architecture of the project must be clear, and the technology used must be guaranteed not to be questioned
4. Java basics
I won't say much about the importance of the basics, but what I want to say is that, like collections, threads, volatile, locks, network IO, etc., don't stay at the surface level of online blogs.
You must go deep to the source code level so that you can stand out and widen the gap with other candidates.
5. Various mechanisms of the database
ACID, transaction isolation level and principle, index principle, common sub-database sub-table posture, etc.
6, various things in the JVM
Generation, collection algorithm, garbage collector collocation and comparison, online troubleshooting, class loading, etc.
These things, the minimum requirements must be fluently stated, but if you want to open the gap with other candidates, you must highlight the bright spots.
For example, I did the tuning of the garbage collector before, switching from CMS to G1.
After I finished the basics of CMS generation and garbage collection algorithm process, I said that CMS has two major shortcomings : one is memory fragmentation, and the other is floating garbage.
Then began to say why these two major shortcomings occurred? What happens because of these two major shortcomings? (Causes RT to rise); What are the advantages of changing to G1?
Then I will spray those principles again, and how much performance has been improved after tuning. This is in the mind of the interviewer and it has opened up the gap with other candidates.
7. Frame
The framework you have used must be clear to your chest. Spring's most basic IOC, AOP, and Spring transactions must be seen.
The common postures of Mybatis and Tomcat should be known, the common deployment plan, cluster principle, persistence mechanism, and the underlying data structure corresponding to the five data types of Redis.
Reactor model operation mechanism, solutions to common caching problems.
Know the posture and basic principles of Dubbo and ZooKeeper. If you have studied the source code of this kind of RPC, whether it is Dubbo or SpringCloud Family Bucket, it would be even better. Just say it, crush the interviewer, and let the interviewer listen to you.
8. Distributed related issues
It’s even better if you have studied the frameworks related to big data, absolutely plus points
For example, I have thoroughly studied the underlying mechanism of Kafka. When interviewing ants, I directly asked me the underlying mechanism of Kafka:
-
If you let me design, how to ensure zero message loss. Directly from the three possible message loss stages, how to design to ensure
There are also common solutions for distributed locks, and common solutions for distributed transactions must be studied.
For example: when interviewing ants, I asked me about the mechanism of TCC, and directly stated the posture, usage scenarios, and the advantages and disadvantages of using TCC.
9. Algorithm
I am not very proficient in this, I am only familiar with common lookups, sorts, linked lists, queues, heaps, binary trees and other simple ones.
I also know the basic concepts such as dynamic programming and 01 knapsack problem, and the headlines are hanging here.
10. Believe in yourself
Finally, there must be self-confidence during the interview process to give the interviewer a feeling that he is particularly confident and that he can do nothing.