Why is there (2)

I did not think of the last article “three years in front, thinking about the interview” there are so many front-end students to see. There were also a lot of encouraging and questioning voices in the comments section, and the number of students communicating in the group reached 700 in two days.

Some students in the group asked a lot of questions and wanted me to share some interview skills, which I have also sorted out in this article.

How much memory does a 100*100 canvas take up?

Feedback and solutions

Here’s a look at the nuggets’ comments 😀

• More than three years of experience in the undergraduate course itself is difficult to get P7, right?

P6, p7 is a hurdle. I understand p7- technical experts, in some areas need to have a certain amount of precipitation or strong comprehensive ability, with the ability to push things to the ground.

Among the friends I have met, some have worked for P7 for three years and some have worked for P7 for 10 years. Among them, my friends who can get to P7 in three years have profound attainments in React Native and published famous technical books.

As for THE P6, it can do the core work on its own. Normally, the lead developers on a team should be at this level, and there are many of my friends who have been working for P6 for only a year.

So the position of this matter, their own positioning should be clear, do not arrogant, do not belittle themselves.

If you want professional answers to the rating criteria, you can consult the headhunter in the group (Headhunter Xiao Yu) ~

• React and Vue know little about React and Vue.

It doesn’t mean THAT I don’t really know React Vue, but the interview is a process to discover the highlights of the interviewer. I really don’t understand why I should expose my obvious weaknesses. Usually, I will tell the interviewer that I don’t know much about style and React Vue. So I can spend my time doing what I’m good at. Ng1 can play very slip is not also a kind of learning ability to reflect it?

Here’s a quote from a friend:

1. Willing to get involved in the product; 2. Responsible for complicated front-end projects alone; 3. His previous entrepreneurial experience has improved his ability of communication and business understanding. This is the core competence, at this salary level, the position of technical level is not important, product ability, leadership ability, presentation ability, understanding ability, any one is more important than technical ability

If you want professional answers about the rating criteria, you can consult the headhunters in the group

• The experience is very similar to that of the big guy. They should have graduated in 15 years and worked for three and a half years, 211, but they are much worse than the big guy.

Comparing yourself to others is one of the least meaningful things you can do. Just try to be better than you were before

• Is the front-end base this high? Crying backstage in the bathroom

Other positions do not have to think so, salary is always a value exchange, can bring what kind of value for the company can be what kind of salary.

• Question the salary and be unkind

At the beginning, the rough range of offer was exposed, which caused a lot of doubts. It was quickly removed to avoid unnecessary embarrassment.

I can quite understand the salary comparison, because the same working years, for example, 1 year, have a friend 10W +, another example, 985 bachelor’s degree, front-end, work for one year, change jobs, from 30W + to 50W +. Again, salary is always an exchange of value.

For example, of course, mean is not little, earn more tremendous (pay will always be better-off ratio descend enough to spare), example is said to gossiping about other people’s salary is not necessary, if you will have a very high salary friends, should go to ask them is how to interview, how to prepare, how does that work, how to learn. State of mind to straighten out.

And there is a lot of overlap between the salary level, it is likely that P6 is higher than P7, this should be a common sense salary design. (And there’s that dreaded word: pay inversion.)

The salary level reflects not only the technical skills of technicians, but also many soft qualities.

A collection of problems in an ac group

• What if there is no big project in the front-end interview?

Project experience problems.

• The interviewer said that the foundation is poor. I don’t know how to fix the foundation.

Basic knowledge problem.

• Self-study front, how to talk about the project in the first interview ah

Project experience problems.

• Now encountered a bottleneck, is all kinds of basic knowledge, scattered knowledge feel almost understand, but can not be combined to think. An interview question, may open the inside of the knowledge point all know, but can not be connected as a whole. Any suggestions?

Knowledge melts into knowledge.

• Hello group owner. I have worked for 3 years, with a general undergraduate degree. However, I have only one and a half years of front-end experience (three years, as announced). It was always a small company. Therefore, job-hopping is relatively frequent and the foundation is relatively weak. Now I’m filling in some foundations. But it still feels like a bottleneck. Want to go to a big company, may not meet the requirements. Small firms feel less comfortable with technology growth and are prone to wage bottlenecks. I have always wanted to try to work in a medium or large company, but I am still confused. How do I choose between small and medium-sized companies in my phase and how do I approach them?

Basic knowledge problem + knowledge penetration.

• I want to know how the group leader usually front-end system, as well as the surrounding technology stack, which piece of ability the interviewer values more, which ability the interview should have.

Knowledge flows together.

The above problems can be roughly divided into

• How to consolidate the basic knowledge
• How do technologies fit together
• How to enrich the project experience

First of all, the importance of basic knowledge cannot be stressed too much. For example, if the basic properties of functions are not understood properly in high school, the study of mathematics will torture the whole high school career. Physical stress analysis is not good, basically you can say goodbye to physics.

For basic knowledge: read more, coding more, summarize more, nothing else.

How to read

What kind of book? What are some must-read books for front-end development engineers?

I personally recommend JavaScript Advanced Programming, You-Dont-Know-JS series, JavaScript Ninja Secrets.

Many students say that the foundation is not strong how to do, in fact, we already know the answer in our hearts – make up the foundation.

In the first six months of my work, I read JavaScript Advanced Programming for about three times. At the beginning, I did not understand closures, prototype chains, etc., but these are basic knowledge, so I had to force myself to read them. At that time, I just came into contact with AngularJS due to my work. Everyone knows that AngularJS has a steep learning curve. It is very difficult to understand the ways of service and how to write directive. I can only read books outside of work. I remember reading the Definitive AngularJS Tutorial and AngularJS In-depth Analysis and Best Practices many times.

Make a list of books THAT I have read. Books that I have read (though some are non-technical)

Here I also recommend a good friend – Old Yao, you can read his front-end learning experience, he is also in the front-end interview group, you can also ask questions to him.

“Front-end network Lao Yao talk: how to learn JavaScript?”

Yao: Front-end Books I read in Those Years

Through the above example is to show that laying a solid foundation is not a simple word, just like old Yao, read more than 100 front-end books, this point I also feel inferior.

In a word, is based on business development tools, we are in the process of business development in solving a problem, one by one specific basic knowledge don’t pass this time, for a concept is not clear, such as closure in understanding business level issues to deal with such details when technical problems will lead to longer development cycle, thinking on different levels, It’s gonna be a mess.

Sharpening the knife does not mistakenly cut wood workers, read more books, more coding!

Summarize and share more

There are many ways to summarize and share, such as writing a blog, sharing technology in my own team, etc. Here I share a former colleague’s blog, he only worked for one and a half years, now he is in the headlines, you can see his usual writing level. 10081677 wc/blog. This student is also in the interview group 😀

This is Lao Yao’s blog

Old Yao wrote regular expression tutorial regular expression series summary

Through the above examples, we can find that these students with solid basic knowledge are also engaged in in-depth study of concept by concept, and only slowly can they produce output. And in the output process is also a learning, the same will consolidate their basic knowledge.

I remember that I organized a front-end technology sharing meeting in the company, sharing some technical problems and solutions encountered in work every week.

In the normal development process, we will certainly encounter a lot of technical problems, when looking for and discussing solutions with a lot of thinking, we should record the process of solving problems, these are very good materials for technology sharing.

If it’s a general question, write down a small theme to share. This is a post I made at my company about how to use gulp. Learn Gulp with me

In this way, it can not only ensure the normal business, but also in-depth understanding of specific problems, but also share with peers, increase the influence in the team, if you can also write articles, published on Github, Nuggets, etc., can also improve the popularity in the industry ~ why not?

Moreover, it is very important that once we decide to share technology, our mentality will also change, and we will concentrate on the face of it, from data collection and screening, demo creation, simulation and real sharing, asking questions and explaining them by ourselves, team discussion, and finally published in a paper, discussing with readers and modifying them.

A set of procedures, in the long run, all aspects of the ability will be significantly improved: including data collection, screening ability, ability to organize written, speech ability, explanation ability, community visibility and so on, in short, a lot of benefits!

Mastery of knowledge and skills + project experience

For the integration of knowledge and skills and the accumulation of project experience, many students will say that a lot of front-end “advanced” knowledge is actually not needed, many of their concepts are just understanding, always do not know how to use, they do not have complex projects to show.

Is that really the case?

To take a simple example, we often use the to-do-list project to practice when learning the Vue and React frameworks.

So let’s think about this project beyond just understanding the basics of the framework, what else can we think about?

• Why is the project directory structure the way it is, and what does each part mean?
• How is the business code organized? Is this organization ok when the business is complex?
• How is engineering done?
• What is the build process like? What do you know about the build tools?
• What is the process of going online?
• What is the difference between local development and deployment?
• What is the git usage specification? How to do branch management well?
• How to work well as a team?
• How are the front and back ends divided? How was it coordinated? How do I do that across domains?
• How do product features come about? What was your role in it?
• What is your r&d process?
• If you add a search box, how do you solve the problem of rapid typing leading to frequent Ajax requests?
• What are the technical difficulties of this project?
• What are the implementation schemes of animation? What are the options for animation optimization?
• What are the performance optimizations?
• What if users type in unsafe content? What are the common security problems?
• A client in Shanghai said that his H5 page could not be opened. How do you solve the problem?

Of course, this article will definitely not solve these problems. What I want to say is that although a sparrow has all the five organs, there are many problems in the development of each product, including business, product, team and technology. For each problem, our R&D personnel can participate in the improvement. In the face of these specific problems, if you are afraid of actively participating in the project, can you not master your knowledge and skills and enrich your project experience?

One of my former colleagues once came to me for guidance when he was quitting and looking for a job. After several rounds of interviews, he said to me: “I wish I had taken the initiative to participate in those tasks, so that I can look back and see that I did not do particularly complicated functions. Unlike you, who were competing for work, I did not understand at the beginning, but now I realize that project experience and my ability are accumulated bit by bit like this.”

For those of us with 1-3 years of work experience, how do we stand out from our peers? Only practical basic skills, plus rich actual combat experience. If you are an interviewer, you will not only have a good grasp of basic knowledge, do not fool around with business, take the initiative to challenge complex business, but also give technical explanations to team members. Everyone will think of you when they encounter problems. Who would not like such a colleague?

Other problems

“How can I get hired if I want to change jobs after two months? I always feel fired after two months.”

“I’d like to hear about your schedule for self-improvement after you joined the company. How do you deal with it in your daily work, so that you can improve yourself as soon as possible.”

“How do you reconcile the constant overtime and urgent projects with your self-learning plan?”

These can be divided into

• Self management
• To apply for a job interview
• Soft skills etc.

More content, we will talk next time!

hiring

Ant Financial – micro loan business group recruitment front can send a resume to [email protected] email title: resume – name – front attach your resume

One-on-one tutoring

Topics include career planning, resume modification, mock interview, interview skills, job content, etc. Welcome to meet me ~ www.zaih.com/falcon/ment…