text
From my personal point of view, write about the feelings of 30-something coders: It is indeed because of age pressure that they have begun to increase. For example, a young man in his twenties may understand everything and is familiar with the things in the group. Sometimes I wonder if I don’t have enough IQ, if my self-learning ability is too poor, if my basic skills are not good enough, if others are working hard and working overtime, you know the crisis of people in their 30s.
Personal articles
1. Would you please introduce yourself?
2. What do you think is the greatest strength of your personality?
3. Tell me about your biggest shortcoming?
4. What do you think about overtime?
Skills
1. Please talk about your understanding of java exceptions? What are the similarities and differences between runtime exceptions and general exceptions? What kinds of exceptions do you encounter in your daily work? Explain in detail how these exceptions are generated?
2. What is the difference between String, StringBuffer and StringBudilder?
3. What is the difference between ArrayList, vector, etc.?
4. Talk about what design patterns are used in development? What occasions are they used for?
5. Talk about the common design patterns of J2EE? Let me talk about the factory model in detail.
(Due to space issues, choose one question for detailed analysis. The answer is at the end of the article)
Sixth, talk about several common patterns in J2EE that you are familiar with or have heard of. Tell me more about your views on design patterns?
Practical operation
1. There are 1000 tasks here, which are divided among 10 people. How would you distribute them? First write the simplest version on paper, and then optimize.
2. Please design a scheme to assign different IP segments to each group, and you can quickly know which group a certain IP belongs to?
Interview Skills
For every job seeker, it is necessary to have an excellent resume. The company will give job seekers an interview opportunity after the resume is screened. However, many job seekers miss their favorite jobs during the interview process. How to succeed in the interview? "Details determine success or failure." Many job seekers have strong professional skills, because some details are ignored in the interview process, and a job opportunity is lost. Here are some interview techniques.
1. Preparation before the interview
- The interview materials should be prepared before the interview, resumes, certificates, etc., should be sorted together in advance. It is best to have a simple briefcase, the paper material should not have a lot of wrinkles, and keep it clean and tidy.
- Secondly, to understand the relevant information of the interview company, you can go to the company's website. If you have a friend who works in this company or is familiar with the company's situation, you can ask them to help introduce it. To understand the nature of the company, corporate culture, system and development status, of course, the more you know, the better. This allows you to understand the company's requirements for employees and their future development. As the saying goes, "Know yourself and the enemy, never end in a hundred battles", at least these contents can let you know the environment after you enter this company.
2. Punctuality and dress
It is not recommended to find a job before the interview, but to promote yourself. With strong professional skills, the appearance should also be paid attention to. The examiner's first impression of you is very important. So programmers should pay attention to the following points when interviewing.
-
Punctuality. Plan your interview schedule in advance, try to avoid rush hours, and don't delay time due to traffic jams. If possible, familiarize yourself with the route in advance. There must be a backup plan in case of emergencies. If you cannot attend the interview on time, it is best to notify the other party in advance.
-
You don’t need to be over-prepared in terms of dressing. Generally speaking, the dress for technical interviews is comfortable and clean, but you should have a good mental state. A full mental state will make you feel confident.
In addition, during the interview, keep eye contact with the interviewer to show that you are friendly, sincere, confident and decisive.
3. How to stand out in an interview
If job applicants are fully prepared before the interview, they will have considerable confidence to cope with the interview.
-
As a fresh graduate or a programmer who is looking for a job, when you apply for a job in programming or software development, the recruiter will always arrange a written test to test your programming ability. The test questions include computer knowledge, programming and logical analysis, etc. The program design interview questions are mainly about program design, IQ questions and various computer-related technical problems.
-
Before participating in the interview, you must review the programming language you may use, and get your best code. Because writing code is the highlight of the program design interview process, it is an opportunity to show that you have the ability to do the job. Performance in answering programming interview questions is one of the important criteria for most computer companies and software companies in deciding whether to hire someone.
-
The actual interview questions of the program are usually quite difficult. On the one hand, programming interview questions are to test your ability to write code, and on the other hand, to test your ability to analyze and solve problems. Most interview questions basically take an hour to get the answer, so it is normal to not find the answer to the interview question immediately. Don't be discouraged by this.
-
In addition, don't start answering the question before you have figured it out. Starting with an example can further deepen your understanding of the question. After writing, find an example to verify the code you wrote, and check whether your code has considered all kinds of error conditions and special cases.
-
Most technical interviews will have some non-technical questions. These questions generally appear in the early stages of the entire interview process. The purpose is to determine your work experience and job search goals to see if you are qualified for the position.
Non-technical issues seem to be relatively simple, especially when you have already broken through the tough technical tests. But non-technical issues are also very important and must not be taken lightly.
Answer points
-
Although non-technical questions are simple in form, they are not easy to answer because there is no right or wrong answer, and each job seeker’s answer is different. The purpose of non-technical questions is to understand the job applicant’s personal experience and work ability and compare it with other job applicants. The so-called personal experience includes your work experience, as well as your knowledge and level of knowledge.
-
Sometimes, even if you do well in answering technical questions, if your previous personal experience is not commensurate with the position, you may not get the job. Therefore, you must be cautious when answering questions about personal experience-such questions are usually a signal that the interviewer doubts you are competent for the job. At this time, the principle that you should most follow is to promote strengths and avoid weaknesses, not to be humble or overbearing.
-
Finally, the examiner will usually tell you a time to reply to you, sometimes there will be no response. For job seekers, it is recommended to contact the examiner, call or email within one week after the interview, to express gratitude, and to ask about the result of the interview. Of course you can express your enthusiasm for this job. Many people ignore this link. After the interview, the company may also lose some applicants. It may bring a great turn for the better.
Not every interview is smooth sailing. If you fail once, you should pay attention to summarizing the experience and lessons of this interview. This will save you huge wealth for your future job search. I believe that every job seeker who works hard will win his favorite job.
The author switched from Java development to Android development in 2013. He has been in a small factory, and has also been to a large factory such as Huawei and OPPO. In April of 2018, he joined Ali until now.
I have participated in many interviews and interviewed many people as an interviewer. I know that most junior and intermediate Android engineers want to improve their skills. They often grow up on their own. The unsystematic learning effect is inefficient and long, and it is easy to encounter the ceiling technology stagnation!
I have compiled a list of the most systematic Android development mainstream technologies at the Ali P7 level, which is especially suitable for in-depth learning and improvement of friends with more than 3-5 years of experience.
Mainly include Ali, and the mainstream architecture technology of ByteDance, Tencent, Huawei, Xiaomi, and other first-line Internet companies. If you want to learn Android development in depth and become a qualified senior engineer, you can bookmark these advanced Android technology selections
I have collected and sorted out the interview questions of Alibaba, Tencent, ByteDance, Huawei, Xiaomi and other companies in the past few years, and sorted out the requirements and technical points of the interview into a large and comprehensive "Android Architect" interview Xmind (in fact, it is better than Expect to spend a lot of effort), including knowledge context + branch details.
Java language and principles;
big factory, small factory. Android interview first see if you are familiar with the Java language
Advanced UI and custom view;
custom view, the basic skills of Android development.
Performance tuning;
data structure algorithms, design patterns. All of the key foundations and key points need to be skilled.
NDK development; the
future direction, high salary is bound to be.
Cutting-edge technology;
componentization, hot upgrade, hot repair, frame design
There are a lot of materials for learning Android on the Internet, but if the knowledge learned is not structured, and when you encounter problems, you just taste it and don’t study it in depth, then it is difficult to achieve real technological improvement. I hope this systematic technical system can provide you with a direction reference.
When I was building these technical frameworks, I also sorted out the advanced advanced tutorials of the system, which will be much better than my own fragmented learning effect, which can be seen on GitHub; "Android Architecture Video + Study Notes"
Of course, it is not easy to learn and master these abilities in depth. Everyone knows how to learn and what work intensity is as a programmer, but no matter how busy the work is, I have to spare 2 hours a week to study.
8%AF%95%E6%8B%BF%E9%AB%98%E8%96%AA%EF%BC%81.md)**
Of course, it is not easy to learn and master these abilities in depth. Everyone knows how to learn and what work intensity is as a programmer, but no matter how busy the work is, I have to spare 2 hours a week to study.
Within half a year, you will be able to see the changes!