In fact, many newcomers know nothing about interview skills according to what they don't know, so the interview was severely hit, and some even gave up. So from this article, I want to summarize some interview skills and some pits, and prepare for the success of the interview.
How did I interview Java?
I. Resume
There are only two steps to finding a job. The first step is a resume, and the second step is an interview. Let's start with the resume. Generally speaking, companies must choose from top to bottom, because education itself represents ability. But it doesn't mean that education represents everything. When we don't know the actual situation of the interviewer, we can only choose from top to bottom. Whether hr or we do technology, we all have our own standards, so you should write your resume first and let others see it. And people with different functions get resumes in different ways.
I have my own opinions on the selection of resume. Of course, different interviewers have different choices.
1. I'll see if the technical requirements mentioned in my resume meet my requirements. I value the skills he is good at in my resume. If no technical vocabulary is mentioned, then this person has the following possibilities:
1 is very watery
Number two is awesome, but the probability is very small.
No.3 can't write a resume
First, many people will lose the interview opportunity because of their bad resumes.
You will definitely ask, how should I show my strength in my resume?
You are interviewing for an engineer whose main technology is SSM technology. It is not enough to have the word SSM in your resume. It is best to reflect the ecology of SSM and your understanding of SSM.
Second, personal introduction
If the resume has passed the screening, it's time to look at the real chapter, the interview link. First, you must prepare a 5-minute personal introduction.
When I meet such an interviewer, I can't finish my personal introduction, and there is too much nonsense. Others are very tired. Since high school, interviewers have not had much patience and time. This will leave a bad first impression. The correct way is:
Briefly explain your working hours, and be good at technology stack and your job expectations.
Third, technical terms.
I used technical terms to screen my resume, which became the key part of my interview. Resume is both a technical term and a double-edged sword.
1. If you don't write professional terms, your resume is not easy to pass;
2. Write that you need to be fully prepared, otherwise your technical ability may fail in the interview;
Fourth, ask about the depth of the project
Project experience is the most important link in the interview. To fully understand the interviewer, I will spend a lot of time asking the interviewer about the projects he has done.
No one has only one project, so my question becomes: I can see that you have done many projects. Is there any project that you do best? You can tell me.
If you have any questions about learning Java (learning methods, learning efficiency, how to get a job), you can always ask me. This is my Java exchange learning button. Group: 6 15 in front, 74 1 in the middle and 636 in the back. Communicate more problems and help each other. There are good learning tutorials and development tools in the group.
When the interviewer talks about his own project, as an interviewer, there are several things to be determined: 1. First of all, we must determine whether the project is done by ourselves, that is, to determine the authenticity of the project;
For example, your project was built by SSM. Can you tell me the process of the construction project and the matters needing attention?
At this time, someone was forced to say nothing.
After careful inquiry, I was told that the project was built by other colleagues, and I was only responsible for developing the business.
2. Defects of the project
When building a project, thinking too much will lead to over-design, and thinking too little will lead to various problems brought about by business growth. There is no general industry standard for enterprises to explore best practices in a certain technical field, but the ideas can be used for reference.
But if you have experience, you can continue to refactor and really fix the defects of the project. So what? Here comes my question: How did you solve some problems in the project?
This is to examine your actual ability to deal with problems, and whether you can think independently and whether there is a brain running. This is a real personal ability.
3. The depth of the project
After the project reaches a certain scale, if you want to get greater promotion, you will definitely dig deep into the principle.
In fact, it's difficult to examine the depth of the project, and there will always be some common problems in the industry to be solved, which is why companies such as BAT and TMD often set some industry standards and open up some technical solutions.
Of course, many companies still can't reach this level, so the depth of the project varies from person to person, and there is no universal standard.
Therefore, the investigation direction has become the sustainable development, vertical field and deep thinking of this project.
Five, program basis, handwritten code, algorithm
If the interview requires handwritten codes, are all interviewers stupid?
Of course not. We can see a person's programming ability and thinking by writing code. We often look at other people's code, so the person who can quickly see your code problem, in my opinion, is above you
6. Do you love technology?
In short, even if you don't love technology that much, show that you love technology.
Seven, personal career planning
At first, I thought that the so-called personal planning was all empty talk and unrealistic things. But with more people, I gradually found out. People with career plans are really different from those without career plans. I will find that some people will make no progress in the next few years and completely confuse qualifications with skills.
Why is this happening? I guess there are the following reasons: 1. Without personal planning, everywhere is April Fool's Day;
2. Busy with management and ignoring technology;
3. Being in a position for a long time, doing the same thing, always writing CRUD；;
Eight, the interviewer's feedback
At the end of the interview, as a respect, I will ask this question at this time: I know the situation. Is there anything you think you are good at but haven't been asked?
Everyone will have their own thinking, even prejudice, so we must get the interaction and feedback from the interviewer during the interview to prove our point of view. Report a talented person's mentality and get to know the interviewer in all directions.
9. Do you have any questions for me?
The interviewer must keep a low profile, not condescending, especially as a technician. If you feel that the interviewer is a little nervous, you can talk about something else first, such as your major, where you live, and the time of commuting, so as to relieve the tension.
As for the last question, why ask: What questions do you want to ask me? There are several reasons:
1. Confirm interview feedback;
2. Give the interviewer a chance to communicate;
3. Look at the interviewer's understanding of the examination department or his interest in the company;