The test algorithm, as many people say, know an algorithm and what can be done, may work a lifetime can not be used, even if it can be used, a lot of algorithms have libraries and packages to achieve, bring to use is. Indeed, so the test algorithm, not for the test, in order to will, but in the process of exploring the algorithm, to examine and verify whether a person is smart, whether the basic skills are solid, whether the smooth communication, whether the ability to quickly respond and learn. In the process of discussing and communicating, discover the flashpoints. Being able to think or speak is not the point of the test algorithm.

Looking at writing code again is more about examining and verifying the ability to get out of live. In a lot of cases, there is no requirement on what language to write in. In this way, one can examine the basic skills, no basic skills, it is impossible to be able to quickly out of the work. Secondly, it can examine the accumulation of usual training and experience, including the way of working, programming style, thinking method, and so on. The third is the initiative to accept the task and complete the task, is not willing to accept any team needs to complete the task. The fourth is the speed and quality of completing the task, that is, the speed and quality of producing work. This test of writing code would be a small snapshot of the work scenario that would follow.

From the process of writing the code and the code that is finally written, one can take an in-depth look at the basic qualities of a person, the way he/she works, and the conditions under which he/she comes out with the job, and the efficiency and quality of the job that he/she comes out with.

As for the initiative, or responsibility, there are many aspects and many ways to examine and verify, for example, chatting about the past project, the role in the project, the completed tasks, the quality of completion. In the process of chatting about algorithms and writing code, you can also get a glimpse of some of them, because it's hard for someone who isn't proactive and responsible to feint at accomplishing specific tasks.

About interviewing big data engineers, these tips you know, the green vine editor will share with you here. If you have a strong interest in big data engineering, I hope this article can help you. If you still want to know more about data analyst, big data engineer tips and materials, you can click on other articles on this site to learn.

The above is a small editorial to share with you about interviewing big data engineers, these tips you know? The relevant content, more information can be concerned about the Global Ivy to share more dry goods