I recently talked to a programmer with a good resume about the interview of Ant Financial, but the news I heard was that I didn't pass the technical side.

This confuses me. Later I found out that this is not an exception. Many large-scale programmers with about two or three years of work experience have encountered technical bottlenecks.

Work is getting more and more comfortable, but instead of losing the enthusiasm for active learning, no longer assiduously study technology and understand new knowledge.

And as a group with more serious overtime work, sometimes even changing codes and working on projects all night, even more lack of time for in-depth thinking.

But I have to say that these are just some excuses to comfort myself. The first year of work is often the fastest year of technological improvement, with enthusiasm and passion. With the passage of time, there are not a few people whose technology is still in the state of one or two years ago, and mistakenly treat repetitive operations as skill experience.

Before analyzing the reasons why one's technical level has not been improved, first have a clear understanding of which areas of ability are concentrated:

1. Technical Depth

Do you have a deep understanding of the architecture design ideas of message middleware?

Have you ever delved into the architecture design of middleware or distributed transaction framework?

How to deal with faults and optimize the underlying system in tens of millions of concurrent scenarios?

2. Technology breadth

Do you have a certain understanding of a series of related technologies such as high concurrency, caching, high concurrency, high availability, and microservices?

3. Project experience

This is definitely an icing on the cake. Have you been responsible for a large-scale, highly available, and highly complex system architecture design for tens of millions of users? Or are you just responsible for the CRM system and OA system of dozens of people?

"All the events we have experienced are not emergencies, but the result of a series of gradual and change." The feedback mechanism of time will never lie . It is far from enough to have a big factory goal. It is necessary to make up for shortcomings, arrange daily learning reasonably, improve efficiency, and so on.

The following is the interview process recorded by the programmer himself after he went to Ant Financial for an interview . Friends who need information, click here to get it!