I have participated in interviews with many companies since years ago, and received offers from several giants, as well as from other companies. Summing up the experience is also a review and summary of the past.
1. Resume
There are a lot of guidance on programmers’ resumes on the Internet, so I won’t repeat them here. You can search for the summaries of other great gods on the Internet and modify them according to your own situation. I have a few suggestions:
-
1. Try not to be fancy. Programmers and designers or product operations are not the same. The decision whether our resume is successful or not depends on the technical interviewer, and what they value is your project experience content and technical description.
-
2. Try to write only what you know and understand deeply in the skill description. You can add some new technologies or popular frameworks appropriately, but this part needs to be understood. If you don’t have time to read the source code, you can read the summary of it by the masters. heap.
-
3. Try to add keywords in the project experience section, such as what technology is used, which design patterns are used, optimized data comparison, extended summary, and the like. Instead of blindly introducing the content of this project (that is the description of the product manager), such as performance optimization, it is divided into UI performance optimization, memory optimization, database optimization, network optimization, power consumption optimization and so on. It can be described from 1. how to find the problem, 2. how to solve the problem, and 3. the comparison of the solution effect. To give a simple example - UI optimization, what problems can occur in the UI (stuck and not smooth), how to find the problem (mobile developer permissions > GPU over-drawing to find layer problems, TraceView CPU usage analysis), how to solve the problem (reduce Hierarchy, custom View drawing problems, etc.), after solving the problem, compare the performance again.
2. Interview process and interview questions
Interview: If you do not prepare adequately for the interview, it is a waste of time and irresponsible to yourself!
Especially those who are in a hurry to get on the job, but have not fully sorted out their own technical points, they will be cast in the sea, time is running out, and no one will read their resumes.
Generally, you can submit your resume after you finish writing it. You can find a friend to refer you or Lagou.com or Boss to directly hire and deliver it directly, which is faster.
The general interview arrangement is 3 rounds of technical interviews and 1 round of HR interviews, and some companies may increase or decrease.
In a technical interview, you will generally introduce yourself first, then ask about the project you have done, check the basics, then write an algorithm, and finally ask if you have any questions.
Self introduction
Self-introduction generally mainly tells about where you work, your current work situation, how long your work experience is, and what you have done, especially highlight your highlights. It's good to prepare this in advance.
Project experience
After introducing yourself, the interviewer will look at your work experience, pick some questions for you, or directly ask you to introduce the best things you have done.
When you write about your work experience, you must be very familiar with the responsible part, which can withstand the torture of the interviewer. If you only participated in it, you should try your best to be familiar with it, otherwise, don't write it up.
Everyone's experience is different and what they have done is different, so I won't sort it out for everyone.
Base
After asking about the project, it's time to inspect the candidate's foundation, which generally includes Android foundation, Java foundation, Android's commonly used open source frameworks, design patterns, network foundation, and so on. Let me list the common inspection points below:
- Java basics, reflective class loading and dynamic proxy, generics and annotations, concurrency, JVM (high frequency), etc.
- Android foundation, Handler communication mechanism, cross-process communication method, Activity startup mode, memory optimization, layout optimization, View drawing process, Android event distribution mechanism, animation classification and its principle, MVC, MVP and MVVM mode, SparseArray principle, etc.
- Android open source framework, Volley, OkHttp, Retrofit, Glide, Picasso, EventBus, RxJava, Router, etc.
- The basics of the network are generally questions and answers for HTTP and TCP, three handshakes and four waved hands to remember.
- Six Design Patterns
- other
On the one hand, you can directly read the source code for these basic knowledge, on the other hand, you can search for related articles on the Internet to learn. I have also compiled some related common interview questions here. If you need it, you can get it for free at the end of the article.
other
In addition to the above, the interviewer may also ask about the reasons for job-hopping. I usually answer from the perspective of personal technical growth, so I won’t go into details.
Finally, the interviewer may also ask you what you want to ask. Generally, we have to ask about technology and project-related things, such as what kind of technology stack you use, what is the size of the team, and what will I do when I come? What kind of work and so on.
Nowadays, many people complain that their resumes cannot be submitted, interview salaries are very low, they doubt themselves and the market, but if you think about it carefully, it seems that this is the case from childhood to adulthood. Excellent people will never have such problems, teacher Those who hope are often students with good academic performance.
If we want to be excellent, we should see what those excellent people are learning and doing, and try our best to communicate with them; go out and see the world more, and then force ourselves to learn from death.
In this way, you will not feel powerless when you have a mortgage or a car loan. Those who really find a good job are those who improve silently.
Summarize
Learning technology is a slow and arduous road. It cannot be learned on the spur of the moment, nor can it be learned by staying up for a few days and nights. You must develop the habit of studying hard at ordinary times. So: Persistence is the most important thing!
So how can we make our answers fluent in the interview?
The answer, of course, is to improve your own strength during work or study.
And the technical points involved in the interview do not know such a little, we still need to learn a lot. In fact, no matter what, no matter what kind of interview, no matter what kind of interview, if you want to avoid being abused by the interviewer, you have to max out the interview questions and make comprehensive preparations. Of course, in addition to this, you need to lay a solid foundation in your daily life , so that no matter how the interviewer digs into a knowledge point, you can handle it smoothly~
For future development and if you want to find the direction of advanced learning, click the card below to get a free consultation and receive an Android architect advanced learning roadmap~
