Now taking the bus back to school, just finished the interview brain bomb pain, really unable to review, write a face classics right when relax. In the interview, MOMo only asked about the project and source code. In the end, HR said that the interviewers on both front and back had good comments, and they might send an offer after confirming with the HR director, but they didn’t send it at all. They even wanted me to be a monitoring tool, so please forgive me.
One side
HR to content
Maybe it was momo’s interview style for part-time interns. At the beginning of the interview, momo talked about “how to guarantee internship time” and “why I left my last company” for more than 20 minutes.
Project experience
Then I started talking about hawk, the Hadoop cluster monitoring tool I made in Sogou.
I didn’t understand why I was talking about the project at first. Later, after talking about the project, the interviewer said, “I made a monitoring tool that was written in Python, but it never came online because I didn’t have the time. If you come here, we will rewrite the program, but it will not be a single point, it will be distributed.”
Hadoop cluster monitoring tool – Hawk
Their dregs project, such as later change it change it hope can do some better, open source out, here is no nonsense. Most of the points will be asked to the end, fortunately the project itself is relatively simple, fewer points.
As for this project, I don’t think I spoke well. I was nervous at the first time, and my speech was halting.
The source code
The source code part of my preparation is not good, 2:30 PM interview, 1:00 when I started to review the original reading notes. By the time the interviewer called me for an interview at 2:50, I had just gone through all the important questions I had solved. I didn’t go over the Yarn source code example I chose, but I still remember that example, so I basically answered it.
Select Yarn source code
I talked about the general process of the Kill App.
All the key points are there, but it’s not complete. Start with an asynchronous reclaim container and the Container exit code, and end up forgetting the container exit code. But the interviewer didn’t remind me and moved on.
Describes the HDFS file creation and write process
The interviewer asked me if I had read the source code of HDFS. I just said I saw a little bit. Let me choose a lecture, I said I would talk about the difference between DU and DF, the interviewer asked me to talk about the process of creating and writing documents.
The problem is with the DN exception when writing data to the pipeline stream. I read the source code of 0.20. In that version, DN failure is directly discarded. When the file is written, NN will uniformly check and issue the data block copy command. However, this policy has been changed in the 2.x source code (to be added).
Second interview
The interviewer for the second interview was a cute little fat man who liked to laugh a lot. I thought his level was lower than that of one side, but in fact he was the leader of the basic service group on the second side, and the leader of the subordinate platform group (and the subordinate warehouse group) on the other side.
Project experience
Cold data compression and cleansing tool — Vulture
Because I did not speak well about the first project, I hurriedly reviewed the project documents while waiting for the second interview. At the end of the lecture it was smooth, and all the leads came back. Therefore, since the project experience is their own, we must be familiar with and familiar with, in-depth in-depth in-depth.
Search for debug profiling tools
To be honest, while I appreciate meituan’s internship experience, I really don’t want anyone to talk about this Web tool again, let alone talk about it further. Here are three questions:
- Architecture of Web applications
- How to implement user authentication
- The principle of decorators
Well, I don’t want to talk about it in the book. I have only given a general outline of these questions, but I resist them and do not want to go further. The interviewer was about to ask, but I quickly expressed my lack of interest in the Web and the interviewer stopped asking.
What’s your problem
I asked three questions:
- Confirm what the job will be – it will be a monitoring tool
- Confirm the level of the first and second interviewers and the organizational structure of the internship department
- Check to see if you’ve passed (stupid! How can you just ask!
Now I remember I forgot to ask about my interview performance. The only time I forgot to ask, I got whipped up
HR side
Momo has HR face, but the only two HR face I have experienced are percentage point and where to go.
I talked about my internship experience, the guarantee of my internship time, and why I left my job. And told me a lot about the internship world. Finally, talk about salary, treatment, etc.
By the way, the HR also asked me if I had received any offers from other companies. I honestly said, “Sorry, yes, and I have arranged other interviews later.” He also wanted to ask me the salary of the company after I got the offer. I deflated the conversation by saying momo was my current favorite, and HR didn’t discuss salary.
Don’t spit unpleasant
A few things to tease about corporate hospitality:
- The interview was at 2:30 p.m., and everyone who came to the interview was waiting in a small conference room. Some people were writing interview papers, others were just sitting there, one was called out, and then another was arranged, just like in a Nazi movie. It made people nervous. I had to wait a good 20 minutes before the interviewer called me and asked how long I had been waiting. He said he was in a meeting and didn’t even apologize.
- No place to interview, go to a cafe in Momo, sit by the window, the sun is burning, the interviewer did not think to pull down the curtain. This is a little pretentious, but I miss those years of thoughtful mentors.
- One waited 20 minutes in front of the other; Two in front of waiting for more than 10 minutes, not long; HR waits for another 20 minutes. I’m so…
However, I can barely understand that there are a lot of people interviewing today. Momo may not have enough staff to entertain people in a small place. Understand each other. It’s not easy to find an internship, a job, or a company.
conclusion
The interview lasted from 2:30 to 5, and there was almost an hour of waiting. One side of the interviewer only clenched a project to ask in the end, until I asked the source code to change the brain to rest, behind has also been immersed in one side of the interviewer to pressure out. When I finally closed the elevator doors my whole body went limp. It was so hard. In addition, I received the offer from HR when I was still taking the bus, which was a recognition. Thank every company that gave you the opportunity to interview and thank yourself for all of this.
This time interviewers like to hold on to a point and ask questions in depth. It is good to simply look at this point, which can test a person’s technical depth and technical attitude. But the interview is about the project and some of the source code, nothing else. Maybe this is the style of different interviewers, but I don’t think it reflects the professionalism of the interview and is not helpful for the interview and personal growth.
In comparison, the interview of Ape Test Bank, Toutiao, Meituan and even Renrencar all seemed much more professional. I summed it up by myself and investigated the algorithm, foundation, project experience and system design on the whole. Basic examination, including but not limited to language, theory, operating system, network, etc. The general examination of project experience is used to examine depth and breadth, often extending horizontally or vertically from project experience to basic and system design; The system design test may be optional because of low requirements, or it may be based on fundamentals (e.g., let you design a HashMap, to support XX function) or project experience (e.g., where the project needs optimization most, how to optimize). Different companies have different priorities.
Advice to yourself:
- Practice project descriptions in private, asking yourself to be able to systematically and concisely state the main points and extensions
- Continue reviewing the source code. Also, when taking notes, make sure you know the version of the source code
Link to this article: [Face] Momo – August 28, 2017, Intern of A Mass recruitment program Monkeysayhi.github. IO This article is published under the Creative Commons Attribution – Share Alike 4.0 International License. You are welcome to republish, reproduce, or use it for commercial purposes.