Preface
There are not many real interview time and opportunities for the cause of the 2020 epidemic. Although I have interviewed more than 1,000 fresh graduates and corrected more than hundreds of written test papers, because of the low pass rate, I have been complained by my colleagues many times. " Be merciful". Today I want to talk about my own interview standards. This is not a strategy article, it is intended to be an introduction, let us discuss how to make interviews more efficient.
What needs to be written before is that " equality" and "efficiency" have always been mutually exclusive . Information is passed from one person to another. Due to the limitation of expression ability and receiving ability, information entropy will inevitably be generated. Therefore, spending a day to understand a person’s technical strength and learning ability is naturally better than a half-hour interview. To be more comprehensive. But it is a pity that there is not such a long time in reality, so the most basic task of an interviewer is to guide the interviewer to maximize his ability in the most limited time.
Recently, the company planned to start a new project and began to prepare for recruiting one after another. Unfortunately, I was invited to be a preliminary interviewer. Recently, the interview queue was very full, so I didn’t have much time to write this week, and my daily job was screening. Resume pushed by HR, suitable for the initial test.
Friends who like my article can give me a follow, a like, what’s new in programmers, and in the circle, share it in the first time, and Android-related information will also be shared regularly!
Byte recruitment standard
table of Contents
1. Resume
2. Part of the real questions and analysis
3. Summary
1. Resume
It is said that the resume is a stepping stone . This is not a nonsense. In most cases, the interviewer needs to go through the preliminary screening of HR before getting your resume, rather than the technical staff screening the technical staff’s resume, uh~, you still Expect her to analyze resumes from a technical point of view?
The technical terms written on the resume are roughly in line with the technical requirements we provide. The working years are in the appropriate range. The overall resume is pleasing to the eye and passes through, and successfully gets the interview opportunity.
Pleasing to the eyeTM is a difficult standard to measure. It depends entirely on people’s aesthetics and mood of the day. Sometimes the resume you submit is not necessarily due to poor technology, but it may be simply not pleasing to the eye...
Tips for writing a good resume
- To be able to fake
I heard people say that my resume is very moist, but I am still half-trusted. After reading so many resumes, I really feel the water injection phenomenon of resumes. To be honest, most of these resumes are in the packaging of training institutions. There is no meaning of discrimination. I personally do not object to fraudulent resumes.
As long as the working years are appropriately increased under reasonable circumstances, the project experience is actually nothing (I had misreported half a year of work experience when I was looking for a job, and I was worried and almost didn't recruit myself). I can smooth the project business by myself. The technology mentioned, then this project is yours.
The premise is not to be too exaggerated . I have encountered a veteran with 6 years of work experience. The most recent project on the resume also states that the student management system is responsible for student management, teacher management... This project experience and working years are obviously not compatible, and it is inevitable. Make people wonder about the authenticity of your work experience. Ask a few more basic knowledge points. If you don't answer well, just pass it.
- The project is the focus (as long as it is an interview, regardless of the size of the company, you will be asked about the projects you have done, so the "answer" here will be a bonus item!)
- Show the correct way to write the project on your resume
Many people’s resumes will put the personal ability module at the forefront, and then list a lot of technologies that they have used, or that they have used in projects but are not familiar with themselves. This seems to appear to have a deep technical stack, but actually digs a hole for myself. Remember: write less about the skills that you can't or don't know!
In fact, the interviewer is more concerned about which technologies you have used in your project, which functions you have done with these technologies, what problems you have encountered when doing these functions, and how to solve them. When asked about this, the interviewer will know whether you have actually done the project or to what extent. So the project should be carefully polished.
Note: If you just graduated and you don’t have much project experience, it’s okay to work for many years. If you change it to your own blog address or GitHub project, it will feel much better, at least it seems to love learning! By the way, add more to your skill list.
It may be due to the height of the station. During the interview, I will ask about long-term development such as study route and career plan.
In my opinion, I am able to work and have the ability to solve bugs, but I also need to have a sense of foresight and long-term planning for my career development and industry development!
2. Part of the real questions and analysis
Huawei
The first side is the first time:
- Including self-introduction
- work experience
- What projects have you done, what roles have you played in the projects, what difficulties have been encountered, and how have you resolved them.
- Develop some commonly used libraries, etc.
- Finally, I asked some career plans
The second side is the written test:
Java has a lot of basics, two algorithmic questions, and then Android-related questions
The third aspect is the technical interview:
-
The interviewer started to introduce some projects, technical points and the like
-
Then catch the technical points for in-depth digging
-
Six principles of design patterns
-
How to use handlers for child threads
-
Ask how to start the local app when connecting to the webpage.
-
The four basic components of Android are Activity, Service, Content Provider, and BroadcastReceiver.
-
2 ANR (ActivityNot Respone) (no response) First introduce the Main thread (also known as UI thread, main thread)
-
Function:
1. Create UI control 2. Update UI control state 3. Event processing limitation: Main thread is not recommended to have an event exceeding 5 seconds. Condition: When the user input event does not receive a response within 5 seconds, an ANR dialog box will pop up to broadcast the receiver The onReceive() execution time exceeds 10s. Solution (principle): All possible time-consuming operations must be performed in the sub-thread () common time-consuming operations: I/O: network operation SDcard data operation -
FC(Force close)原因：1.Error OOM(out of memory error) StackOverFlowError
-
RuntimeException solution: look at the log
-
Asked specific questions about the project
-
Ask about the basic technical issues of Java, multi-threading, jvm-related. The Android part mainly asks general basic questions.
The fourth side is the comprehensive side
1. Why leave
2. Is there a career plan?
3. Outlook for the company's future
4. The salary treatment of the previous company
5. Expected salary
Byte beating
One side (3.26 on-site 30min)
- Introducing the project, I probably talked about how it was implemented, without asking for details. [I feel that the interviewer doesn’t understand android very much...]
- What is the difficulty of the project.
- Have you ever used Huawei products?
- Which items can be applied to their products?
- What are the shortcomings of the project?
It seems more than that, but I really can’t remember orz
Two sides (3.26 on-site side 45min)
- The introduction of the project is also a more general introduction, without asking the details of android implementation.
- Have you ever thought about promoting the project to the market? Have you thought about cooperating with other companies? Have you thought about combining bracelets?
- What are the defects of the project.
- [It seems that there are some project-related questions here, but I can't remember the goldfish brain. 】
- Is it local? Where do you go to elementary and junior high school? Are your parents retired? Where do your parents work? Do you have any brothers or sisters?
- What are your hobbies?
- What do you think are your shortcomings?
- If you want to introduce your project in front of five hundred people, what would you do?
- What should I do when the project is not progressing and I am very anxious? Have you ever thought about seeking help from people around you?
- How to adjust yourself when stressed.
- What is upsetting me recently? I said it was looking for an internship. He asked how to relieve this emotion, what is the state of the people around, and how do they encourage you?
- Would you like to go to Shanghai. [Actually, the interviewer talked a lot about this question afterwards. It probably means that Huawei’s internal adjustments are very fast, and business needs may make you travel frequently, or go to Shanghai and Guangzhou to work for a few years, but it’s not sure how long it will take; it is also possible. You will not be able to develop Android because of your company’s needs in the future, and you will do other things. In short, there will be many changes.]
- Have you ever understood Huawei’s philosophy and why you want to come to Huawei?
- If the pace of work is very fast, can you accept it? Maybe the pace will be very fast just after joining the job.
Baidu
Common knowledge points
Android knowledge activity scene, startup mode, life cycle, ipc, componentization, kotln, Ctrip
java aop, ioc, process thread relationship, data structure, thread synchronization
Other design patterns, sql statement
I didn’t ask any questions about the computing network, the operating system, and the algorithm questions.
- 50 minutes on one side
1. Some basic knowledge of java, talk about design patterns, and project introduction
2. Basic knowledge of Android, ipc communication, componentization
3. What third party library have you used? Have you read the source code? What can I ask you if you haven't seen it before?
4. What do you want to ask me about the current multi-process keep-alive scenario
5. Although your basics are not good, you still have to live it up for you if you master it
Two sides after ten minutes
- 70 minutes on both sides
1. I talked about the project and dug a little bit deeper. What tripartite library have you used? Have you read the source code? What can I ask you if you haven't seen it before? ***
2. Write SQL, Kotlin grammar
3. An intellectual problem, super simple rule, I didn't think of it
4. Rhetorical question
Three sides in ten minutes
45 minutes on three sides
Is a female interviewer
1. Talk about the project and talk about the difficult areas of your project (I dare not talk about it after the previous spray)
2. What is the learning route and what is the career plan?
3. Talk about design patterns
4. Scenario questions
5. Design a minesweeper game, focusing on the state change and random position after clicking
6. Anything you want to ask me
3. Summary
Many people ask me what is my career plan from Android Xiaobai to architect?
Our first entry into this business may be out of interest, maybe out of prospects. Entering this profession means that you need to keep learning, learning, advancing, and advancing.
At the beginning of our career, in order to get a job, we had to make our knowledge system more **"broad"**
After entering the job, you find that you do not need to use all the knowledge you have learned before. You start to need to advance the **"depth"** of a certain knowledge module.
At this point you have the elementary development: knowledge points
After working for a few years, you find that you need a bigger stage, and you need several in-depth studies in connected modules. At this point you have the knowledge of an intermediate engineer:
After a few more years, you are already a veteran in the workplace, and you can solve almost all daily problems at work. You have a lot of knowledge. You connect all your knowledge to form a complete knowledge system.
At this time you are a senior engineer: knowledge system
However, you have reached the age of 30+ and are about to retire. There are countless senior engineers behind you who can take your place at any time. At this point, you need to explore the deeper secrets of the code. You are no longer a "bricklayer" who only builds houses.
You know the composition and structure of each brick. You know where in a house you need this "brick" and where is suitable for another type of "brick". You know how this house needs to be built and how to design it to be stronger, reasonable and beautiful. At this point, you are an architect.
Why can't many programmers be architects? 1. A good and healthy career plan is very important, but most people ignore it. 2. Learning habits are very important. Perseverance is the right answer. 3. Programming thinking has not been able to elevate to a higher level. It is limited to coding and business, and has not considered the selection and expansion. 4. There is no good architect to guide and train around. The circle you are in has a huge impact on the growth of programmers.
Because of the length of the article, there are still many questions and answers that I have not listed. If it seems to be troublesome and requires a PDF version, I have sorted out the Android learning PDF+architecture video+interview document+source notes, advanced architecture technology advancement Top-level brain map, View, Handler, Binder, Android development interview special materials, advanced advanced framework materials , private message me [data] for free. *
