[Spring Recruitment] I met with Ali, Tencent and Byte and all took offers, summarizing the experience of this spring recruitment

Like it and look again, make a habit, WeChat search [Ao ​​Bing] to follow this Internet tool man.
This article has been included on GitHub https://github.com/JavaFamily , with the complete test sites, materials and my series of articles for interviews with major companies.

Preface

This article is mainly a hardcore summary of Ao Bing's readers' spring recruitment. I mainly post some typesetting and polishing. You can also actively contribute (the manuscript is well paid). I can't create it. I edited the interview video of my graduate student at Peking University. After two weeks, someone said that I would not post technical articles, and the backstage was scolded. I was too difficult.

C actually contributed almost all of his spare time when everyone couldn't see it. On weekends and evenings, so touch it lightly, right?

text

2020 is a year that did not start well at the beginning, but the internship is still going to start, and this year's internship seems to be more difficult than usual. After experiencing the spring recruitment war, I finally got Meituan, Tencent, Jingdong, 360, Sogou, etc. offers (all are java back-end development).

After the end of the melee, I felt that I needed to write a summary. First, I would summarize myself and leave a mark. Second, I hope to share my own experience with you and help you all.

I am a non-computer undergraduate class, and I went to 211 for the postgraduate entrance examination. I belong to the most common computer graduate student. I don’t have any internship experience. To tell the truth, I’m very general, so I think it has some general reference significance, of course experience. It's just for reference. Finally, you still have to choose the best way to learn.

Next, I will share my experience of this spring recruitment in seven parts:

1. How to prepare for an interview
2. How to send your resume and choose a position
3. What to pay attention to in the interview
4. Java interview high-frequency knowledge points
5. Choice of offer
6. Some other thoughts
7. to sum up

The following whole process hand code, whole process dry goods, whole process high energy!

Part 1: How to prepare for the interview

I myself started preparing for the interview in February. I personally suggest that the preparation of the battle front does not take too long. It is most suitable around 2-3 months. Of course, if you think you need a longer time to prepare, there is no problem. It depends on your personal basis.

First of all, there are two main areas for interview preparation: general and professional.

The so-called general-purpose section is generally the basic algorithm. There are no complicated techniques. Just use Leetcode and Niuke to brush it. Now the recruitment process of major factories all have modules with online shredded codes (especially bytes), so this section needs to be paid attention to.

The so-called professional sector is generally development or algorithm, suitable for the field you want to go, such as java development, C++ development, front-end, mobile terminal, machine learning, etc.

In my personal experience, except for some companies that are obsessed with algorithms, the professional sector is more important than the general sector. You must focus on the professional sector.

Secondly, preparing for the interview does not mean simply recitation!

When preparing the knowledge points, you need to take notes, do a good job of your own understanding (it is important to have your own understanding), and form a system, because if you just simply recite and you cannot connect the knowledge points, just If a system cannot be formed, the effect will be poor.

For example, you need to know the usage scenarios of the technology (talking about the technology without combining it is a rogue), the pros and cons, and the comparison with the same type of technology.

Example 1:

The interviewer asked: I now need to record certain key operations on a system and use it for big data analysis. How would you design this function?
(2020 Jingdong Interview Questions)

If you have a global perspective and a system when reviewing. You can immediately know that the core of this question asked by the interview manager is to ask whether you know how to use AOP for horizontal business. If you just memorize AOP can be used to record logs, can be used to check permissions, but do not understand his core, without establishing a system, this kind of question is easy to answer wrongly.

Example 2:

There is a static variable with an initial value of 0. Now there are two programs that modify this value at the same time, and each program performs an auto-increment operation. What is the possible final value of this variable? If volatile is added to this variable, what value might it have?
(2020 Meituan Interview Questions)

If you just memorize some concepts of multithreading without understanding what is going on, this kind of question becomes, know a little, but just can't answer it. Therefore, it is necessary to understand, form a system, and understand the application and analysis.

Example 3:

If you are asked to design a cache, what issues do you think you will consider?
(2020 Ali interview questions)

In the same way, if you don't have a complete system understanding of caching, then answering this kind of question is to answer a little bit from the east and a little bit from the west. For specific caching knowledge points, please refer to the Ao Bing official account.

There are many interview questions of this kind, I will not list them one by one. I want to emphasize that what big companies want is not a robot that can endorse, but people who can truly understand and solve problems.

To sum up, the focus of the review interview is on the professional section, but also the general section. When reviewing, remember that you cannot become an endorsing robot. You must know how to establish a system so that such review is more efficient and orderly.

Part 2: How to deliver resumes and choose positions

Basically, Internet companies' resume delivery methods are internal push (campus bbs, or senior school sister), Niuke.com, official website delivery, some recruitment software, etc., all of which are similar. For job selection, the broad categories are technology, products, operations, etc.

What I want to talk about here are a few issues that may be relatively special.

1. Early approval

In today's spring moves of gold three and silver four, time has clearly become an important battlefield, and the earlier the so-called cast, the greater the probability of hitting. In fact, there needs to be a trade off consideration here. When you are not ready, it is not suitable to vote too early. Because it is very likely to sink directly into the pond. Therefore, you need to measure your own state before making a decision.

1. Questions about the pool

The so-called pool is when your first delivery interview fails, and then your resume will enter the company's large pool.

Once in the pond, they begin to wait for the process of being caught repeatedly. Except for individual companies, most companies will have a situation where they can get people.

1. Processes of some large factories

Ali:

Ali's process is the most complicated and relatively long. The basic process has one side, two sides, three sides, intersection, HR side, and in front of HR, there may be additional sides. The average number of interviews is 5 sides.

In addition, there are evaluations and online written tests (2 programming questions), which must be participated. Generally, people will not be screened. If a department is hung up, you can transfer to the department, but you need to complete the assessment and written examination again. There is a situation of HR screening. Mainly, in addition, interviews are basically sudden attacks, basically in February-May.

Tencent:

Tencent’s process is relatively simple and efficient. It is divided into early approval and regular approval. Generally speaking, early approval is the main battlefield. The basic process includes initial test, retest, GM interview, and HR interview.

If you pass this round of interview, there will be feedback within 24 hours (whether it is grayed out), and the overall efficiency is higher. There is no written test for advance approval, and there is a written test for regular approval (but it is not necessary to participate, but participation will have a higher probability of initiating an interview).

If a department is suspended, it can be picked up by other departments. HR interviews basically do not screen people. The interviews are mainly telephone interviews and video interviews. Interviews will be scheduled in advance, and the time is basically from February to the end of May.

Byte bounce:

Byte’s process efficiency is very high, and the efficiency is quite high. Basically, one side, two sides and three sides can be completed in one day. There is a unified online written test and an advance approval. However, Byte’s internship recruitment is a year-round recruitment, so there is basically no daily and summer vacation. The difference is that the HR side basically does not screen people.

A department is hung up and can be re-delivered. Interviews are mainly video interviews (online interviews for Niuke, must have a shredded code), and interviews will be scheduled in advance. Recruitment takes place throughout the year.

Meituan:

Meituan’s process is relatively simple and efficient. The basic process has one side, two sides, three sides and HR side. There is a unified online written test (5 programming questions). If one department hangs up, it can be picked up by other departments. HR interviews rarely screen people. The interviews are mainly telephone interviews and video interviews. Interviews are scheduled in advance, and the time is basically from February to the end of April.

Jingdong:

The JD process is relatively simple and the efficiency is average. The basic process is one side, two sides and HR side. There is a unified online written test, and there is basically no advance approval. It is a unified progress process. The written test is first and then the interview. The interview is mainly telephone interview, and the interview will be scheduled in advance. The time is basically at the end of March to April.

NetEase:

NetEase's process is relatively simple and efficient. The basic process is one side, two sides and HR side. There is a unified online written test, and there is basically no advance approval. It is a unified progress process. The written test is first and then the interview (the written test will screen people). The interview is mainly telephone interview and video interview. The interview will be scheduled in advance, and you can Choose the time period, which is basically from March to the end of April.

Baidu:

Baidu's process is relatively simple and efficient. Basically it is one side, two sides, three sides, HR side. There is a unified online written test in a week-by-week rhythm, and there is basically no advance approval. It is a unified progress process, and the written test is first. Re-interview (the written test will screen people), the interview will be mainly telephone interview and video interview, and the interview will be scheduled in advance. And you can choose the time period yourself, which is basically from March to the end of April.

Huawei:

Huawei's process is relatively simple and relatively long. The basics are technical. Supervisor face. The interval between the two interviews is relatively long as a whole. There is a unified online written test, and there is basically no advance approval. It is a unified progress process, and the written test is first. The interview will be mainly video interview, and the interview will be scheduled in advance. The time is basically from March to May.

360：

The 360 ​​process is relatively simple and relatively long. Basically, it is the first test, retest, and HR face. Basically once a week, there is a unified online written test, and there is basically no advance approval. It is a unified progress process, and the written test is first. The interview will be mainly video interview, and the interview will be scheduled in advance. The time is basically from March to May.

Sogou:

The Sogou process is relatively simple and relatively long. Basically, it is the first test, retest, and HR face. The overall cycle is long, and there is basically no advance approval. They are all unified progress processes. Interviews are mainly telephone interviews, and interviews are scheduled in advance. The time is basically from March to May.

The other companies are also similar, so I won't list them all.

For the specific interview process, you can ask more referees and friends in the same session, or go to Niuke.com to pay more attention to the interview dynamics.

To sum up, generally speaking, you can submit a few more attempts to deliver your resume, choose according to your personal circumstances, and have a certain understanding of the position before delivery. The first delivery is very important, and some companies have written tests or Resume screening, so we should also pay attention to resume writing and online written examination or assessment.
In general, gold three silver four is the iron law, everyone must plan.

Part 3: What to pay attention to in the interview

Generally speaking, the interview part is basically divided into 4 sections: self-introduction, resume questions, professional slogans, and reverse questions.

First of all, let’s talk about self-introduction. Personally, I feel that self-introduction is not too long. Succinct and concise is enough, but there is one thing to pay attention to. Self-introduction needs to highlight two aspects: the first is enthusiasm for technology, and the second is to guide interviewers to ask questions in their familiar fields.

I once chatted with an Ali interviewer. Taking Ali as an example, Ali mainly values ​​three aspects of students:

1. To be at the forefront of academic performance and solid basic knowledge
2. Like to toss and have a great passion for technology
3. Have internship experience, participation experience, or dissertation experience.

Therefore, in the self-introduction part, try to highlight the above aspects.

Secondly, let’s talk about resume questioning. This is mainly about the interviewer’s questioning of the technical items in your resume.

Therefore, for the items you write on your resume, you must be very, very familiar, otherwise the question is as if you have not done it before, which is very embarrassing.

So you can pack your work appropriately, but if you pack just for packaging, the gains outweigh the losses.

In addition, for the project in your resume, you need to have a complete preparation, answering from the project background, project introduction, project role, project technology stack, etc., rather than just talk about what functional project I have done.

The next step is the most exciting sling session! This link is the link of the sword, light and sword, but it will be the link.

This link is the time to examine your basic skills. I won’t go into details about the specific knowledge points. You can refer to the next part.

I mainly remind 3 points:

1. To answer any question must be logical and organized.
   Example 4:

Do you know the synchronized keyword?
(2020 Meituan Interview Questions)

I believe that any java interviewer has been asked this question. This is a classic question. For this answer, I believe that most people have started the lock upgrade.

But I think a better way to answer is to have a systematic and systematic answer:

For example: The synchronized keyword is an important solution for java to solve concurrency problems.

I will answer from the following 4 levels:

• Understanding of the synchronized keyword at the use level
• The embodiment of synchronized keyword in bytecode
• The realization of synchronized keyword in JVM
• The realization of synchronized keyword in hardware

First of all, the synchronized keyword can be applied to code blocks or...

Answering in this logical way can make the interviewer feel that you are a professional person and make it shine. You can refer to Ao Bing's article, which is really easy to understand.

1. For the interviewer’s question, if there is something that cannot be answered temporarily, or is not understood. Can you say whether it can make me think about it, or honestly I don't know. Don't stop talking and get stuck, so everyone is embarrassed, after all, the most afraid of sudden silence.
2. You should take the initiative to guide the interviewer’s questions, highlight your strengths as much as possible, and answer your own understanding as much as possible, instead of reciting the same.

In short, this link is a link that requires basic technical skills, logical expression and fate hahaha. If you have the conditions, you can participate in some mock interviews to get familiar with the process, such as Ao Bing's mock interview.

At last. It is to reverse the questioning session. What do you want to ask me?

Different people have different opinions in this part, and the questions you can generally participate in are:

• Regarding the evaluation of the interview just now, what are the shortcomings that can be improved
• Understanding of technical business
• other problems

In short, this piece is quite satisfactory.

The above is all the experience of the interview.

To sum up, interview fate is very important, commonly known as fate. In the interview, try to guide the interviewer to ask questions about your strengths and answer the questions in an organized manner, rather than thinking about what to say. Finally, be responsible for any word mentioned on your resume.

Part 4: Java interview high-frequency knowledge points

In fact, if you have more facets, you will find that the core is just that. Let me cite a few high-frequency knowledge points that I think. (How it feels like the final exam outline hahaha)

I don't want to write a piece of truth, because I searched a lot on the Internet, but I feel that everyone likes to read this piece of sutra, so I still write a little.

1. Combination boxing (especially HashMap)

I think this is a bad question, and I should be familiar with the conditioned response.

Remind some unpopular knowledge: what are the characteristics of Arrays.asList, fail-fast and fail-safe, and some parameters of hashmap (and why), whether hashmap can store null values, whether concurrenthashmap can store null values, etc.

1. Concurrent programming combo box

For example: synchronized lock upgrade, object header, bytecode level, openJDK level implementation (3 queues), hardware level implementation,

The underlying principles of volatile, DCL (Double Check Lock), CAS underlying principles and ABA issues, various types of locks,

Reentrantlock, the underlying source code of AQS (especially understanding the design ideas), the difference between runnable and callable

The usage scenarios and principles of synchronization tools (CountDownLatch/CyclicBarrier/Semaphore) in java,

Thread pool (7 parameters of ThreadPoolExecutor core, 4 rejection strategies, 1 usage principle), copy-on-write, etc.

1. Threads and processes

I think this is also a commonplace question. Reminder: the difference between wait() and sleep() methods.

If you can know when to use threads and when to use processes, you can add points. For example, you know what the underlying nginx uses.

1. JVM Combination Boxing

This section is definitely a dead section where you can ask questions. Just review it appropriately. Take hotspot as an example:

For example, you need to know the JVM memory structure, if you also know the difference between different versions, you can add points.

Class loading and parent delegation mechanism, if you know that tomcat breaks parent delegation, you will get extra points.

GC Roots, JVM common parameters (please take out a blank paper to write), common OOM, four major references, and classic cases (localthread),

Four garbage collection algorithms (mark sorting, mark removal, copy algorithm, generational collection algorithm)

Top ten garbage collectors, JVM default garbage collectors, pros and cons of various garbage collectors, usage scenarios

If you can talk about CMS, G1, ZGC, the interviewer will start to shine

If you can name the 7 stages of CMS (in fact, more than that), you can also talk about concurrent model failure, background & foreground collector, incremental update + write barrier, etc., the interviewer begins to fluctuate.

If you can name the complete process of Remembered Set, Card Table, Collect Set, young gc and Mix GC, SATB+ write barrier, Marking bitmaps and TAMS, Pause Prediction Model in G1, the interviewer will start holding glasses and drooling.

If you can talk about the color point in ZGC, the interview will begin to climax

At last. For the various parameters of JVM tuning, various commands (such as 100% cpu inspection, deadlock check) and commonly used JVM monitoring tools (such as Arthas, etc.), you can also talk about the object allocation process ( Allocating on the stack), JIT, escape analysis, etc., the interviewer has a complete climax and cannot extricate himself.

In short, the JVM is a bottomless pit, and everyone controls the scale by themselves.

Design Patterns
this core understanding of the main ideas, as well as specific cases of different design patterns (this is very important, otherwise only know the concept of using a p)

such as. Don’t just answer the singleton pattern (of course, the singleton pattern is also the core, 5 ways to achieve it must be known)

Adapter mode (Callable), agent mode (Aop), decorator mode (I/O), responsibility chain mode (handlerchain), template method mode (tryAcquire), etc. will not be listed one by one.

1. BIO / NIO / AIO

This piece is also a high-frequency outbound. Search for a lot of knowledge points, pay attention to the implementation of the underlying NIO, and the usage scenarios, if you can know Netty, add points.

1. Source torture the soul (mainly Spring framework, of course, there are countless source codes such as springboot, dubbo, springcloud, zookeeper, etc.)

It is circulated in the industry that if you don't know Spring, you won't be doing Java development. Do you mean this piece is to be asked to death?

Take spring as an example. (To be honest, I don’t know how to write these knowledge points, because the system is too large), let me cite some basic parts:

Some non-technical questions (such as the understanding of spring. There is no standard answer to this, but you can definitely hear your skills)

First come to Spring-Aop

For example: the underlying principle of Spring-Aop (the principle of opening annotations), how to implement it, why the jdk proxy uses an interface (don't tell me this is a specification), the aop failure scenario and the reason, which post processor does spring use to complete the aop Yes, what is the relationship between aop and aspectj, the process of aop in spring (this must be a bonus, don’t simply think that spring is as simple as instantiating beans and then doing aop), how to set up aop exposure in Spring, the usage scenarios of aop, If you can talk about the asm used at the bottom of cglib, the interviewer will climax directly. Aop is relatively simple to get started, and I generally like to ask aop

Next is the bottomless pit of Spring-context, spring-bean, and spring-core. Which is the legendary IOC

For example: the life cycle of IOC (this can be answered to the death, from the beginning of the this() method to the end of the refresh() method, it seems that the following questions are in it. Of course, Baidu fooled it out and probably the interviewer understood it), Talk about the common extension points of spring (this can be directly asked, everyone learns by yourself, what do you not know about the extension points?), what did spring's ConfigurationClassPostProcessor do (you can directly ask through, such as the bottom layer of @configuration annotation, @Import How to deal with the three situations, how does spring parse beans, etc. What do you not know about this class?), @Autowired and @Resource in Spring (don’t tell me what bytype, it’s Baidu at a glance), circular dependencies in Spring (Why is it designed like this), the creation process of the bean in Spring, the callback of the life cycle in Spring, what do the five core post processors in Spring do, talk about the factorybean in Spring, and so on. I will not list them one by one.

Do you think Spring IOC is over? Sorry. How is Mybatis integrated with Spring (core @MapperScan underlying principle)

Next is Spring-webmvc, spring-tx, spring-cache, spring schedule

For example: talk about the parent-child container in Springmvc (why did you write so many @controller@service@MapperScan and don’t know the parent-child container?), the request process of springMVC, etc., the seven propagation methods of spring transactions, the underlying implementation, and Spring Scenarios and reasons of transaction failure, principle of timing tasks in spring, and cache in spring have been used? and many more

Next is Springboot,

For example, do you understand the watch mechanism in Springboot? Do you understand springboot automatic assembly? Do you understand the Springboot startup process?

Well, I don't want to write anymore.

In a word. The source code is the best to look at. In this piece, let's see our fate, and say that the interviewer will directly orgasm.

Everyone must develop a good habit of looking at the source code!

1. Mysql Combination Boxing

To be honest, this one can actually be asked to death, but after all, it is not a DBA.

Everyone owns a bunch of Baidu. For example, the underlying page structure of InnoDB, such as the isolation level implementation (MVCC and lock)

1. Redis Combination Boxing

Look at Ao Bing's public account. Look at the underlying source code implementation of redis.

1. Distributed transaction and microservice architecture design

The core of this piece is scene design, which is more flexible

The basic knowledge points are: CAP theory, BASE theory, Paxos & Raft & ZAB consensus algorithm, 2PC, 3PC, TCC, final consistency, Seata, etc. The focus is on understanding.

1. MQ message queue

The core of this piece is the scene design, which is more flexible, and everyone can understand the underlying principles clearly for an MQ.

1. Algorithm combination punch

The first thing to bear is the various sorting algorithms, which must be proficient in recitation, various time complexity and space complexity. If you can still know the optimization methods of different sorting algorithms, the interviewer will climax.

This is the problem of massive data. For example, the problem of topK is nothing more than the storage, processing, and operation of massive data. Mass means too much data. As a result, either it cannot be resolved in a short time, or the data is too large to be loaded into the memory at one time.

solution:

Targeting time: You can use clever algorithms with appropriate data structures, such as Bloom filter, Hash, bit-map, Heap, database index or inverted index, and Trie tree
for space: nothing more than big and small, divide and conquer (hash mapping) , Isn’t it just a large scale, I turned into a small one, and defeated each one.
If you still know Roaring Bitmap-to solve the problem of sparse BitMap space, the interviewer will climax

The last is how the bottom layer of the JDK implements sorting. If you can talk about DualPivotQuicksort and Timsort, the interviewer will climax again.

1. There are many miscellaneous items

For example: HTTPS, TCP three-way handshake and four waved hands, load balancing algorithm, characteristics of each JDK version, common linux commands, CDN (this is a question that Ali is said to be asked, very magical), sub-database and table, tomcat The underlying principles, as well as the combination of JDK (such as the difference between == and equals, the difference between stringbuffer and Stringbuilder (this can also be asked in depth), static and final keywords, four object-oriented features), cookie and session, XSS and csrf, DNS resolution process and so on.

To sum up, you can review these questions in a more targeted way based on your bu and ask the seniors and sisters whether the interviewer pays special attention to them. However, the above questions are basic compulsory questions, and it is better to master them proficiently. Of course, the more prepared the better, the above are just some of the core issues that I think are the most important, and there are many other knowledge points. For complete knowledge points, please refer to the Ao Bing official account.

Part Five: Choice of Offer

For the choice of offer, after talking with many people, I think there is basically such a big principle:

Go to the big factory if you can go to the big factory, go to the core if you can go to the core.

It is very easy to say, but in fact, the choices we encounter may be very tangled. Let me talk about some choices in special circumstances for your reference.

ps. The following comparison is in the same position. As for what is a big factory, what is a small factory, and what is the core, I believe you can understand.

1. Super large factory is not the core and small factory core, choose super large factory non-core.
2. Super large factory is not the core and the large factory core, choose the large factory core.
3. The big factory is not the core and the small factory is the core, and the big factory is not the core.

This is almost the case. Of course, you can also consider other factors, such as whether to consider conversion, whether there are requirements for the city, etc.

To sum up, the internship is here to learn! Don't be afraid to choose, just as the words written in the front say, because how much you can learn depends on you, and you must go for an internship. Don't think you can't learn things without a big factory. In a word, just do it!

Part VI: Some other thoughts

1. You have to believe that personal strength is important in the interview, but fate is also very important. So your failure to get an offer does not necessarily mean you are not good.
2. The competition is really fierce, so you need to work harder and believe that God pays for your work.
3. Don't change your goals lightly, just go to death after you make up your mind.
4. You are not alone in the fight, you have to learn to share, and communicate more with Daniel.
5. Self-study ability is very important. Remember to follow the official account, add WeChat, discuss frequently, and learn to ask questions.
6. Life is not only about work and code, but also about life itself.
7. Have an independent spirit, a free mind, and don't blindly follow the trend.
8. Never give up. Despair is vain, just the same as hope.

Part Seven: Summary

In 2020, although I have made a bad start, I believe that everything will be fine. Just like this difficult internship interview, the difficulties will eventually pass, and hope will eventually come, and everything will be a new beginning. It is also the first article of my life to write such a formal wiki haha, I should write a wiki frequently in the future (guess where I ended up in the end), I hope that after many years, I will not forget my original intention and be a qualified programmer~

Thanks to the friends who have helped me all the way, and even some friends are just enthusiastic people who have never met in the chat group.

Thank you Dachang dads for giving me a chance to study

Thank you for not giving up and persisting till now.

I also wish all the friends who work hard to get the offer they yearn for!

Written at the end

Opportunities are everywhere, but whether you can seize them depends on whether you are ready.

It took me a lot of time to typeset the entire article, not to mention the consuming experience behind the readers. You can see how a good boy prepares for a spring or autumn recruit, and the same is true for friends recruited by society. That's how it should be. If you don't fight an uncertain battle, the more prepared you are, the greater your winning rate and the greater the reward for you.

A lot of the article mentioned paying attention to my public account. It was really written by him, not by me. I laughed when I read it.

I hope everyone can find the job they like. If you work hard to enter the company you like, don't relax. Learning is going against the current. If you don't advance, you will retreat.

When the tide fades, you will know who is swimming naked.

I'm Ao Bing, a tool man who has survived on the Internet.

The more you know, the more you don’t. The talents’ [three consecutive years] are the greatest motivation for Bingbing’s creation. See you next time!

Note: If there are any mistakes or suggestions in this blog, please leave a message, please say something!

The article is continuously updated, and you can search for "Ao Bing" on WeChat to read it as soon as possible. I have prepared interview materials and resume templates for first-line companies. This article has been included on GitHub https://github.com/JavaFamily , and there are complete interview sites for major companies. Welcome Star.