Recently, many companies have started to recruit in the fall one after another, but many fans have complained to me that it is difficult to recruit in the fall . To be honest, it is indeed a bit difficult now. There are many jobs in Android development positions in the past, and the interview questions are relatively simple. You can choose any offer you get. It's a pity that the market is changing now, the demand for jobs is decreasing, and the technical level requirements are still improving. It can be regarded as good luck to have an interview invitation. It is estimated that this is also what many applicants are thinking. (Don't spray!)
In the early stage of the interview, I always like to frantically scan the interview question bank without thinking. In fact, this is the wrong way. Are you sure that the interviewer will ask you the interview questions you memorized? Everyone can calm down and think about it. How many times have you asked questions in your usual interviews? It is estimated that everyone should be a little forced.
In fact, during the interview, the questions mentioned are basically based on the project cases described in your resume, so we have to brush up the questions in the early stage of the interview, and we also need to find questions for the projects in our resume. If you have extra time, by the way, you can find some related extended technical questions to understand, in case you only need it from time to time.
In addition to the importance of brushing the questions for the interview, the resume is also very important . Most people don't respond after submitting their resumes (don't panic). In fact, it can be judged that there is something wrong with your resume. Because most people's resumes have similar things, and there are basically no highlights . When our company recruited technical talents, I looked at the resumes forwarded by HR. I suspected that these resumes were written by one person (the same), or they were written too simply (perfunctory), or they were long-winded (I couldn’t find myself . technical highlights) , at that time it was not good to judge which person should come for the interview first.
In fact, everyone has had such a situation, and I was no exception many years ago. And what we can do is to constantly submit and optimize resumes, don't vote for a company only once (thicker skin, more votes) . When making a resume, it is best for you to investigate the background of the company you want to interview and the job requirements and responsibilities you want to use, and then make your own resume accordingly.
Imagine if you are the boss of a company, and now two people have submitted their resumes, A's resume is universal and can be delivered to all companies. And B's resume is specifically optimized for your company, such as adding the company's logo, responding to the company's values in personal advantages, doing research on the company's business, and so on . Then when I posted ByteDance back then, I added a line to my personal characteristics, pursuing the ultimate. I don’t know if it’s a psychological effect, but it’s over anyway. So which one would you prefer to admit? I believe the answer is most likely the latter.
Suggestion: It is best to do different companies, and there are different versions of resumes.
After continuously optimizing your resume, you will find that the probability of interview invitations is getting higher and higher. At this time, it is recommended that you leave yourself about three days of free time when you make an appointment for an interview , because we can use this time to make good use of it. Targeted review of interview questions, so as to improve their interview pass rate.
As for the interview and salary discussion, I don’t know how to tell everyone, because everyone has different expressive skills, so I will skip it here. Below I have compiled some relevant learning document notes and corresponding interview exercises (including answers) for different technical modules in Android . You can refer to and review them in a targeted manner.
