Introduce myself first, oneself 3 years change profession procedure yuan one, this year April end naked resign. I went on a trip in May and came back to look for a job for two weeks. I interviewed eight places and passed four. It is already on board.

In this month’s time, I have some thoughts on front-end learning, naked resignation and interview, and I hope to share them with friends who are in the same dilemma and doubt.

About the interview

Let’s talk about the interview first.

Interview questions will not share, nuggets there are many excellent interview questions summary article, at the end of the article I will read and feel useful links posted, brush interview questions, let us pass a large probability is no problem.

Since I am a front-end engineer, and my previous learning and working experience has nothing to do with IT, I feel that MY knowledge structure and basic skills are very inadequate, such as data structure, algorithm, design mode and network related skills need to be well prepared before the interview. You can express your weakness in these areas during an interview, but it’s best not to be completely ignorant of them.

How to pass the second, or even the third, in my opinion, is to review your resume over and over again. All the technical points and keywords mentioned above, whether you know how to use them, whether you understand the principles and related knowledge points, whether there is real project experience support, this is very important.

So, our resume needs to have enough shine to pass an employer’s initial screening, but not enough to leave us stumped during the interview. – I encountered a strict interview, asking the resume line by line, and drawing the skills on the resume if the answers weren’t good or bad.

Review the basics + look at the interview questions + prepare the resume technical points/project experience, I think is more effective and general preparation for the interview plan. But in the interview, often the interviewer will put forward some and our own skills are not consistent with the requirements, this time should not adjust our review direction?

For example, I encountered these questions in eight interviews:

Do you have a well-known open source project on Github?

Do you blog regularly?

Did you write a little book on the Nuggets? (even though the man even b

Do you have your own library of open source UI components?

Do you have any hobbies that you do really well?

… .

My answer to all of these is: no! Rarely blogging and rarely submitting to Github, I felt like a loser the moment I was asked these questions.

After the interview I was torn about whether to prepare for it or not, whether to write a blog every day. Submit to Github? Should you write your own UI component library and then go out and get a job?

Reason tells me that it is pointless to do these things deliberately. These are the things THAT I can’t adjust or prepare for during the interview, and it’s a pity if the company has such a demand.

Of course, these are the areas that need to be made up for in the next stage of study and work, and it is too late to prepare for these during job hunting and interview.

At another company, the job requirement reads: Be familiar with the VUE or React technology stack. I have experience in both VUE and React projects on my resume, and I am more familiar with VUE. Redux has not used it, nor has it been mentioned on my resume. However, in the actual interview, the second-round interviewers kept asking react+ Redux questions, because their company used react technology stack, and the final evaluation of me was that I did not have enough experience in react project.

Maybe the company is short of people and needs someone who is a good fit on the technology stack and can get started right away. In my opinion, I am not a good match for this position. Skill points can be prepared in advance, but the project experience is real, and it is important to prepare for the interview based on your actual project experience. Of course, their job requirements don’t match the actual interview situation.

So, if you encounter an interview that doesn’t match your skills, think of it as a learning experience and don’t have to doubt yourself or feel bad. You can always find the right company for you.

So much for the interview, a summary:

  • In preparation for the interview, focus on the basics and your resume
  • Don’t reorient your study for interview questions that you can’t prepare in a short time
  • Stay positive and don’t let an interview fail you because it doesn’t have to be your problem

About the naked resignation

Nuggets have always been said: naked resignation for a while cool, always naked resignation straight.

In my experience of quitting naked for a month, that’s not the case. Quitting naked is more tiring and stressful than going to work. I’m reading books, looking at codes, and looking at notes I’ve made from 7 a.m. to 12 p.m.

Since I have almost no interview experience before, the last company was the first and only front-end job I interviewed before, and I interviewed eight companies this time, which is not easy… .

Here’s what happened when I quit naked:

Week 1: Go traveling, happy… .

Week 2: My roommate went to work early in the morning, but I didn’t have to. Finally, no one would @ me all the time in the nail group. Finally, I could relax and read the written code. .

Week 3: Why do you forget what you Read the next day? Why cast a pile of resume nobody reason! Why!!

Week 4: Going out for interviews is so tiring! It’s so hot outside! What was that interviewer asking?! Why don’t you ask the questions you prepared! What a grievance! Why hasn’t the offer from your favorite company come yet? I am not abandoned by this world!!

During the period of naked resignation, I was caught in the double attack of feeling abandoned and self-doubt.

About naked resignation, here is the conclusion: can not naked resignation, do not!

Tell me more about why I quit naked.

One is the lack of front-end interview experience. Later, I heard from a big man that it takes one to two months to prepare for the interview if you want to get a good offer. At the beginning, I really thought it would be just one or two interviews as before, but now the market requirements for the front end are greatly different from three years ago.

Second, there is no extra time to prepare for the interview. My last company was really busy, 9 am to 9 or 10 PM every day, urgent projects on weekends, endless business code. What is more frightening is that the front end leader is sitting next to me. He spends a lot of time on technology research and hardly participates in business development every day. However, whenever he finds that I am not typing code, he will ask me what I am doing and arrange new projects for me.

I was capricious and decided to quit. Now that I think about it, I find it very inappropriate. First, if I quit my job without knowing whether my ability matches the market demand, I may be unemployed for a month or even longer. Second, I have some opinions on the leader’s practice and work arrangement. I should try to communicate with him first or give feedback to the technical manager/project manager at the next higher level, rather than sacrifice my job opportunity.

Finally, I would like to say that my technical progress and growth may be affected by too much work and too many bad things at work, which is a problem I may encounter in every company. Next, I should learn how to overcome it, rather than escape it.

Since the choice to do this line, is the choice of endless learning, come on.

Recommended interview questions

The following links cover almost all the basic interview questions I have encountered. The rest are mainly related to project experience, interested partners can chat privately.

The nuggets pamphlets

Some of the nuggets are really high quality and the author has written them with great care. I recommend the following.

Yck’s approach to front-end interviews

React Combat: Design patterns and best practices

Introduces the principle and practice of front-end performance optimization

Aresn Vue.js component details

Qi Mo students analyze vue. js internal operation mechanism

Denver post

The following four articles are very useful in summary, thanks for the author’s selfless sharing!

SnowLu – Job hunting in winter

What you Need to Know about the Job Search season

Hi, do you really understand this?

What you Need to Know about the Job Search Season

blog

Nguyen half-stretching