The most effective point for the society to recruit a big factory is probably the experience of another big factory. Manual dog head.

What if you don’t have big factory experience and want to step up to the challenge?

The front end, you can start from writing a resume. Take a look at what you have to write, and then learn and prepare in reverse.

There is no room for education and work experience, only professional skills and project experience that we can improve.

I have worked for two major companies, read hundreds of resumes and interviewed nearly 100 people over the years. Recently there are children shoes to ask me to help change resume, I found that still say not over, summed up.

First, professional skills write proficient, the interviewer is hard to resist

Have at least one or two writing proficiences in relatively narrow areas of expertise

We often use the terms knowledge, familiarity, proficiency and mastery to describe how much you have mastered a professional skill. If you are familiar with nearly ten of your major skills, this resume is a bit mediocre.

Especially in education experience and work experience and other aspects are not outstanding circumstances, here more to highlight the key!

1, basic knowledge of HTML and CSS can be proficient

Being a markup or rule-based language with no complex internal language logic can be achieved by spending a week or two reading through API documentation and books.

If you are proficient on your resume, the interviewer will not let you off the mark. It is important to put in the effort to prepare for the interview and to be able to answer the relevant questions fluently.

As we learn more, the more we know, the more we don’t know. This time do not be afraid, some cold knowledge can not answer it does not matter, to achieve the interview “proficient” is ok.

Say a own experience: WHEN I recruit in school, resume write: proficient in HTML and CSS, XXXX, after two years of work, I silently changed the proficient into familiar.

To sum up briefly, in addition to the common basic knowledge, make clear the following concepts, interview “proficient” is stable:

  • HTML tags, right-click to view the source code of several websites, including e-commerce, search engines, information and other types of websites, to understand the role of each tag
  • CSS box model, float, layout, various center alignment implementations
  • CSS3 animation, animation performance
  • H5 brings new features
  • Semantic, W3C standards, SEO
  • Accessible reading
  • CSS language extensions such as SASS and LESS
  • Engineering specification: ESLint, BEM, etc

2. Proficient in the scenarios used in the project

For example, the React framework used in the project is something you can try to master. If you write proficient, be prepared. If you use it proficiently in a project, it’s a long way from proficient.

React’s core function is to build the UI, and it’s possible to master it in a short period of reinforcement learning.

  • The framework itself can be studied in depth by reading the documentation and source code
  • JSX can’t run without Babel
  • There are state management Redux, routing router suite
  • Package the webpack used
  • React and React – Native

Redux-related flux, React-Redux, redux-thunk, redux-saga, etc. It took me about a week to understand them. Be careful to use them unless you are ready for them.

It is best to expand the “mastery” direction based on your own project experience. For example, if the project uses Vue more, choose Vue direction, so that there is some foundation for preparation, and the project experience can also provide evidence. It says on your resume that you have to reverse drive to learn, and this is also an advanced route.

3. Add some information about your business skills

I used to do business related to data visualization. Although the project was not that complicated, I still spent a lot of time to learn. The resume can be written as follows: Familiar with Web data visualization, skilled in using echarts, D3 and other tool libraries to achieve various data visualization scenes, skilled in drawing graphics and animation with Canvas, familiar with SVG and WebGL, and have a certain understanding of performance optimization in drawing graphics and animation.

This sentence can roughly convey that I am familiar with the business of data visualization, and I can try to achieve it by myself when THERE are customization requirements that cannot be met by open source libraries. I have a good understanding of the APIS provided by The Web, and have a certain foundation in graphics and mathematics. I will pay attention to the performance of visualization business. What’s more, everything mentioned in this article is related, which makes it more convincing.

Data visualization will involve the basics of mathematics and graphics, and then the use of Canvas and other WebAPI. There are also many open source tool libraries to use. If the project is useful, you can also spend some time to achieve “mastery”.

4. Don’t write at random

Do not write too much about your professional skills. After all, time is not allowed. If it does not match your years of work, it will not be true. You can’t write it arbitrarily.

For example: don’t write JavaScript proficiently, even if you are proficient in using it.

Unlike HTML, JavaScript is a programming language. It has many characteristics of its own, with advantages and disadvantages. We may need to learn one or two other programming languages to really explain that the strengths and weaknesses of one language often require comparisons with other languages that have some similarities.

That’s just the language itself, the platform V8 engine it runs on, and the features offered by browsers from various manufacturers. I know a guy who reads V8 engine source code, if you dare to write proficient JavaScript, you can be asked to tears.

Personal experience: I remember being asked this question in an interview, how is the array sort method implemented? What is its time complexity? I can only honestly answer that I have not understood, if in some scenarios need optimization, you can implement the corresponding sorting algorithm according to the need. Luckily my resume says I’m familiar with JavaScript…

Ii. Explore the overall value of project experience

The previous professional skills have reflected the technical characteristics of the individual. If there is proficiency or proficiency, it needs to be reflected synchronously in the project experience. When summarizing a project, focus on the project as a whole, not the individual!

If our work experience is only responsible for business development and assist the main process to complete some function implementation, it will only be mediocre in the resume. With the cattle blowing down in front, all kinds of proficiency, is also far from.

1. Summarize the project from the architect’s perspective

Programmers who don’t want to be architects are bad screws.

Summarize what you learned during the project, not just what you were responsible for:

  • The framework used in the project, such as React, must have a reason to choose it. For example, other businesses in the project synchronously use React-Native, use Taro framework synchronously to develop small programs, and use RN for mixed development of apps in the team. The most awkward stack is the stack used by all team members.
  • With WebPack, it’s even better to have custom developed Loaders or plug-ins if generic configurations don’t meet the needs of the project
  • Continuous integration is used to automate deployment and improve efficiency
  • The project configured code segmentation to optimize the loading speed of the first screen, and made various strategies to optimize performance
  • The project developed a self-developed framework to solve some of the problems

The above are just examples and can be summarized according to specific projects.

2. Summarize the project from the perspective of the main process

Sorted out, it seems that the front-end development of the difficulties are not so much.. Such as:

  • The business has infinite DOM loading, which solves the performance problem
  • Data visualization is also a difficulty
  • Development of rich text editor
  • Complex CSS3 animation processing

The main program is often responsible for solving difficult problems in a team, and often overlaps with the architect’s work. If there is a problem in the project that you didn’t develop yourself, just hand it in and it can be done, you can put it on your resume. You don’t have to force it on yourself, so does a team.

Summarize the project from the perspective of the project manager

After the completion of a product, how many users it has, what kind of achievements it has made, and which of these achievements are related to technology. Such as:

  • After front-end performance optimization, the page loading speed is faster, more registered users, and the conversion rate is improved
  • Perfect error prompt and extremely fast interactive response can improve user experience
  • Backward compatibility with older browsers can cater to a very small percentage of users
  • Fine responsive design, so that users of different sizes of equipment can have a perfect experience

It’s all about technology.

4, p.

Personal experience: My first job after graduation was in a large factory with a strong technical team and the core business of the company. However, what I did in the team was mainly business development, and I made rapid progress at first, and then gradually I was waiting for death… I don’t know how many people are like me…

Some of the technology the company was using is still cutting-edge today. The company had a self-developed framework, but it was stable before I joined and only needed occasional maintenance. There are also self-developed build tools, of course, was developed by the big guy before I entered the company. The UI component library is also available. Great server-side rendering, with chunked encoding for HTTP to optimize the first screen time to the hilt…

Although I have nothing to do with all this awesome stuff, I am a loyal practitioner of these techniques. Later, when JOB-hopping interview, I directly boasted about what technology was used in the project, and the interview success rate was 100%.

Finally, it is not easy to organize, if you feel helpful to yourself, remember to like the collection ~