How can programmers quickly find a suitable job in this year's market?

Several previous articles were written about the interview experience, which took everyone to understand some of the current market conditions, as well as the different perspectives of the recruiter and the job seeker during the interview process.

Today’s article writes some suggestions that may be more useful for job interviews:

First, the balance between value and quantity

In the early years, most of the interview routines were: memorizing interview questions, memorizing stereotyped essays, brushing algorithms, and entering a big factory. Because the market is relatively tight, and big factories are recruiting people in a large area, this routine is very popular, and it can be prepared in one go, and basically can be used in all interviews. Because all big factories are recruiting people, they basically ask similar questions, so after preparing the questions, you can conduct a large number of interviews.

However, the current market conditions are changing imperceptibly. Large factories are constantly sending "talents" to the market, while small and medium-sized factories are here to undertake these talents. SME recruitment focuses more on practicality and versatility. If you don't have some abilities for the time being, then you have to look at your learning ability. Moreover, the interviews of small and medium-sized enterprises are multifaceted. Therefore, the underlying logic of recruitment interviews has undergone some changes.

At this time, if you still memorize the interview questions at one time, and then face three or four times a day, the effect may not be very good, and a lot of opportunities will be wasted. The correct strategy should be to spend three or four days carefully preparing an interview and dealing with an interviewer.

It is not unimportant to prepare for the questions, and the frequency of interviews is not unimportant, but to shift the focus from focusing on the probability of spreading the net to the quality of each interview.

Second, don't use one resume for all companies

This one follows the previous one, not only now, but also in the past and in the future, if you can dig out your matching points according to the needs of the recruiting company and prepare your resume. Then, you will have a huge advantage whether it is in the resume screening or interview process.

For example, an e-commerce company is recruiting, and in your past experience, you can only match it with the fact that you have received three-party payment. At this time, your resume should highlight the point that you have done three-party payment, because this point is the reason for others to choose you. At the same time, before the interview, you have to thoroughly understand the logic of the three-party payment that you have done before, and even learn more about it.

Doing this is hard for most, but worth it.

Third, rehearse and predict in advance

This one follows the previous one. Take an e-commerce company as an example. It wants to recruit people with e-commerce and payment experience, and your resume also reflects this. Then, there is a high probability that they will talk to you about this aspect during the interview.

What you need to do is, before the interview, conduct a rehearsal and try to answer these questions orally. When you can explain these processes yourself, you really understand. Oral dictation is essentially a learning process (Feynman learning method).

Even if the interviewer doesn't take the initiative to talk to you about these questions, sometimes he will ask: Tell me about the highlight functions you have done in your past experience, or talk about the functions you think are technically difficult or business complex. At this point, your preparation will come in handy. Don't ask what bright things you have done, and you answer that there are no bright spots, just some management systems and functions.

Of course, the rehearsal and prediction is not only about the technical level, but also what you have done, the achievements worth "showing off", and some thoughts on software, work (career planning), workplace, etc. In short, prepare some reasons in advance that can make the other party choose you.

Fourth, gain a deep understanding of the company

Most people are, there is an interview invitation, so go. In fact, before going, there is another very important preparation: getting to know the company. Through the Internet, learn as much as possible about the company's situation, such as business areas, recruitment needs, interviewer conditions, salary conditions, etc. This is also a very important aspect of interview preparation. Only by knowing yourself and the enemy can you be able to do a job with ease.

Fifth, reasonable salary expectations

Different industries, different companies, different positions, and different market conditions have different salaries. Do your research and estimate reasonable salary expectations. If your expectations are too high, higher than the upper limit that the company can provide, even if the interview is successful, it is likely that because of such a high expectation, the other party is too lazy to bargain and lose the opportunity. Even when within reach, too much haggling is not a good strategy.

Sixth, push in

Although this article is written at the end, I personally think this is the best choice. If you really need to find a job, then put down your face, ask your friends to help, see where there are suitable opportunities, and take the route of referral. With the endorsement of this level of connections, if you are not very capable, you can easily surpass many competitors, which is equivalent to taking a shortcut. At the same time, you can get a more comprehensive understanding of future positions. But preparation is also necessary. You can’t perform too poorly to embarrass the recommender.

Of course, internal referrals also need to be prepared in the early stage, such as whether you have done great things (wrote open source, completed large projects, etc.), whether your workplace quality is OK, whether you are excellent, whether you are willing to endure hardship, whether you are popular, etc. It all has a lot to do with it.

After all, most people are not willing to risk their credit unless they are very good, professional or well-connected. This also requires long-term accumulation in being a person and doing things. But it's certainly a direction worth striving for.

at last

As Golden September and Silver October are approaching, many backstage partners told me that they are preparing for interviews recently and urgently need some high-quality materials. So in order to better help fans who are interviewing recently, today I bring you a copy, Ali Java Interview Quick Guide 2023 Edition (as shown below):

Alibaba Java Interview Quick Guide (2023 Edition)

This interview guide has fully infiltrated 23 technology stacks from basic to advanced, and the length has reached nearly 300 pages. The editor also compiled a Java resume template of an excellent colleague and my friend's interview with Ali. Hope It can be helpful to everyone. Due to space limitations, I will only show the key parts of the information below. Friends who need the full version can check it at the end of the article.

  • There are not many bbs, let’s first look at the main content of the interview guide:

JVM articles:

Java thread articles:

Framework articles:

  • Spring

  • MyBatis

Database articles:

  • mysql

  • Redis

MQ articles:

Microservice articles:

  • SpringCloud

  • Dubbo

Zookeeper:

Distributed articles:

Network articles

Design Patterns:

The space is limited. The hard skills of the Java interview only show these parts of the technology stack. Let's take a look at the soft skills of the interview:

interview soft skills

Template reference:

Ali Sutra:

at last

The length of the article is already very long here, so I won’t continue to lengthen the length to affect everyone’s reading experience. You need the Ali Java interview crash guide + Java resume template + Ali’s seven-faced face-to-face experience shown above. Click the small card below . ~

Guess you like

Origin blog.csdn.net/Javatutouhouduan/article/details/132025270