2.5 hrs of remote written tests, 20 mins of technical phone interview, and 30 mins of HR interview.

The written test consists of basic problems, very easy, as well as advanced C problems.

It seems that 2.5 hrs can never be enough to finish all the tests, including debugging one piece of code. This might be their strategy for preventing someone from using any references.

The technical phone interview is quite professional.

Some questions about Linux socket and concurrent design, what is select, poll, epoll, etc. They are not very challenging.

Some regular problems such as how to solve the memory leak in C, what is the internal mechanism of a smart pointer (C++), etc.

They asked questions one by one very quickly, with no time for further explanation.

Finally, the HR interview was not friendly at all; rude, if I could say.

HR first told me the results of the written test and technical interview were very positive.

Then the lady asked questions and explained the structure of the team, like a robot!

She asked questions and you answered them, but got definitely no feedback, just like an answer machine. It was fast-paced.

She was trying to ask all the questions at hand. She was calling from her cellphone, and the phone signal was poor.

I told her the phone was cutting out and requested her to repeat the question. She replied, "Well, it seems you did not understand the question. Let's go to the next."

However, the questions were very normal, such as what is the biggest challenge, how you deal with conflicts, etc.

It took minutes for me to get adapted to the "answer" machine manner on some company culture questions, blablabla.

The following interview went smoothly. I just felt the HR was very impatient.

Five days later, I got an email with one line of message from the very same HR: "Hi xxx, You are not shortlisted to the next step at this time."

Just got rejected, with no reason provided.

Actually, it might be the shortest email I have ever seen. Nothing like a large company.

It seems it is the HR who made the decision. I am very disappointed.

It seems in this high-tech company, it is the HRs who make the decisions.

Generally, the technical questions are not hard. How to establish a socket server and what APIs to be used.

One guy in the team asked me to list the parameters of each API, such as accept, connect, listen...

I did not remember quite clearly. It was a weird question, since no one could deal with these "raw" APIs day after day if not for educational purposes. However, the guy seemed to be very serious about these, even the order of parameters.....er...