preface
Most of us go through life looking for jobs, going through interviews, being reviewed by interviewers and being screened by companies. Especially for programmers in the IT industry, switching companies is a familiar thing. Then the problem comes, how to efficiently find a good position, a good team, a good company?
The body of the
With that in mind, I turned to Dendi, who recently got to know him from the Nuggets. Dendi likes to discuss problems and share ideas with others. The gold digger account is Dendoink. You can follow him and add him on wechat if necessary.
In my heart, I would like to thank Brother Dendi for his careful guidance and valuable experience and advice, which makes me more clear about my career development and growth direction.
First of all, the following content is more to provide methodology and ideas, not technical discussion, after all, looking for a job is not entirely technical, non-technical experience is sometimes more useful than technical.
My exact words were:
Dendi, I would like to ask you a question, I am looking for a job recently, if you are the interviewer, what do you value about the candidate, or the focus and scope of assessment.
Dendi’s advice is summarized as follows:
1. School or social recruitment
Clear oneself is to apply for a company to recruit or school recruit, if be school recruit, lay particular emphasis on foundation; Social recruitment focuses on project experience. Pay more attention to the study of professional courses, solid foundation has the potential to always find a good job.
Most companies are eager to recruit people to do projects, so the main consideration is your project experience, to see whether you can quickly start the project, technical stack mismatch, teamwork ability, and tool use, to see whether you are familiar with the things used in daily development.
2. JD
We should obtain information from JD (job requirements) at the very beginning, which is the key assessment content in the interview process, so we should focus on review. However, it should be noted that some JD is roughly written by HR, so the first step is to make clear the requirements on JD and sort out the design to technical points.
3. Communicate with HR
The first phone call with HR is critical. Find out as much information as you can before the interview. For example, team size, working hours, salary, the background of team members, technical aspects to understand the technology stack, after entering the project to take over.
If hr does not know the technical project, ask them to ask the technical director. They should try their best to take the initiative in their own hands. Do not rush to the interview in case it is not their ideal, they will waste each other’s time, which is bad for both the company and the individual. Therefore, it is very important to communicate with HR for the first time. We should try our best to obtain such information before deciding whether to go to the interview.
4. Assess project capabilities
The interviewer will check your project skills against the project experience on your resume, usually he will ask very detailed questions to look at your project skills, to find out if you did the project, which modules you were responsible for, and to what extent.
For example, H5 page development in the process of what problems ah, have optimized ah, small program written, vUE used to what extent, Webpack configuration optimization will be and so on. All you need to do is describe the projects on your resume in as much detail as possible, down to webpack configuration and bugs encountered during development.
Descriptions can start from modules, functions, technical implementations, problems encountered during development, and principles.
5. On foundations
About the foundation, this is sure to be assessed, the interviewer mainly see your knowledge is not wide, do not understand the latest standards, do not pay attention to technical dynamics. The use of the code framework does not understand its principle, you are a good scholar of technology or conformity of the code porter.
6. Get to know the team
When the interviewer has finished checking you out, it’s usually your turn to ask questions. It’s a great learning opportunity, of course, but more importantly, it’s a direct opportunity to get information about the positions on the team.
- You can ask whether the company attaches much importance to technology. If the technical department has no voice in the company, it will be very tiring to work in this company. There will be a group of people who don’t know the code to teach you to write the code like SHI.
- Ask about the configuration of team members, such as how many front-end, generally 6 to 10 front-end teams are better.
- The technical background of the team members, whether they are outstanding, to what extent they are outstanding, what kind of excellent system they have led, and whether they have a plan for team building.
- The development process is not complete, whether there is a unified and standardized process, whether the project has a process from construction, development, testing to online automatic deployment. My practical experience tells me that a team without standardization is not an efficient team. Some of the time in the development process is spent in filling holes. For example, inconsistent code styles lead to no major changes in the code diFF after merging, and unstreamlined testing may lead to getting up in the middle of the night to fix bugs. If the line is not automated, it may stay after work and wait for the line to be tested again… (Tears in his eyes, remembering his own experience)
- Although do not resist overtime but ask the technical department will often work overtime, do not waste youth time on overtime, their own body will be unbearable, their time than overtime get those money is much more valuable, to use their own time precipitation valuable things.
Evaluate your immediate boss
During the interview process, there may be several interviewers, and it is important to know which one is your immediate supervisor. Mentally assess his personality, style, speaking style, values, technical vision. After all, your immediate boss has a lot to do with the job, and if he or she likes to blame others and is difficult to get along with, he or she will have a hard time.
Mentality 8.
Don’t worry, do more exercise, after all, have a good attitude and healthy body, will always find the ideal job.
9. Other
Recharge your batteries. Read more, make more friends, share more. Notice I’m not talking about technology entirely, but other aspects of learning and communication. Those who engage in technology cannot completely engage in technology. Technology is to solve people’s problems. We should make technology truly valuable. How can this be done?
To jump out of the technical perspective to see the problem, more understanding of the industry dynamics, more request god, more communication and sharing with people, after all, the Internet people who earn the most money are not the most advanced people.
conclusion
I am also on the way to learn and grow