From the technical director to hr, a “piece” | nuggets technical essay

Basic knowledge preparation

All skills are built on a solid foundation, and it is difficult for a skilled woman to make bricks without rice. For the preparation of front-end basic knowledge, in addition to the accumulation of usual development time, I still suggest a systematic brush interview questions.

Generally speaking, the basic knowledge involved in the front-end includes the following:

1. HTML/CSS related (HTML asks little, CSS asks more about layout and animation)
2. JS basics (closures, prototype chains, inheritance, event proxies, etc., are required)
3. Browser compatibility and front-end performance optimization
4. Front-end engineering (Webpack project packaging, Git project version management, etc.)
5. Vue, React, etc.
6. Framework underlying principle related (see the source code is certainly too late, you can brush the principle of the analysis of the blog and video)
7. Algorithms, data structures, design patterns, network principles (usually involved in large factories)

You don’t need to go to Baidu to find the relevant interview questions, I have a website that contains all the knowledge of the interview questions recommended to you. Very comprehensive, including all the front-end interview questions. Click on the front end

I have participated in many front-end interviews, and every time I have to spend time to prepare the basic knowledge, I feel very troublesome. So I wrote an interview treasure book of my own, and sorted according to the knowledge points. If you have time, I recommend you do the same

The basic knowledge is ready, the next skill formally began

Job analysis and resume preparation

I know that when looking for a job, people only look at years and salary, and then make a sea investment. That’s what I did at first, but then I realized that there’s a lot to be learned from the job requirements that companies post.

Next, I will analyze a recruitment information for you:

Like the recruitment of station B, we should not only focus on the front end of the resume, but also involve the back end. It’s important to note that if you have node development experience, you’re more likely to get an interview than any other candidate whose resume doesn’t cover the back end.

By analogy, if the company is an e-commerce website, you have done e-commerce related projects must be focused on description. If the job requirements involve specific skills, make sure you include them in your resume. Using this example from Site B, your resume should say “proficient or familiar with Canvas”.

So when looking for a job, we should prepare more than one resume, according to the different requirements of the job to deliver different resume, short for: what it likes.

Here’s how to write a resume:

I’ve interviewed a lot of people before, and I’ve seen resumes where I really don’t know what they’re trying to say, and it’s completely missing the point.

I think a resume should have at most three parts: personal information, skills description, and project experience. You don’t need to write about yourself or your interests. The interviewer isn’t really interested and it’s a waste of space. If you’re really good at looks, you can add a photo. If you know photography, hosting, editing and so on can write, but what love sports, travel need not write, everyone can. One of the weirder ones I’ve seen is writing “watching TV” under “hobbies”, which is penalized.

In terms of personal information, I still suggest truthful writing. Many people will cheat in terms of educational background, which I don’t agree with. If you have English cet-4 and CET-6, you can write in a conspicuous place, which is a plus. Major personal information such as name, contact information, residential address, and university should be included. If you graduated from a computer science major, you should also include your major. Personal information this one, it is necessary must write, others on the strengths and weaknesses.

In addition to the mainstream skills, the other skills will be added according to the previous job analysis. In short, it is ok to give HR a sense that I have the skills you need. Some people dare not write proficient, afraid of being made difficult by the interviewer, in fact, it is not so exaggerated, we just write it, do not be too modest and do not exaggerate too much.

Project experience is the most difficult to write, and it is the resume’s watershed

Personally, I think a good project description should be concise, not smelly and long like an old lady’s foot bindings. The project description should include the type of project, the problem solved, the revenue created, the technology involved, and the technical difficulties broken through. The description of personal center, login and registration should not be expanded. It has no value at all.

This year’s unripe do not have working experience, affirmation is to do not have project experience, but this still cannot be short of. You can write your own project if you don’t have one. There are so many online projects, just copy one and change it yourself.

Resume layout is also very important, programmer’s resume concise atmosphere is ok, do not get fancy. I would like to recommend a good online resume editing website, my own resume is also made on it. If some new people don’t know whether their resume is good or not, you can send it to me privately, and I can help you have a look at it first. Online resume editor, click on job resume

How to present your project

In the front end interview, the basics were pretty much the same, but it was the project that really pulled the distance. Many people in the interview, write on the resume of the project is not prepared in advance, when the interviewer asked, half a day do not understand. Give the interviewer the impression that you are not familiar with the project or don’t know much about it. So we must prepare in advance, mainly from the following aspects:

1. Introduce the entire project in a few words. Time for the interview is limited, so be brief and logical when introducing the project
2. The basic knowledge involved in the project must be fully mastered
3. The implementation details of technical difficulties of the project should also be studied clearly, and the more detailed the explanation, the better
4. The problems and solutions encountered in the project should also be prepared in advance
5. The last is the harvest in the project

Never be unprepared for a fight

General Question and answer preparation

General questions are questions that are likely to be asked in the interview, and we should prepare them in advance. I have prepared a few for you here

Why don’t you introduce yourself?

This I still suggest to prepare in advance first, the effect of the scene is generally not good. Technical personnel generally eloquence is not very good, otherwise will not do it. The main purpose is to introduce their personal information, working years, technology stack, etc. And it’s a great opportunity to bring the interviewer to your area of expertise

Why do you want to change your job?

There are three reasons for changing your job: lack of money, unhappiness in the company, and no room for advancement in the company. As long as everyone’s cause is positive and don’t trash the company, do what you want. Never say bad things about the company, even if it was really fucked up

What are your salary expectations?

Give yourself a range, don’t say too dead, different companies can adjust up and down. We’ll talk about salary in more detail

What are your plans for the future?

Not to mention space, there are two main aspects, one is short-term planning, and the other is long-term planning

Is there anything else you’d like to know?

Can understand oneself salary, pay, holiday to wait now, here do not carry, what want to understand although ask

What new skills have you learned recently?

This question mainly wants to test you usually love not to study, have certain sensitivity to new technology. You don’t have to have a deep understanding of it, but you can’t say no. If not, find out for yourself

What neighborhood do you go to?

The main idea is to get a sense of what you are learning through, not to mention the entertainment community, some front-end community, like nuggets, etc

Ability to communicate with technical officer

First of all, be sincere and friendly. No one wants his colleague or subordinate to be bad-tempered and thoughtful. It professionals in general are easier to get along with, not so much drama. The most important thing is to turn passivity into initiative and bring the interviewer to our area of expertise.

First of all, the content of your resume must be good at yourself, general interviewers are based on the resume to ask questions. Secondly, when introducing yourself, you must talk about your areas of expertise, but only half, and induce the interviewer to ask you. For example: when you introduce your own project, you say that the company pays more attention to SEO, so you have done server-side rendering, but do not say the specific implementation, such as the interviewer to ask you, this is called half leave half, if you directly all say it, will give people the feeling of showoff skills.

If the interviewer asks you questions that you don’t know, don’t pretend to know them. Won’t say oneself have not understood directly, also can let the interviewer hint a little below oneself privately to study well again, but want to hold good measure, don’t let the interviewer have you to test his feeling, in fact general as long as the attitude is modest and sincere good.

Last but not least. That is, to compliment the interviewer in a timely manner and to flatter him or her. Lily: You are really good. You learned a lot today. Be sincere and don’t exaggerate.

How to access the hidden information of the company

Get from chat:

If you mind working overtime, that company must work overtime a lot. If you don’t feel the interviewer is asking you a lot of depth, then the company doesn’t have a big head. All welfare hr will tell you, and what’s not said is not said, so don’t get any illusions.

Obtained from environmental observations:

If everyone is quietly sitting in their work station, generally formal large companies, overtime is relatively less, even if the amount of overtime is not large. If everyone is mixed together, meeting in various conference rooms, the desk is full of food, generally more overtime start-up. It depends on what kind of team you want to join.

Salary Negotiation Skills

There has always been a saying in it circles, “Starve the timid, support the bold”. If you dare to ask, the company will dare to give.

When writing your salary expectations, be sure that this is what you’ll be happy with in a year’s time. Because it’s hard to get raises in it companies these days, it’s important to expect more than you do now to avoid changing in a year’s time. It’s best to give a range that can be defended or attacked, but the span of the range should not be too wide, otherwise the HR will think you do not have a clear understanding of your ability.

General HR will pressure the salary, they will tell a variety of reasons, but you have to be firm, do not be they said at random loose mouth. The best way to do this is to say that you have received an offer from the company and that you just like your company. The hr will definitely ask you about their salary, so you can add +1K to your expected salary.

❤️ follow + like + favorites + comments + forward ❤️, original is not easy, encourage the author to create better articles

Pay attention to the public front terminal, share exclusive learning routes + boutique courses, more front end small dry goods waiting for you