In March, I interviewed 3 major Java posts, and I summarized some interview routines


Let me first show you the job requirements of the big factories I interviewed:

ByteDance Senior Engineer:

1. Computer-related majors have a bachelor degree or above, and more than 3 years of cloud service development experience;
2. A solid programming foundation, proficient in Java development language, familiar with core technologies such as JVM, web development, caching, message middleware, etc.; 3. Experience in designing and optimizing large-scale distributed, high-concurrency and high-availability systems;
4. Proficient in mainstream open source frameworks related to Java, and understand its principles and mechanisms;
5. Have product awareness, clear thinking, good communication skills and technical learning ability

R&D architect:

1. Solid Java foundation, proficient in Java EE, database, cache, message queue, index and other technologies;
2. Proficient in distributed architecture, familiar with mainstream microservice frameworks, such as Spring Cloud, Dubbo, Zookeeper, etc., and proficient in their principles;
3. Proficient in common Linux commands, network protocols, tuning of jvm, tomcat, nginx, etc.;
4. Have strong advancing ability and sense of responsibility, excellent communication skills and team spirit, and love technical work;
5. Experience in building large-scale websites with high concurrency, high performance and high availability is preferred;
6. Experience in building complex ERP business systems for enterprise operation management is preferred.

Senior engineer:

1. More than 6 years of work experience, as a core member, participated in the development of large and medium-sized Internet Web applications, and development experience in Internet finance-related loans, payment, and settlement is preferred;
2. A solid foundation in JAVA, an understanding of basic frameworks such as io, multithreading, and collections, and a certain understanding of the principles of JVM;
3. Familiar with Oracle database, master SQL performance tuning, familiar with database principles, and have experience in separation of reading and writing, database and table splitting;
4. Have a deep understanding of various open source frameworks such as Spring, spring mvc, mybatis, spring boot, etc. (the features provided by the framework and its implementation principles, have seen the source code);
5. Familiar with distributed systems and common components: Dubbo, Zookeeper, MQ, FastDFS, Redis, ELK, etc., and understand the underlying implementation principles of RPC.

Some people may ask, how can I go for an interview if there is a huge disparity in experience requirements?

In fact, everyone in our industry understands that many work experience on resumes depend on packaging. Who does not work overtime for 3/5 months at the end of a year? If you want to look good on your resume, it is normal to pack it, and whoever is serious will lose!

To put it bluntly, I have been working for almost 4 years now, and it is true that I am going to interview for a 6/7 year position.

Okay, let's talk about business.


I cut a picture of the resume I found online

I don’t think it’s too difficult for the resume. Just change the packaging and write down all the projects you’ve done. (Speak down, in fact, if you have a project that a close colleague or friend participated in, you can also write it. A lot of details can be asked. Of course, if you have relatively rich project experience, you don’t need to do this.) In short, the project experience should be richer, and the summary should be good!

Regarding the familiar and proficient technology, it is the easiest, you can write whatever you want for your job! Just sum it up a little while writing, plus some of my good technical embellishments, it doesn’t look like I’m copying recruitment information.

Other places can be succinct and concise. Note: Don’t look like your job-hopping in this area of ​​work experience is particularly ordinary, you know what it means!

Note: This is not to tell you how to lie, it depends on the situation of yourself and the interview company! After going out, don't say it is for the teacher to teach! ! !

Project experience introduction

Project experience is mentioned in the resume, so let me talk more about it here.

The richness of project experience reflects the level of your technology. The more projects you participate in, the stronger your ability. (This refers to the people who are actually working on the project, except those who are paddling)

Another point is that your summary of each project should reflect your sense of responsibility here, that is, your expectations, plans, actions and results achieved for the project. This place is talked about right away, the STAR rule of project experience is introduced in the interview.

STAR rule
Background, design, actions, and results.
Generally, interviewers will ask a question when interviewing us. Please pick a project that you think is well done and explain it to me. At this time, we usually pick a business that we have done recently for us. A project that has significantly improved our technical indicators.
**The first is the background. **Before we explain this project, we must first explain to the interviewer why we are doing this project and what is the background of doing this project. For example, our business needs to improve user retention, and then to improve our overall user experience, etc., as well as where our system encounters bottlenecks, and if we do not do it, what impact may it have on our business. This is why we are going to do this project. And don't talk to the interviewer, because the company arranged for me to do this, I will do this.
**The second is design. **In the process of the project, we need to design our project according to the characteristics of our business and the characteristics of our users, such as the characteristics of our users, and then to achieve our business goals, in terms of technical indicators. , We need to consider the number of visits to our overall system, our QPS, our carrying capacity, the capacity of our bottom-level storage, and our subsequent six months to one year in the future, whether our system capacity growth needs Prepare for expansion in advance and so on.
**The third is action. **The action is how we proceed in the whole project process to ensure the smooth progress of our project. Here is to reflect our overall project management ability to promote and our ability to solve problems.
**Finally is the result of our project. **Many small partners actually don’t pay much attention to the results of our project. In fact, this is a wrong idea. First of all, when we explain the results of our project to the interviewer, we cannot use this relatively general concept, such as , The retention of my user has improved, and the response of my system has become faster, etc. We need to give some more specific indicators. For example, my user retention has increased from 40% to 45%, my system response time has been reduced from one second to a few hundred milliseconds, and my system has changed from its original stability. The increase from 99.9% to 99.99% and so on, here is to reflect our attention to the results of our entire project and our attention to the business.

technical problem

In general, there are three sources of technical questions in interviews:

1. The technology used in your project;
2. The technology reflected in your resume vocational skills;
3. The technology in the company's job requirements.

↑↑↑Have you made notes? ? ? ↑↑↑

Do you know how to prepare now?

Looking at the top job requirements, in fact, many commonly used cutting-edge technologies are repeated, and most companies want to investigate nothing more than these:

Specific technical issues include Mysql, Redis, MQ, distributed, Nginx, etc., such as Mysql index, clustered index, non-clustered index, back-table query, MVCC, distributed transaction transaction and other principles, such as Talk about Redis master-slave synchronization, clustering, sentinel, etc., MQ scheme selection, and how to troubleshoot Nginx logs...

Said at the end

I just have a set of technical interview questions with popular technical points. If you need it, you can privately write [Interview] or [Information] to get it for free! ! !


  • Dubbo
  • springboot
  • springcloud

Performance optimization

  • Nginx
  • ActiveMQ
  • RabbitMQ
  • Kafka
  • Memcached
  • Redis

Open source framework

  • Spring
  • SpringMVC
  • MyBatis
If this article can help you, I hope you can like it, forward it and pay attention to it, and support the editor!
Reply to [Interview] or [Information] via private messages in the background to get the above interview questions for free!
If this article can help you, I hope you can like + follow and support it!
Reply to the [Interview] or [Information] in the background, and you can get the above interview questions for free!


[External link image is being transferred...(img-JVvoieRU-1622712634455)]

If this article can help you, I hope you can like + follow and support it!
Reply to the [Interview] or [Information] in the background, and you can get the above interview questions for free!