You are my south wall, is my empty joy a fool’s paradise.





This article has been uploaded to my GitHub warehouse, welcome Star:
github.com/YellowTuDo

preface

The tiger word

How do you foster trust and get the interviewer to let down their guard and listen to you?

This paper mainly from the following latitude to break through: psychological analysis, the interviewer pain point, how to prepare for the interview explained one by one

Interview motto: there is no technology, only did not memorize the interview questions. (Daniel doesn’t need to prepare for the interview.

STAR interview method

Law of the interview

STAR: complete by description
Project background.
The target.
actionand
The results ofthe
Complete the pastExperience to record the candidate’s past
Project resultsand
thinkingAnd the process
Talent qualities.

Now do you know what the interviewer is asking you about? You know the interviewer has a formula, right?

Since we like to ask about projects, let’s first think about what kind of projects are so high that people think of them as cow cup? Of course: distributed, microservice, high concurrency, high availability.

Some people will say, this I also have no contact with ah, haven’t eaten pork, haven’t seen the pig run? No contact, go to contact, see the principle, can say you don’t make it? The person also is not to be born to be able these, 9 years compulsory education you still did not learn “face should try to learn”, I should say some of what good. Learn what the interviewer wants to hear, and be proficient at it.

Write on your resume, be sure to be able to, don’t write of zha zha bluff, ask to drop the chain, “for resume review interview”. Dig deep into three or more of the points on your resume and ask questions to prevent the interviewer from firing away at them. (Prepare in depth)

The advantage of the second set is that you can respond quickly to the question and make an answer.

Only if the project is not good, people want to ask you the foundation, to see if you have a solid foundation (interviewer psychology: if solid can also be used), the project is good, the interview is like a chat. Of course, the interview itself is a process of chatting and getting to know each other. It is very important to maintain a harmonious atmosphere.

The mode of person-to-person collaboration comes first, then comes technology.

Interviewer pain points

Pain points

In fact, the interviewer’s pain point is only a few, but it is the interviewer needs to run through the whole interview, all the time to send out the temperament, to convince the interviewer, and capture your shining point is not easy.

1. Excellent education background, big factory background, open source project.

2. You are skilled enough to have a macro vision, open mind, and pay close attention to the trends of the whole industry.

3. You have good communication skills, language organization skills and affinity.

4. You are passionate about technology, aware of the latest technology, and disciplined.

Guiding the interviewer

Avoid stepping on the pit

Interview management self-cultivation: prevent the interviewee from controlling the pace, accurate intention.

Know how to say the project, just started, if you can’t control the pace of the interview, master the absolute power of the interview, then easy to be bombarded by the interviewer, or affect the confidence of the interview.

The scene of a

HashMap

You have to at least think of key-value, array + list, expansion mechanism, Poisson distribution, thread insecurity, head plug, tail plug, etc.; When asked about security issues, you can quickly navigate to concurrentHashMap. (Instead of waiting for the interviewer to ask you a series of questions, volunteer and tell everything you know.)

Interviewer psychology: Asking you if HashMap threads are safe is to look at your thought process and see if you’ve used multiple threads before.

So you have to prepare the hashmap and you have to prepare the lock optimization and send the package and all that stuff. Of course, this will expand into more detail, and you will need to lead the interviewer to a place you are familiar with. (The direction you are leading is something that you can clearly understand and support.)

Excellent interviewers, questions are always coherent, the front of the question will always be foreshadowed for the back, to think more, the underlying problems behind the question. Put yourself in the interviewer’s shoes and think about what you would ask if you were the interviewer.

The interview will only take so long. The interviewer has no grudge against you. He or she wants to recruit, not make things difficult for you.

The interviewer’s skills are usually much higher than yours, so it’s impossible for you to know everything. When you meet someone who really doesn’t know anything, simply point out that the two words “don’t” will accompany a smile. You will not improve the interviewer’s good opinion of you, but also think that your integrity is questionable, and “no”, maybe you just forgot.

The essence of leading is that you have to be able to look at a technical point, what the next question is going to be, and then lead on to what you’re familiar with. Of course, if you’re still preparing for an interview, it’s best to know everything. (This is true regardless of the depth of the question.)

The interview last

Is there anything else you’d like to ask?

Do:

Technical stack and the organizational structure of the business company, personnel situation. You can even ask about learning methods. .Copy the code

Don’t:

Interview results Salary package Personal...Copy the code

Why the low offer rate

1. Limited to normal development skills of adding, deleting, modifying, and checking, lacking technical depth
carefullyTo prepare.

2.Java technology is not systematic, which makes it difficult to prepare for the technology breadth topic.

3. I don’t know how to package my strengths in my resume, and I don’t pay attention to details in the on-site interview.

4. The resume has no priority, title, personal introduction, and project experience.

Will your resume catch hr’s eye in 10 seconds? 1 minute Does the interviewer see your strengths?

conclusion

1.
For recruitmentWriting a resume,
To resumePrepare for the interview.

2. Be humble, speak up, and show your skills like a tree.

3. Guide the interviewer to ask you questions properly, and control the pace, even if you can’t, don’t force it, and don’t cheat.

4. Keep learning, love Java, keep recharging, and be in awe of technology.

5. The interview can be prepared and packaged (respect for the interviewer), but don’t shoot from the hip.

Share with you

Your manager is not your boss because he should be more forward-looking than you. He is your boss because he sees things higher, thinks farther, and works deeper than you.

The reasons for failure are many and varied, and the success stories are all the same. Successful people are successful in three aspects: identifying problems, defining problems, and solving problems.

To contact me

YellowTuDo | article [original] [reproduced please contact himself] if there are any errors in this blog, please give criticisms, be obliged!


Like a person to say like, grateful to say thank you; Saying something negative won’t get their attention, it will just push them further away.


This article has been uploaded to my GitHub repository. Welcome to Star ➡️ :
github.com/YellowTuDo