I have to say that the wishing on the headline is pretty stellar. I made a few offers 24 days ago and finally got the byte offer I wanted most (though I thought at the time that even if other offers got it, I might not go. )
I also went through several toss during the period. I thought I was going to hang up, but on the contrary, I lost my horse and knew no good. Instead, the base was in a more suitable team.
I have to say that some of my potential underlying thinking methods are still a bit consistent with the "byte model". The interviewers who have talked along the way are very happy and agree, and feel that they can join such a team. I will be happy at work
Okay, when I have finished speaking, then I will start to cut into the theme——
[Theme background]:
30 years old, 5 years of outsourcing work experience, key undergraduate
【Interview Position】:
Byte Java Gang
【interview time】:
2 months, 3 interviews
To the point
one side
1. Introduce yourself, why choose to come out and see the opportunity
2. Talk about projects, how to do alarms, and how to do unified access to monitoring items
3. Talk about projects, configure center projects, and ask how to do real-time configuration push
4. Discuss why all the component dependencies are selected to be controlled in the configuration center
5. How do I do a current limiting function? How to make this current limit distributed?
6. How to grab the lock? How to release the lock?
7. After the timeout is added, is it possible for someone to steal the lock without releasing it? How to deal with it?
8. How can this problem be solved without zk's heartbeat?
9. If you want to make the current limit configurable, you need a background management system to configure the global flow of an api at will, how to do it?
10. In a certain business, it is now necessary to generate a globally unique incremental ID, and the amount of concurrency is very large, what to do
11. Algorithm question: Find the specified number for the matrix that M*N increases horizontally and vertically
12. What do you want to ask me?
Two sides
1. What is the tool chain and technology stack used in daily life?
2. Has golang ever stepped on the pit? Are there any bugs in this golang code?
3. How are the storage, conflict, expansion, and concurrent access of HashMap in Java resolved?
4. In the zipper method, what are the advantages and disadvantages of the red-black tree when the linked list is too long?
5. Where is the concurrency insecurity of HashMap reflected?
6. When HashMap expands, what special treatment does it have on read and write operations?
7. How does ConcurrentHashMap achieve concurrency safety?
8. What lock mechanisms does Java have, and what are their characteristics?
9. Do you know CAS? How is CAS implemented in Java?
10. What is the MySQL storage engine used? (InnoDB) Why choose InnoDB?
11. What is the difference between MySQL clustered index and non-clustered index?
12. What are the differences and advantages and disadvantages of B+ tree and binary tree?
13. Design an index for a scene, the specific scene is forgotten, anyway, it is the knowledge of joint index and column selectivity
14. How to solve a new query scenario?
15. If you want to check A in () AND B in (), how to build an index?
16.When checking A in () AND B in (), how does MySQL use the index?
17. If query A in (), does MySQL check the index for N values separately, or is there a better operation?
18. Which data structures of Redis have been used? How is ZSET implemented?
19.Zrange start, stop, the total length is n, what is the complexity?
20. How do Kafka consumers do message deduplication?
21. MySQL de-duplication, Redis de-duplication, if the scene volume is very large and misjudgment is allowed, bloom filter can also be used
22. Introduce Kafka's ConsumerGroup
23. How are Kubernetes and Docker used?
24. What is the storage structure of a time series database?
25. Do you understand the LSM tree? What kind of storage structure is it?
26. Have you used Cassandra and RocksDB in production? How big is the amount?
27. What is the tombstone mechanism of Cassandra?
28. Algorithmic question: The original question on Niuke's questionba, you can go and see: NC57 Reverse Number
Three sides
1. Talk about projects and work experience
2. What pits have you stepped on in the process of using Kubernetes?
3. Consider a business scenario: The number of comments on headline articles is very large. For example, a popular article has millions of comments. Design a back-end service to realize the timing display and paging of comments.
4. If you use id to turn pages, how to design the database table? How to design the index?
5. If the quantity is large, do you think it is necessary to divide the database and the table? How to divide it?
6. How to query paging after sub-database and table?
7. How to ensure that the primary key is still incremented after sub-database sub-table?
8. Now it is necessary to support deep paging, page number jump directly, how to achieve it?
9. If the amount of instantaneous writing is very large, the storage may be interrupted, how to protect it? (breaker)
10. How is it realized inside the circuit breaker? (You can use ringbuffer)
11. The circuit breaker will cause the write failure, what if we do not allow the write failure?
12. Algorithm problem: N concerts, given in the form of [{startTime, endTime}…], calculate the maximum number of concerts you can listen to
What did I do before I took the byte offer? Start with the preparation of your resume. The resume is the facade, but also the stepping stone. Whether you can get an interview opportunity from a big factory depends on your resume; then to prepare-brush the interview questions, interview big companies like byte, we are sure It is necessary to have a certain understanding of the interview with a big factory, so that you will know what the interviewer will ask; the final knowledge reserve is the so-called skill improvement, etc.~
At the same time, if you want all the information of the article, you can get it for free by scanning the QR code of the editor after [Follow] + [Comment]! ! !
How to write a good resume
A resume is actually the face of a person. Everyone does not know each other. How can the interviewer know your general information quickly? It will start with the resume. Let me tell you what you should pay attention to when writing a resume:
- Concise and clear: On my resume, I don’t think it will be very fancy, it will be very simple and clear. It will catch the interviewer’s attention so that the interviewer can quickly catch the key information without immersing the interviewer. Among the so-called fancy
- Highlight the key points: Generally speaking, the interviewer will make a lot of targeted questions based on your resume, and the order of general questions is from front to back, from top to bottom, but if you are not too familiar with you, or you are not Write very proficient in the front. When the interviewer asks questions, the answer is not very good. Even if you answer very well later, it may reduce a lot of scores. On the contrary, if you write all the things you are particularly familiar with, if the front The question is answered very well, even if there are some flaws in the following questions, the interviewer’s score on you will be improved a lot.
- Pay attention to the wording: I have seen many people write resumes that are proficient in Java multi-threading, proficient in Spring, etc. This kind of basic is a one-sided death. Generally speaking, if you write proficient in Spring, then I think you can basically write by yourself Independently develop a Spring framework. If you are familiar with writing it, I think you have seen a lot of Spring source code and are familiar with some of the principles. If you write and understand, I will think you will know the basic usage of Spring. So whether each of your skills is proficient, familiar, or understanding this term is particularly important. The interviewer will verify whether you have this ability based on what you write. To give another example, everyone will have their own project experience. When you write a project, the wording of your role is also very important. Whether it is the project leader or the project participant, the interviewer will vary according to your role Let me ask you about the work you are doing. If you exaggerate, this is easy to spot.
Swipe the interview questions
In fact, brushing the interview questions is the most "first aid" method, so I brushed the interview questions before the interview. Regarding the problem, I really have something to say:
Java Interview Collection
Java collection interview questions
Multi-threaded/concurrent interview questions
Redis interview questions
Spring interview questions
MyBatis interview questions
Spring Boot interview questions
RabbitMQ interview questions
Algorithm interview questions (must ask for byte interview)
Real BAT interview questions + special training
My knowledge reserve
Speaking of my knowledge reserve, then I have to tell everyone what I have experienced in the past 24 days. Interviewing bytes. This is a challenge for me, so what I need is to improve my skills and summarize the technical points. I have something to say:
Java core notes
This Java hard-hearted notes document includes JVM, JAVA collection, JAVA multi-threaded concurrency, JAVA basics, Spring principles, microservices, Netty and RPC, network, log, Kafka, RabbitMQ, Hbase, MongoDB, Cassandra, design patterns, load balancing , Database, consistency algorithm, JAVA algorithm, data structure, encryption algorithm, distributed cache, Hadoop, Spark, Storm, YARN, machine learning, cloud computing.
JVM
JAVA basics
JAVA collection
I will not list the articles due to space reasons. At the same time, in addition to the documents brought to you by the editor, there are also "Java intermediate and advanced core knowledge points" as shown below. Friends who need to learn from the editor can scan the QR code of the editor to share for free! !
High-level core knowledge in Java
Data Structures and Algorithms
Must know tools
Interview guide
