Week 3 Interview

Deep technical interviewing

On the one hand, I asked HR some basic questions and had a good conversation with HR. Two technical side, a very strong glasses of the little brother. We asked tornado how to write asynchronous library by ourselves, such as interacting with database, how to write asynchronous library here, Meng bi, I can only say THAT I am biased towards business. I asked you about the format of the HTTP request header, but I didn’t remember it. I forgot what kind of content-type there is. Asked the scientific principle of the Internet, just remember a bit similar to the jump board, do a forward proxy. I forgot exactly. Forty minutes, three, tech. It wasn’t good. Hardly any technical questions. Knowing that I was non-professional, he asked me a few professional terms… What are the three structures of a program? Who ever heard of that… Given the if structure, I said there should be a loop and order. And then said er graph, I haven’t heard of it, but I have experienced it in my design, but I don’t have this concept. I was asking some weird stuff anyway. What I said most was that “professional people have fewer problems, while non-professional people are worse.” They said that MY skills are too narrow. I used to work in OpenStack, but later I transferred to the background. It’s technology-driven and everyone comes in and learns from each other, which means I’m not good enough to come in and learn from me… I was at a loss for words. Yes, I was always a CRUD BOY and untrained, but why? I was confident that I could do no worse than others in business. Either you test data structure and algorithm, or you ask specific technology or scene, so beat around the bush, and I am not satisfied, it is better to directly say do not want me. It was a really bad interview experience. I felt that I had been judged by my eyes since I introduced that I was a graduate of Geophysics. All right, I’m going to something I can’t read.