What do you need to prepare for the Android development job interview in Dachang? [Attached interview questions from big factories]

foreword

insert image description here

It is the peak period of changing jobs in the "Golden Three Silvers and Four". In the cold winter of the Internet, it is particularly important to seize the opportunity. So as Android engineers, what aspects should we prepare for? For example, whether unfamiliar skills should be written on the resume, which Android components to review, and whether it is useful to brush up the algorithm questions, you may carefully consider these questions before the interview. **In the following, I will combine my own experience and understanding to help you sort out the content that needs to be prepared for resumes, interviews and algorithms, and share some of my experience.

Resume

The resume will play a vital role in the interview process, we need to pay great attention to the writing of the resume.

During the interview process, the interviewer usually pays great attention to the three parts of your resume: work experience, project introduction, and skills . Part of the content to ask. One thing to pay attention to here is the writing of relevant skills, core ideas, and resumes for those who want to enter a big factory. You must highlight your own characteristics and write vividly . You can see from your resume that you are strong . If the resume is not good enough, there is a high chance that there will be no interview opportunity at all.

First of all, you have to let the interviewer know what your interview rating is. Many times a position corresponds to many ranks. When submitting your resume, your resume needs to be given a clearer grade by the interviewer, otherwise the interview process will be more passive and will affect the interviewer's judgment on you.

Therefore, the content of this part needs to highlight your own strengths, and also write some issues that the company is relatively concerned about:

For example, if you are familiar with plug-in, hotfix, componentization, performance optimization, etc., you can write it clearly, but if you are not very familiar with it, try not to write it.
If you are familiar with certain parts of Android, you can write in more detail. For example, if you are familiar with Handler and Binder mechanisms, you can write "familiar with common Android mechanisms, such as Handler and Binder mechanisms."
Seeing that you are very familiar with this part of the content, the interviewer may go deeper when asking questions, so you must prepare in advance how to explain this part of the content, which can basically be explained from the advantages, key points, and difficulties of the mechanism.

Interview

For Android engineers, some algorithms and basic knowledge of Android and Java will be asked at the beginning of the interview.

For Android interview questions, most of them are related to the principle of the system, but there are also many questions without accurate answers, such as the principle of the four major components, you need to explain the four major components from a macro perspective, or You can also break it down and explain it one by one.

Some components frequently used by Android must be understood clearly, such as:

The mechanism of Handler.postDelay
Touch Event Mechanism
Custom View
How to calculate View size
How container controls lay out child controls
Basic operation of database
Binder mechanism
LMK mechanism

In addition, the interviewer may also ask about the principles of open source frameworks, and I suggest you learn more about them:

Excellent web framework

Image loading framework

logging framework

EventBus

Principle of AAC framework

There is also performance optimization. In recent years, the company has paid a lot of attention to performance optimization. Some students may have done special performance optimization or developed some tools and summarized some methodologies. This is a better answer. However, most small partners may usually pay attention to the development of business requirements, and there may not be many actual combats for performance optimization. Here to share this "Android Performance Optimization Practical Chapter", which is very suitable for those who lack practical experience! Scan the QR code to get the complete document.

"Android Performance Optimization Practical Articles"

Most of the interviews will start with the project, and you need to make detailed preparations for your project before the interview. For example, the interviewer will:

let you introduce your project
You need to reflect the difficulty of the project
your contribution to the project
Project implementation, etc.
Some specific details may also be asked, so the suggestion is to talk about it realistically, but you must be very clear about your own modules.

In addition to technical interviews, sometimes some soft skills may also be examined. For example, the interviewer will examine your cross-departmental collaboration ability, communication ability, time management, task allocation and career planning, etc.

When you can answer all the questions you expected, you need to dig deeper into the technical details and depth. For example, I developed a PLT Hook tool in my work. This tool may be modified by referring to open source projects and encapsulating it. The details are not well understood. At this time, you have to do a systematic study of the content involved in this open source project.

As far as the algorithm is concerned, "catch-up" is not very useful for the learning and accumulation of algorithms, so we need to spare some time to review in our busy work. You can also go to LeetCode and LintCode to brush up questions. In addition, although most of the algorithm questions in the interview are simple questions on LeetCode, you also need to pay attention to some classic questions of medium and difficult difficulty.

Summarize

The preparation for the interview is actually accumulated bit by bit during our usual work, and the review is only a means of consolidating knowledge before the interview. The review process is mainly about sorting out and summarizing the knowledge points. You can think about the problems you may encounter during the interview and how to express them. But I would like to say that although the preparation of "scratching Buddha's feet" may sometimes be useful, it is difficult to understand the deeper content of a certain knowledge point by "surprise" in a short period of time, and the breadth of knowledge also requires time and experience. to accumulate. So no matter whether you need an interview or not, you need to think more, train more, and summarize more in the usual work process, and you can accumulate a lot when you need it.

Here is a copy of "174 Questions Required for Android Interviews in Big Manufacturers" Scan the code to get the complete document for free!