Are my own ideas, the main arrangement of their own is how to interview others

Attitude and attitude are very important. It is a comprehensive consideration of many aspects. Not only hard skills (technical ability) are very important, but soft skills (thinking, mentality and communication ability) are also very important.

mindset

Have a positive attitude and can do three things

Answer questions confidently, say if you’re wrong, and don’t deflect questions by changing the subject. If you don’t understand, ask questions back.

Development needs to be divergent, you can give three, that you are willing to think, a lot of things, think more can be done, and now the Development of the Internet, find problems and communication is very convenient, so attitude and mentality is very important

In many cases, attitude determines a person’s height, but also determines whether a person is willing to take on difficult tasks

The extent of one’s knowledge

See is attitude, you may understand is one-sided, but since you can understand that these, said you often pay attention to these, important is not the breadth and depth of knowledge, but if they want to take the initiative to learn, technology update quickly, you don’t want to take the initiative to understand, the last may be eliminated easily.

And sometimes when something goes wrong on a project, you might learn something that can help you a lot.

A sense of identity and professionalism for work

Reading source code, participating in open source projects, in-depth understanding of the theory behind the technology, or breaking through the limitations of language and grammar, js grammar is also borrowed from other languages, these can be used to express a strong identity and professional affiliation to their own jobs.

Willingness to learn and share actively

This is important both individually and as a team, but it is important to note that sharing is not mandatory and should not be shared for the sake of sharing.

Sharing is voluntary and initiated with a clear purpose, a specific topic and a short time.

Questions content

Will ask questions according to the interviewer’s working years and resume, summed up is 1 ~ 2 years to ask the foundation and framework (use direction), 3 ~ 4 years to ask thinking and engineering, 5 ~ 6 years to ask the structure (front-end UI hierarchical management and the overall technical structure of the role of the front end positioning) and management questions

Scope of the problem

  1. Grammar foundation
  2. Frame used
  3. A list of skills to write in your resume

pluses

  1. Programming thinking
  2. Design patterns
  3. The driven
    1. Self learning
    2. Read the source code
    3. Participate in open source projects
  4. Whether they have their own subjective consciousness, such as:
    1. Stand in the user’s point of view to consider whether their functions meet their needs and so on
    2. Think from the product manager’s point of view whether the process can be optimized and so on
    3. Think at the back end, is the data secure and so on
    4. Think in terms of UI, interface, interaction, motion, etc
    5. Standing in their own professional point of view, whether the code is reasonable, the middle of the logic processing whether there is a better way to write
    6. From a testing point of view, whether the function is defective, whether exceptions are covered, etc

1 ~ 2 years of front-end development

Novice development, solid foundation on the line

1. The CSS

  1. The box model
  2. CSS layout: Position, float, Flex
  3. Have done mobile terminal will ask the adaptation
  4. Css3 animation will be added (bonus points if not strong)
  5. Browser compatibility (not strong requirements will be extra points) and so on

2. Js

  1. Basic grammar
  2. Common ES5 apis, such as array.map and array.forEach
  3. Es6 promise, etc

3. Framework foundation (such as VUE, understand other frameworks, CV writing also ask)

  1. What is two-way data binding
  2. What is one-way data flow
  3. Vue’s common component options have those
  4. How do you design your components (surface thinking)
  5. What do you understand about VUE

4. Learning

This stage someone with the growth of the future is really too important, easy to master the difficult entry, but if the old master with the entry, you can take many detours, and growth has a goal, will not feel confused.

  1. Learning channels
  2. Time spent studying each day
  3. Personal growth and planning

Five other

More random in front of the good answer to ask, mainly programming thinking.

3-4 years of front-end development

The company’s main development, most of the business is done by these people

1. Some programming skills

Deep copy and shallow copy, asynchronous programming (not asynchronous API, many people equate this with…) , etc.

2. The core content of the framework, and possibly others

Such as the framework of the design mode, principle and other aspects, the main attitude, say wrong is ok, the surface is you for things whether have a kind of attitude to the end, 3 years can have their own ideas, ask this is mainly to see you are not in the accumulation of experience, this time should think so in-depth.

3. Code management

Work habits and code management, at least to ensure the cooperation of multiple people, such as pull code at work every day, submit code after work, know Git flow, and can solve conflicts

4. Is there any server-side programming

Front and back end task disassembly, there will be no communication barriers, front and back end separated projects, the database does not care, but the UI front end is the dominant.

5. Directory organization and project construction and deployment

To grow up is to be independently responsible for a project. If you don’t accumulate now, the pressure will be great later.

5 + years of front-end development

At this point, you can already decide whether you want to be a technical expert or a technical manager in the future. In small companies, this person is already a small head of the front end

Big companies may not be there yet, but in small companies, 5 years is more than just development and a lot of time to participate in business discussions.

Team recruitment needs to pay attention to the situation

These are all personal opinions. If the person is better, you can say something else

1. The project does not have more than 3 years of development, and no new recruits are recruited

There are more than 3 years of back-end development is also ok, mainly let the new person in charge of their own basic impossible, and even hit his confidence.

2. Never recruit new staff for urgent projects and heavy tasks

The project urgent team recruits, no time to bring people, and the result is similar to no recruitment, and even will distract the energy of the main development.

3. With many tasks and slow time, try to find fresh graduates

  1. People who have worked are easy to leave
  2. Just graduated in the middle of hard training, new growth fast

The last part is the plan I gave myself when I just started working

I recommend learning okR and setting goals for yourself, which will help you grow faster.

To recap, the following phases can be performed simultaneously

Stage 1: Lay the foundation

What is the foundation, for students, the textbook is the foundation, for development, API document is the textbook, a good document can bring people’s growth is huge, such as vUE document, for beginners, really very good, where the knowledge for learning other frameworks is also very helpful.

plan

  1. Finish reading the javascript documentation
  2. Read the CSS documentation
  3. Finish reading the HTML document

Terms of inspection

  1. Regular apis can be used
  2. An impression of an uncommon API

Stage 2: Learning framework

plan

  1. Know what routing is
  2. Know what a component is
  3. What is the life cycle
  4. , etc.

Terms of inspection

With a

Stage 3: Engineering

plan

  1. Understand catalog design
  2. Understanding tool usage
  3. Understand compiled deployment

Terms of inspection

With a

Stage 4: Learn programming thinking

plan

  1. Understand advanced apis
  2. Understand functional and responsive programming patterns
  3. Understand design patterns

Terms of inspection

With a

Stage 5: Learn a back-end language

plan

  1. Understand back-end routing
  2. Understand back-end request processing
  3. Understand the back-end organization
  4. Understand database design
  5. Understanding rendering and so on

Terms of inspection

With a

This article is formatted using MDNICE

– END –