It’s been a tough year, and job losses are at risk across industries. As programmers, we also feel that it is difficult to find jobs, and resumes are being ignored. All the calls are outsourcing.

I think I am lucky. I have met about 5 companies and received offers from 3 of them. Among them are Internet of Things, fast-growing enterprises, and Ping An.

Today is the weekend, I sit down to summarize some of my interview experience and share with you. I hope I can help you a little. That’s good.

I’ll start with the following points

I. The current market situation

Ii. Requirements of technology stacks of different companies

How to write your resume

Four, the interview mainly asked about the technical points

How can we improve our core competitiveness

I. The current market situation

  • I started to look at the interview opportunities from The week of August 10th, and I sent my resume to the boss one after another. Basically, I got a reply and asked for my full resume. And then there are some parts of no reply, maybe it is not very matching, and then have a reply were called to the scene interview.

  • About statistics of 10 delivery, 8 or so to resume, 3 or so have an interview invitation, the whole is ok. Because I hide the resume, only targeted to the company. This will save you time and you won’t have to outsource your phone calls all day. Of course I don’t have a problem with outsourcing. It’s personal.

  • Soon will be September 10, gold nine silver ten or on the whole better. At present, the epidemic situation is basically better, and the on-site interviews are basically conducted in Shenzhen.

  • So this period of time is relatively good, if you are ready to rest assured to deliver. Not ready, hurry to prepare, soon to the golden period.

Ii. Requirements of technology stacks of different companies

  • In terms of the technology stack, most people now need to know or have experience with the Spring Cloud. Because with the slow growth of the enterprise, the basic are in the development of micro service, basically micro service is the mainstream.

  • Then to the basic such as Spring some source code read, if not, at least IOC, DI, AOP, things or to have some basic understanding. These basic features and advantages of the collection framework to be more familiar, this is we usually use the most.

  • For some SQL tuning of the database, some knowledge of the B+ tree of the database, indexes, and Explain execution plans are also necessary. There are some principles for index creation and so on.

  • Secondly, some understanding of our Nosql database such as Redis, mongodb and so on. Data structure, pros and cons, usage scenarios, etc. Redis cache data consistency and other problems optimization, solutions, etc.

  • Then there is our message middleware MQ, the peak clipping, valley filling, decoupling weapon. Some understanding of sequential message, message loss, message idempotent, message repeated consumption and so on. Or sometimes practical experience is best.

  • In addition, it is our micro service, the background of the birth of micro service, what problems it solves, the problems it brings and so on. In addition, a set of components incubated by the current mainstream Spring Cloud Alibaba is also very popular. Our GateWay GateWay layer, Nacos registry configuration center, Sentinel’s current-limiting fuse, feign’s restapi call method, rabbion’s load balancing, seata’s distribution is things, and so on.

  • That basically covers most of the technology stack. If all of this is pretty much the same, then the interview should be no problem.

How to write your resume

A resume is one of the first things you see when you meet with interviewers and HR, and if you haven’t put your heart and soul into it, there’s no point in it. Of course a good resume is comfortable at a glance.

We should not be sloppy in layout, project description, work experience, major responsibilities, etc.

I say a few of my suggestions, I hope to help you:

  1. Project introduction is not long, concise and comprehensive, more crowded together looking more uncomfortable;
  2. The module I am responsible for highlights my responsibilities, describes the work within my responsibilities, the difficulties encountered, the difficulties solved and the promotion achieved;
  3. The technology used, the problem solved, and why this technology or framework was chosen;
  4. What did you learn from the project?

Here’s an example:

A: Redis, RocketMQ and other components are used in the project.

B: Redis is used in the project to cache hotspot data, which relieves DB pressure and improves service response efficiency.

RocketMQ peak clipping and valley filling is used to decouple services and reduce service invocation link length;

Which of the above, A or B, looks more comfortable?

I believe that this adjustment, after thinking to write out the resume is more pleasing to the eye, love at first sight.

Four, the interview mainly asked about the technical points

In fact, when the interviewer communicates, one is to see your mastery of knowledge points, followed by the depth of your mastery. I remember answering an interviewer’s question like this:

Interviewer: What if I store a value in a map and my hashcode for that value is the same?

Me: before JDK1.7, the value will be stored directly in the linked list, because 1.7 and 1.8 will handle the hash conflict differently. 1.8 also exists in the linked list when the length of the linked list is less than 8. When the length is greater than 8, it will be converted into red-black tree for storage. On the one hand, it is mainly to prevent too much data from affecting the query efficiency.

I believe that what the interviewer wants to know has been made clear to him, and your impression will be better.

The technical point of this, need not say more or the foundation, this is really very important. You must know it by heart.

The second thing is our Spring, some features, IOC, DI, AOP, things, etc.

Then the data level of Mybatis, Mysql tuning.

And then there’s some caching middleware, messaging middleware. Avalanche, penetration, hot data updates, message backlog, message accumulation, message idempotent.

Then there are some extensions of the framework, selection, use scenarios and so on. Some practical experience in the project, some heavy and difficult points in the project.

How can we improve our core competitiveness

As a programmer, I think the only thing is to keep learning, and constantly improve their hard power, so that they can continue to grow up. In the fierce competition has a certain foothold.

If you help, remember to give me a thumbs up oh ~ of course welcome to pay attention to my public number, back-end architecture advanced, I continue to sum up some source code learning, micro services, interview related to some of the content.

All dry goods, looking forward to your attention!