Personal situation
2017 graduation, regular undergraduate Computer Science and Technology, after graduating in second and third tier Java development in a small city, 2 years experience in Java development. Distributed development did not experience high concurrent treatment, usually do the project To G majority. The following is written by the same interview you want to give the company's junior partner to be a reference, but also want to write down some of their harvest and depressed pits.
Resume Delivery
At that time, taking into account the development of Shenzhen, so the BOSS voted micro-public banks, the first side is a phone interview. Only about a period of about two to electric surface. For the first time about Monday night at seven o'clock, but waiting for half an hour did not come to the phone. Later BOSS say something, changed about half past seven pm Wednesday. Post: Java development engineer.
one side
Half past seven telephone to the party, listening to the sound interviewer is a very young guy. I have not asked for an interview empty now, and I say possible. After the first simple self-introduction, the project did not ask, ask directly related to the technical side of things.
I think you used the project redis, you know redis common data types What are you?
What do you usually do with redis?
Do you know how fast you redis?
redis persistence mechanism to talk about.
How to achieve redis Distributed Lock? (Redis answered a series of questions, followed by questions, the interviewer brother will say, OK, OK, that time really gave me some hallucinations, feeling he was satisfied with me, let me relax a guard, was a routine batch)
Do you know what it is Spring's AOP? (Interviewer: OK, OK)
You know AOP implementation principle underlying it? (Interviewer: OK, OK)
CGLIB difference JDK dynamic proxies and dynamic proxy? (Interviewer: OK, OK)
With JDK dynamic proxy either case, using dynamic proxies CGLIB under what circumstances? (This problem did not answer it, had read the related article, was not remember), but (the interviewer still: OK, OK)
What design patterns used it? (I say usually are basically development of multi-function modules, design patterns used less, but achieve some design patterns will pay attention when reading the source code, such as JDK IO system, HttpServlet, Spring Design Pattern) (Interviewer still: OK, OK)
Several singleton pattern implementation? (Interviewer: OK, OK)
Talk about database optimization ideas? (Interviewer: OK, OK)
You know it back to the table? (The first time I heard the word, that he did not know) (Interviewer: OK, OK)
mysql common execution engine What? (Interviewer: OK, OK)
Index realization of the principle? (Interviewer: OK, OK)
The difference between B-tree and B + tree? (Interviewer: OK, OK)
Thread pool principle? (Interviewer: OK, OK)
ConcurrentHashMap versions of difference? (Interviewer: OK, OK)
HashTable Why inefficient? (Interviewer: OK, OK)
HashTable there is no lock on the entire class? (Read the original source code, the basic methods used synchronize all keywords, I said no)
Do you have any questions for me? (Ask the next relevant business and technology stack)
Side result: death.
to sum up
The interviewer is very nice, always say OK, so I have some float up, sometimes the interviewer seemed very pleased with you, does not mean you really can too, since I learned to be in a job interview learn to maintain a sense of balance, no matter what the interviewer's opinion of you, keep the sense of balance is really important. Interview questions quite conventional, can be said that ninety percent of all routine questions, learned related technologies should be able to answer, there is no particularly difficult for people, interview experience is good, overall praise, although they have not seen. Revolution is not successful, comrades still work.