1. The essence of the interview is to tell the interviewer what you would do
This is a common mistake many people make when they are just starting out. They don’t know exactly what the interviewer is asking. They are not really trying to figure out what you mean, they are just trying to figure out what you are going to say. (Turn to music byte)
For example: How do you use caching in real projects?
First line answer: use redis, key-value store
However, the interviewer may want to know: what kind of data is generally cached in the business, why it is cached, how to ensure the real-time performance of the cached data, what impact the failure of the cache will have on the normal business process, why we choose REDis, and the implementation principle of REDIS, etc.
As long as you can answer in depth and thoroughly on one aspect of the topic, the likelihood of doing so increases substantially.
If you don’t know how to get back to the topic when you hear it, or if it’s easy to say in a few sentences, then it’s basically hard for you because you don’t have enough knowledge to say anything about technology.
2. The higher the salary requirement, the greater the probability of admission
I interviewed a recent graduate who said he was proficient in Java, mysql, and Spring on his resume, and I asked him what salary were you looking for?
His answer is 4K. Regardless of whether what he wrote on his resume is true or not, one thing is very clear: if you buy meat in the market, others are selling it at 30 yuan per catty, while there is a roadside stall that only buys 10 yuan per catty, will you buy it?
In addition, I want to tell you that generally speaking, for a regular Internet company, it really does not care about paying more wages, the most important thing is talent;
Or let’s think for a moment, suppose you are the project manager, you hire people to help you do things, you will save a little salary, to hire poor skills, to help the boss save costs, their own slowly to bring people, to find a lot of things?
And, speaking from the heart, people will only focus on a point, if you expect to pay a little higher, so he is considering whether to admit when you consider the salary problem, or is to consider your technical issues, but the salary is the boss, technology is their own use, so in some ways if some technology about with you, But in the subconscious, because your expect salary high and think that your better technology, finally admitted to you, it’s like assuming that we want to buy a feather coat, look at the two at the same time, a 800 yuan, another 1000 yuan, I believe that most people would think the 1000 yuan this quality better, add money to buy this dress isn’t you, So which one would you choose?
Finally, a reminder that expecting a higher salary is not borderless, so how much is appropriate?
There are two aspects to consider: one is the working years, generally speaking:
Starting line: 8K to 12K 1 year to 2 years: 10K to 15K 3 years to 5 years: 13K to 22K 5 years or more: 18K or more
Of course, there are some regional differences, but not much.
Another aspect is to refer to the work standards of large companies. Open the recruitment information and check the recruitment information of large companies. Generally speaking, it is given a range value
Such as:
30*0.8=24 then the expected salary of 24K is appropriate.
3. Your resume lists the most difficult skills
I’ll briefly explain why. There are a number of skills listed on a resume that reflect the following:
1. Do not know what the core skills of Java engineers are, and give the interviewer the first impression of being an amateur!
2. The more skills you list, the more directions the interviewer will ask you for. You won’t be able to master them all, and you’ll end up knowing only a few of them.
3. It completely reveals that you don’t have any working experience. I have seen some write on it proficiency in Ms Office, foreign language level, COMPUTER Rank 2 and so on.
How do you write interview skills?
Based on personal experience and interview feedback, my personal suggestions are as follows:
1. Write two technical points of mastery or in-depth research, such as: multi-threaded high concurrency, JVM in-depth research, etc.
2. Write three familiar applications, this is best to write common framework, such as: SSM, etc.;
3. Write three skills that you know and can use easily, such as automated deployment, full text search, front-end related frameworks, etc.
The skills section should subconsciously lead the interviewer to ask about topics you have already prepared;
4. The key to writing a test is to show that you’re taking it seriously
The first thing you need to understand is that it doesn’t really matter if you do a penned test well or badly, if you do it right or wrong, if you take the penned test seriously.
This may be difficult for people without years of work experience or experience in team development to understand. In fact, most interviewers focus on the following three points:
1. Do you get along
2. Initiative
3. Think logically
Note: I do not mean that people with no basic knowledge of the above three points will be able to interview, but I mean that people who have basic knowledge of programming will be able to interview easily.
5. Be confident with yourself
First of all, being confident in yourself does not mean disrespecting your interviewer.
The main idea here is that throughout the interview you want to make it seem that you and the interviewer are equals, that the interviewer is picking you and that you are picking the company;
6. Learn your resume but use your strengths and avoid your weaknesses
In fact, this is how we often talk about how to package a resume.
Honesty and trustworthiness, do not write false resume this is the most basic professional ethics;
However, it is necessary to make full use of your strengths and avoid your weaknesses. It is just like a company advertising its products to the outside world.
7. Your boss is a smart person, so be honest when talking about your dreams
This is usually the last part of the interview,
You have to come across as a sincere, hands-on technician,
Do not let people feel that you are a impetuous, ambitious low person;
8. We must prepare repeatedly for battles we are not sure of
This is a very, very important part of the interview, but also a lot of impetuous most likely to make mistakes.
Its core idea is actually: the interview must be systematic and careful preparation!
9. How to prepare systematically and carefully?
The following 7 steps are summed up in practical experience for your reference
1. The most basic requirements, skilled in THE SSM structure of CRUD+ advanced query + paging + login + registration + logout + purchase + order.
2. Systematic knowledge points, systematic combing of knowledge points and systematic look at the interview questions, and forcibly divide knowledge points into 3 categories, proficient, skilled, understanding, do not look at the east and west, finally will let you impetuous heart directly in the interview collapse.
3. Write a resume, the resume must be in the eye-catching position to reflect the technical points (HR will recognize a few keywords, decide whether to notify you of an interview), if the sent out resume interview invitation rate is less than 60%, it must be written wrong, the best professional to help you look at the resume.
4. Mock interview (three times) to improve the interview pass rate. The cost of the interview is actually quite high, finally received the interview notice, the painstaking drive to find the way.
When you go to an interview, it’s not worth it to make the usual silly mistakes. The sooner you get a job, the sooner you get paid (the average programmer’s salary is around 500 a day).
Go out for an interview, but not for the sake of it, but to ease your nerves and get used to the technical communication with the interviewer (many people get an offer at this stage).
Immediately after the interview to recall and record the interview asked those questions, their general is how to answer, and then discuss with professional reply whether appropriate, must ensure that similar problems will answer better next time, otherwise also won’t have a lot of time to improve the interview, because in your answer well or clearly wrong places the interviewer will not point it out to you, that is why, A lot of people go out and say they did a great job, and then they tell them to wait and… There is no then ~
Again, talk to professionals immediately after each interview. You’ll find that everyone asks the same questions. You’ll find it so easy! When you get multiple offers and choose just one, it feels like you’ve made it to the top of your life!
7. Through the probation period, although all say interview work planes, screw, but estimates for just into the people, there are still a lot of the technology of no contact or do not understand, then don’t understand, be sure to ask more, ask more colleagues on business, technical study to himself, if still don’t understand will ask professional person, really don’t understand, ask colleagues, All in all, be proactive!
10. Work hard enough to have a choice
Many people advocate that choice is more important than effort, but the more important thing is often overlooked, that is: only enough effort can have a choice.
This creates a loop, or as we programmers call it, a deadlock. Choosing a good company to work for is very important to your career prospects, but only if you can get an offer from a good company!
11. Work for a company you really want to work for
I’ve met a lot of people who, when I talk to them, have similar feelings: They don’t want to work here at all, but it’s hard to find, so they stay there for years.
What kind of suffering it is to go to work every day with a reluctant mood, and I believe that it is difficult to make outstanding achievements, at best, to finish the work, what is the point of doing so!
If you are just entering the line of small white, suggest you first collect, keep looking for a job when used, can also take this as a guide, more targeted learning, if you want to learn popular IT technology faster, Letbyte high salary IT free trial course welcome you to.
This article is from Lebyte
Finally, we recommend two b station super detailed Java self-study full set of courses: from Java zero foundation to project combat oh [B station BV: BV1J5411c78D] ten enterprise-level project self-study course -B station: BV1Gp4y1b7SZ will be BV number, copy to B station can be
Need big factory Java interview full set of questions
Can pay attention to the public number: love programming FAFA
Key words: Study hard
Get complete interview questions