The building Lord has left office for 10 days, this period of time in addition to see the source code, is to cast a resume interview. I have interviewed four companies in total. Tell me your feelings.
1. XX remit
XX is a small e-commerce website, because the author’s technology stack is concentrated in Java language here, so, even though the author has a little understanding of concurrency, JVM, Netty, Spring and so on, there is still no advantage — because they are completely useless.
Throughout the interview, the following questions were asked:
1. Tell me about your project. What features did You use in SpringCloud?
Are you familiar with Mysql? Talk about indexes.
3. How to implement a singleton pattern (I’m good at this)
4. What thread pools are used (I’m also good at this)
5. What classes do Map interfaces have (I’m also good at this)
6. Write a section of SQL (not SQL)
7. How to implement cookie session without login?
Of course, was brushed, it is estimated that SQL is not good enough, and I am good at they do not need.
2. XX travel
This is the weirdest one. The interviewer was a young man who didn’t understand concurrency at all and forced him to ask me about concurrency without saying a word. And you don’t seem satisfied with my answer?
1. Introduce yourself.
2. Talk about Mysql indexes.
3. Say something about redis master-slave synchronization.
4. Talk about Redis cache penetration, cache avalanche, malicious access. How to design redis Key? What if the Redis Master blows up?
5. How to design a high concurrency system.
6. How to design a business with high concurrent activity.
Talk about volatile.
8. Talk about locks in Java. What’s the difference in use?
9. Talk about final.
10. Talk about the Java memory model.
11. Talk about GC.
Why is Mybatis faster than JDBC? ?
In the whole process of communication, except for the above redis and some leading questions about the project, the following about Java, basically silent, and then DO not know why… I really don’t know if XX tourism is still great.
3. XXX middleware
This one is more interesting, is on Mycat middleware to do Mysql middleware. Both interviewers were interesting.
First, the R&D leader asks.
1. Describe what you are good at (concurrency, JVM, RPC, Netty)
2. Talk about Java’s memory model
3. How is Netty’s REACTOR model better than a plain NIO implementation?
Then the middleware leader asks questions.
1. Write a few paragraphs of sorting and filtering string code on the blackboard.
2. Describe common design patterns.
3.GC optimization experience.
In general, although there were not many questions, the questions were very professional, and I could feel that the interviewer’s technology was really deep. According to what they said, “We often have to solve problems at the operating system level, so we should be very familiar with Linux”, and then they talked to me about several OS functions…
Basically, all begin to ask from the resume, unlike some companies, resume write and didn’t write, don’t ask resume at all, ask you don’t understand, that you call me to do what?? I only know what’s on my resume, and what’s on my resume is what I’m good at, so if you don’t need it, don’t call me here.
So cherish the interviewer who asks for your resume.
PS: This is the only company out of the four that gives water to the candidates…
4. XX doctor
How can I put it? The first interviewer was pretty normal, the second one was…
The first interviewer:
1. Understand basic data structures and algorithms? Talk about linked lists. How to improve query efficiency (2 points?) Can it be improved? (Hint skip table)
2. The cookie and session. Implement a remember me function. Where is the session stored? What if there are a lot of users? What if the JVM crashes a session?
3. Design a box office structure.
4. Talk about hashMap.
5. Why threads are unsafe.
6. Why are HashMap threads unsafe?
7. Is HashMap safe in multi-threading? Isn’t it safe to read? (WTF? Starting to doubt them…)
8. What problems are solved by using concurrent libraries?
9. Talk about the Java memory model.
Still calculate relatively normal. Mostly.
Second interviewer:
1. Write some code to filter the string and group it.
2. Given 10 numbers, the number below is the number below the number above…
3. Over, I think you’re still not open-minded enough.
I he yao is helpless…
The company called me at 6 o ‘clock, and they had dinner at 7 o ‘clock, and they didn’t have a drink of water until 8 o ‘clock. What a godlike company…
5. To summarize
1. Mysql, Redis is really not deep enough, because I did not spend time, can not justify. This is really a side effect of career planning.
2. Your resume is not professional enough, and your job may not match your skills.
3. Get lucky. It’s important to meet a qualified interviewer, many of whom are unprofessional.
4. Normal heart, the interview is a matching process, the right company is not many, no surface, that there is no fate, normal. Keep trying to find the right company for you.
Source: cnblogs.com/stateis0/