Today we’re going to talk about finding a job
When it comes to job hunting, whether fresh graduates or experienced drivers, everyone is inevitably nervous.
Should I include all my project experience on my resume?
Is that an algorithm to remember? Is that concept going to be on the exam?
Is there an end to the interviewer’s routine?
Today I will share with you a senior development engineer from netease Xiang Wangfeng iOS development interview guide.
Netease mobile terminal technology expert, with rich experience in mobile development and IM product development. Love open source business, spare time a large number of open source components and technical articles output, iOS performance tuning have their own unique insights.
Generally speaking, no matter netease or other large companies, the recruitment process is as follows: resume screening – written examination – technical interview -HR interview. Generally, there are at least two rounds of technical interview, and there may be five or six rounds of technical interview if the position is important. The HR interview may also be followed by an interview with the department manager.
Relatively speaking, school enrollment tends to test students’ basic knowledge, thinking ability and development potential. In addition to these three areas, extensive project experience or being active on a tech blog are plus points.
Compared with school recruitment, social recruitment is more utilitarian, and it is more expected that the recruited people can directly start to do some projects. In this case, they are more inclined to consider the actual development skills and the matching degree of the project, and also consider whether the values of technology are different from ours.
In the following part, I will focus on the interviewer’s investigation and possible problems in the written test and interview process.
The site of the written examination
System programming
In this aspect, we will examine the three major components of the computer, CPU, memory, and hard disk related principles, such as process, thread, inter-process synchronization, inter-thread synchronization, memory stack, and so on.
Network programming
If you are just doing application and development, the requirements for network programming will be lower, but you should also have a general knowledge of TCP, UDP, and network layer protocols.
The data structure
This aspect will examine some basic knowledge, such as linked lists, stacks, trees, graphs, etc., trees and graphs may be less examination, but some commonly used algorithms are still there.
other
The written test will also cover the basics of the language, such as C++/ C and so on. About mobile development, iOS development, will also involve OC language and iOS basic concepts, network operations, some persistent things how to do, project experience and so on.
Interview research points
Basic knowledge of
This is not to say that if you pass the written test, you will not be asked about the basics later in the interview (although this is less likely if you are a social recruiter). For some fresh students, the interview to investigate the basic knowledge, which is a more important point of investigation.
Experience in project
In general, project experience we ask:
◾ What is the structure of your project?
◾ What is your project process like?
◾ What are the difficulties of your project?
◾ what is your project harvest like?
Some students might just say in an interview, “Gee, I do development. I don’t do process after process. I do process after process.” It is not desirable for an interviewer to leave him or her unable to answer questions about the difficulties and benefits of the project.
Beginning ability
We will decorate some questions, need you write directly, including the programming problem and the algorithm of topic, in general these subjects can be found online, such as looking for a list of which items from bottom, macro definition, there is a simple string title, binary tree traversal, and even a mobile phone number scratchable latex matching, etc., are some may have a little bit of hook, with actual development But it’s still kind of theoretical.
Questions that come up in an interview
Your resume is too long
Some students may wonder: Doesn’t a more extensive resume mean I’m more competent? In fact, interviewers are already so busy that a resume of five or six pages is just too much information for them, and it’s likely to contain information that isn’t useful to them. A good idea is to keep your CV as short as possible, listing all the key information on one A4 page and excluding irrelevant information, such as activities that have nothing to do with a technical interview.
Expression exaggeration
A recent graduate says on his resume: I am proficient in C/C++ and other languages. If you have been a senior developer in a company for five, six or even ten years, you may not say that you are proficient in C++, because the depth of the language is very deep, so students try not to do this description on the resume, if the interviewer is sensitive to this aspect, then you may not even pass the screening of the resume.
Poor preparation
In the graduation season, people may attend many interviews, often without time to prepare, you will be nervous during the interview, the interviewer asked questions, you can not play their normal level of answer, this is a failure of the interview. Make time to prepare before the interview.
Prepare too much
Computer science, or software engineering, is an engineering discipline that requires constant practice. Some students may memorize for the interview. For example, when I ask what is the time complexity of quick scheduling, some students will give the answer quickly, but the actual situation may be that the student only has a little understanding of quick scheduling, and will not write it in practice. He is just memorizing things for the test, which is a big no-no in an interview. The interviewer has a lot of interviewing skills to test your knowledge of the blind area, in fact the interviewer might throw a shallow knowledge, the first to let you answer first, and then the interviewer for in-depth and diffusion, this paper discusses the knowledge points, and then slowly to dig some interviewer really don’t understand something, let the interviewer to expose shortcomings and defects.
Although written/interview skills are important, developing students’ knowledge base and project experience is more important in the work. Over the next two weeks, we invited some of the best iOS developers in the industry to share their work and learning experiences.