Two days ago, the circle of friends brushed a buddy into the byte, and I realized that the gold three silver four have passed most of the time. In fact, it's not just this buddy. I feel that many of my friends have changed jobs during this time period. After all, every jump in wages will have to go up.
Everyone knows that I am from a technical background, so most of my friends are developers. Yesterday, I chatted with the buddy who just entered the byte about the interview. He said that interviews at big factories are too difficult now, that is, I have a solid foundation, otherwise I would have been cold and thoroughly. I immediately asked him to summarize his interview experience and some experiences . After all, everyone knows the difficulty of byte interviews, and it is not ordinary.
The interview is divided into 4 rounds: 3 rounds of technical interview + HIR interview
1. One side: the basic side, asking a lot of underlying foundations (compile-time technology Buterknife, virtual machine, memory leak, concurrency, etc.), generally based on the information on the resume (project) + algorithm
2. Second side: project experience + position direction Foundation (Framework and Performance Direction) + Algorithm
- Franwwork level interview: AMS PMS Binder U draws the process and relies on more event distribution
- Performance optimization layer interview: startup optimization, U optimization, ak volume optimization, I0 optimization, stuck memory optimization, etc.
3. Three aspects: still project experience + professional knowledge (asked a lot about architecture), and some technologies that I usually specialize in researching
- Architecture: Glide's caching mechanism, OKhttp request mechanism, componentized plug-in, mvc, mvmm/mvpRxiava, Jetpack, etc.
- I am also specializing in compose, kotlin, audio and video, etc.
4. Four sides: HR side, HR side is similar, mainly concerned with why, career planning, hobbies, personal management, etc.
Summary :
- Byte interviewers are generally very patient (1 hour +), and they will ask very detailed questions (you need to be hard on yourself, some questions will be asked very deeply, and you will understand your technical depth), which is a test of professional skills.
- The algorithm requirements are not high, and the sword refers to the difficulty of ffer. But - it must be, and those who won't generally hang up.
- The interview efficiency of Byte is very high, the stock will go to the next interview the next day, and sometimes the next interview directly (doesn't give too much time to prepare).
In addition to these, the boss also shared his experience as an offer harvester, including the preparations to be done before the interview, the routines that can be used for reference in the interview, etc. , such as
- Use your resume to get more interview opportunities
- When introducing yourself, immediately and comprehensively throw out the technology stack and highlights
- First introduce the project background and dispel the interviewer's questions
- Use project examples to illustrate your technical fundamentals
- Use examples to illustrate your experience with performance optimization
- ……
More detailed content, I have all organized in the document. Whether you are going to a big factory or not, the experience of the boss is very useful, and it will definitely help you!
In addition to the face-to-face, the boss also generously shared a set of Android interview questions for his own use .
In his words:
Whether you can enter a big factory depends a lot on your interview performance . It is not enough to rely on the accumulation of skills in your usual work, you must master a lot of routines. Technical, project, communication... There are many routines to follow. And if you want to learn these routines, the fastest and most useful way is to brush the questions , brush the high-quality real interview questions, there is no one!
Whether you want to improve the internal strength of Android in the short term, break through the bottleneck of your ability in your work, or prepare to participate in the Android interview, you will gain something in the middle.
In order to facilitate your understanding, I will use the "knowledge point + project practice" explanation method , focusing on summarizing practical experience at work, and sharing some solutions to difficult problems with you, so that you can have a methodological approach in your future work. guide.
Summarize
Many job seekers complain that big companies "build rockets in interviews and screw screws in work", but in fact, most of the questions in interviews are all-round tests of your depth of understanding of technology and ability to solve problems. Your seemingly unreasonable or even useless questions, such as "Have you ever written a custom Gradle plugin?", are actually the interviewers who want to take this to see your understanding and mastery of Gradle, and then extend your understanding of the Android compilation and packaging process. understand. Under the premise of being familiar with the compilation and packaging process, you will be well versed in the principle and process of APK deep slimming.
It sounds like various routines, but the technology is endless. You need to be responsible for every line of code you submit, every tool you use, and constantly dig out the underlying principles in order to sublimate your technology to a higher level. If you need the full version of this guide, please visit my GitHub for access .
GitHub地址：
https://github.com/733gh/Android-T3