Preface
An old friend found him that day, hoping that he can help his son who is about to graduate and revise his resume to have a better starting point. This P8-level boss does not pay much attention to this matter (this young man himself is better , Graduated with a computer major, job-seeking Java development), I took the time to help modify my resume, and by the way, I helped to make up for simple techniques;
Normally, a fresh graduate with an excellent resume, good academic qualifications, and skills has also been used to make up for it. It is generally not very miserable to enter any major factory interview with the guidance of Ali P8; so he started the job hunting journey, and it turned out that A friend lost his pass when he was on Huawei. . . .
This slapped the big cow hard on the face! ! !
After repeated questioning, I finally found the problem: this young man may not be very lucky. He met a serious interviewer. The aura of the interview room was crushed and the whole interview was always tense. , The whole body is tensed; committed a problem often made in a programmer interview [saying too much]
Ok? Is it because people who say too much will be passed?
The five most common reasons why programmers fail interviews
In order to find a high-paying job, it is the most basic to learn solid basic knowledge and professional skills, but it is impossible to express what you have learned during the interview. It is like cooking dumplings in a teapot and cannot be poured out. , The chance of being accepted will be greatly reduced. How can we successfully interview for a job? The following is a summary of the reasons for the failure of the interview, as long as you avoid entering such misunderstandings during the interview.
One reason why Java programmers failed interviews: too little said
Programmers’ poor speech is a common problem in the IT industry. All their language expressions are replaced with codes. Usually, they can only hear the keyboard sound in the office. There is almost no language communication. It may be professional reasons. Programmers The expressive ability is extremely poor. The most obvious performance in the interview is in the non-technical aspects, such as self-introduction, project introduction, etc., everything that has nothing to do with hands-on coding can not come. Even the introduction of the project process and the sections that you are responsible for are all stumbling. In this way, The interviewer will feel that you have no passion for the job, and the whole interview process is a bit awkward, and the impression is average, or even poor, so it is difficult to succeed.
Reason two for the failure of the Java programmer interview: talk too much
In addition to the dense type (exaggerated type) of this part; more pass away are those who are eager to explain themselves; some programmers are eager to prove when they are asked a question (especially if they don’t understand the question) For yourself, use more words to cover up your shortcomings, but you have to pay attention to that, normally the interviewer’s skills are better than yours, or if you can ask this question, you must have a good understanding of this technical point, and the more you say Then the more shortcomings are exposed, it is necessary to master the heat when explaining, I don’t know if you can get to this point;
The third reason for the failure of Java programmer interview: the basic knowledge is not firmly grasped
Many times, companies, especially large companies, do not have particularly high requirements for resumes. It does not necessarily have to be how gorgeous a resume is to be matched. In many cases, super first-line Internet companies value the mastery of basic knowledge. The foundation is also the most important thing. Many programmers fall into this when interviewing Internet companies.
Four reasons why Java programmers failed to interview: failed to answer the interviewer’s difficult questions
The interviewer may give some urgent questions during the interview and ask you to give solutions. Of course, when faced with this kind of emergency, you will generally be nervous and it is inevitable that your brain will short-circuit, but a mature professional will give a complete solution. Thinking, this situation is understandable after all. The most fearful thing is that I can neither type out simple codes nor have any ideas to solve problems, let alone give solutions. Once this happens, the interviewer can only say embarrassed to you.
Five reasons why Java programmers failed interviews: improper words and deeds
Many well-known companies, especially those with obvious labels in their corporate culture, will pay great attention to the performance of this area. Not to mention such a big one, but from a small point of view, even an ordinary person, we ourselves, will like to be polite and civilized. Appropriate people also hope that there will be one more colleague like this, and the cooperation is smooth and full of tacit understanding. The editor recommends that during the interview, you must pay attention to proper clothing, not shaking your legs, be modest and cautious, and not quarrel with the interviewer.
From the above five frequently asked questions, it can be seen that some programmers interviews really answer the opening sentence: **"Dumplings can not be poured in a teapot" **What should programmers do in response to this situation? ?
A collection of interviews compiled for him by Ali P8 closed for 48 days
The interviewer usually has a comprehensive understanding of the interviewer's knowledge structure in just two hours. If the interviewer is procrastinated and cannot directly address the essence of the question when answering the question, it will be difficult to fully express himself and ultimately affect the interview result. In response to this situation, this book does not procrastinate when explaining the knowledge points, and strives to be concise. It introduces in detail the core knowledge points that Java programmers are often asked in interviews. After being familiar with it, the interviewer can show one percent of the interview. Bai Er's strength;
There are 9 chapters in this book, and the contents of each chapter are as follows:
Due to space reasons, it is not possible to show all of them . Friends who need this Java core can pay attention to me and get the full PDF version for free;
Chapter 1:
Explain the principles of JVM, involving JVM operating mechanism, JVM memory model, common garbage collection algorithms and JVM class loading mechanism.
chapter 2:
Explain the basics of Java, involving collections, exception classification and handling, reflection, annotations, internal classes, generics, and serialization.
Chapter 3:
Explain the knowledge of concurrent programming in Java, involving the working principles and applications of Java multithreading, the working principles and applications of Java thread pools, as well as locking and process scheduling algorithms.
Chapter 4:
Explain the knowledge of data structure, involving stacks, queues, linked lists, hash tables, binary trees, red-black trees, graphs and bitmaps.
Chapter 5:
Explain the common algorithms in Java, involving binary search, bubble sort, insertion sort, quick sort, hill sort, merge sort, bucket sort, radix sort and other algorithms.
Chapter 6:
Explain the principles of network and load balancing, involving TCP/IP, HTTP, common load balancing algorithms, and LVS principles.
Chapter 7:
Explain the principles of databases and distributed transactions, involving database storage engines, database concurrent operations and locks, and database distributed transactions.
Chapter 8:
Explain the principle and application of distributed caching, involving the introduction of distributed caching, the principle and application of Ehcache, the principle and application of Redis, and the core issues of distributed cache design.
Chapter 9:
Explain design patterns, involving 23 common classic design patterns.
Those in need of the above-mentioned Java core narration can follow me and get the full PDF version for free;
Read suggestions
The catalog of this book is meticulous, and readers are advised to use the catalog as a reference to review the past and learn the new after reading the book, so as to achieve the purpose of understanding. It is recommended that readers spend 3 weeks to read carefully and understand the knowledge points, codes and architecture diagrams in the book in detail; spend another two days to review, recall the knowledge points against the catalog, and check the missing parts in time; before the interview Spend 3 hours to review to fully grasp the knowledge points of this book. In this way, readers can have a fuller understanding of the breadth and depth of each knowledge point in the book, and will be confident in the interview.