Introduction
It’s the interview season again, and I have to participate in this battle. Actually, I’ve seen it since the end of last year. There are really not many good opportunities for Android, but it’s okay. 3+ years of Android development experience still has some Interview opportunities, but the threshold is not as low as a few years ago. The general experience is that small startups pay more attention to whether your project experience fits with your own, and you can directly come here to take the initiative.
In addition to fancy project experience, Dachang also pays more attention to the breadth of your knowledge. It is a survey of breadth, depth and solutions. Usually enough to work, you should accumulate temporary problems and just talk about the fur. It is estimated that it will not pass the test. . The following is a summary of some of the knowledge points that big companies will inevitably ask when they encounter interviews. I have compiled the best videos explained on the Internet for everyone, and there are various styles.
1. Introduce yourself. Self-introduction is actually a more critical process, which basically determines which questions will be asked in the follow-up session and the initial rating and positioning for you (as an interviewer for countless candidates, this is subjectively personally considered). The main point of self-introduction is to focus on one or two recent projects that you have mainly participated in or been responsible for, and emphasize the roles you have undertaken and the specific things that the roles you are responsible for. The thinking must be clear.
2. After the interview is over, basically the interviewer will ask questions or communicate with each other about the unresolved or doubtful questions. Because the interview is for an architect, pure technical issues (such as aop, bean life cycle, basic jdk concurrency, common caching methods, etc.) have not been asked, and they are directly aimed at the specific architecture and business issues in the project. discuss.
For example, the overall structure will ask why I use F5 and LVS instead of others. The questions asked include performance, how to troubleshoot, general answers (for example, I said to look at the foreground or the background first, the foreground findbugs, chrome f12, the background first to see which server load is high, top, vmstat, sar, etc., if oracle Look at awr, mysql, look at the performance schema. For application servers, look at jstack, jprofiler, etc.) After that, you will generally ask about specific indicators and so on. Basically, if the answer is clear enough, the interviewer will not ask further.
When discussing the rollback of distributed transactions, we communicated that the initiator is responsible for delivering and assigning the ID of the initiator to achieve, repeatable execution of the service and compensation. Another interviewer asked, he must make sure that the value fetched in the cache must be the latest, or it is not available. I said that first delete the cache, then insert the library, and finally insert the cache, there will be no problem, or use Handersocket is implemented so that there is no problem. Then we talked about the advantages and disadvantages of restful, nginx, rpc framework and architecture. When it comes to MQ, because MQ was studied very early, and later because the company developed a customized MQ, it basically didn’t understand the differences and implementation mechanisms of various MQs, so you can answer directly if you don’t know. The problem is not big, everyone will always have weaknesses.
Finally, generally speaking, it seems that the interviewer is a technical background, and he will usually ask whether he is concerned about new technologies outside of work. If the answer is yes, usually the interviewer will further ask which new technologies to look at, which sections of the forum, and for specific If the interviewer has contact with the new technology, he will further ask about the characteristics of this technology and its advantages over the present.
Basically, technical interviews will ask about six or seven questions. Generally, they will start from the overview and proceed to the implementation level. This is actually related to the interviewer. Foreigners generally think that the architect must write code. Although his job is not necessarily to write code, he must know how to verify whether the architecture he designed is reasonable, rather than just give it to the programmer to play freely.
When some companies or departments recruit architects or relatively advanced developers, usually the interviewer is of non-technical background or the technology is not their strong point. At this time, the interview will not discuss this issue, and it may be largely based on the 4+1 model. . If the interviewer is good at DB, he may focus on database design.
3. The technical interview ended in about 2 hours. Then, according to the expressions of the two interviewers when they went out, it can be seen that the technical level was basically passed. Then, I communicated with the supervisors of the two interviewers for more than half an hour, and finally talked to HR communicated for almost half an hour, and HR responded to the question that they would lower the level of internal communication, and then notified me. It can be considered basically done.
4. The next night I received the notice of personnel receipt, because I was not satisfied with the salary, I directly rejected it and gave the minimum requirement. The personnel said that they would communicate with the department again. After another two days, the personnel replied that the salary was adjusted according to my requirements. When I returned on May 11, the OFFER was sent.
5. Add one more thing. As part of the convention, the technical side, the second side and the personnel side basically ask about our company or other aspects. Do you have anything you need to know or want to ask? Please feel free to answer this point. The problem is not big, mainly depends on your own understanding of the candidate company or subjective wishes.
end
Based on salary treatment, with development as the ultimate goal, we must seek the best development in places with high salaries!
Below are some advanced information compiled by several Android industry leaders corresponding to the technical points above. There are ** Android architecture video + BATJ interview topic PDF + core notes and other materials . Hope to help you improve your technology. If you want to get it, you can privately message me [666] to get it for free**
In...(img-egQ9A4QM-1611477596846)]