preface

Meituan three aspects of the classics, one side did not record, make do with it hahaha

Second interview

  • Why are you leaving?

    • The project is too perfect, I want to go to some less perfect project team, experience the project gradually perfect process…..

  • Give yourself a score on what you know about the project

    • I give myself 60 out of 100. “Say the next reason”, after speaking, “that is, you have not understood your system, why not in-depth study, to leave” ？？？？？

  • I want to talk about projects and I want to talk about project meaning, project modules, line of business processes, data flow. As a result, he asked me what the input was and what the output was. What fields were the input and what fields were the output content?

  • Which of these businesses are you responsible for? Tell me about the typical things you do

  • QPS, performance bottlenecks (I said no bottlenecks)

  • If 10,000 times the flow, can the service withstand, what is the bottleneck, how will your service,? And you said there was no bottleneck

  • What about service availability? What is your availability? Several 9?

  • How to do manometry, manometry to see what indicators…

  • Pressure measurement to see CPU with memory, how to look specifically, what value of CPU? How to determine whether memory is good?

  • If your service gets 10 times more traffic, what do you do

  • How do you limit traffic? Why do you use token buckets

  • How to get a unique ID in distributed system, is your system useful

  • In the project, I mentioned redis, and explained how redis is used.

  • Why is Redis fast

  • Why not use another NoSQL database?

  • What’s RDB,AOF? How do you use it

  • How do you deploy redis, double room and multiple nodes, how do you deploy redis inside the machine room (I said cluster + sentry, but I didn’t explain clearly, just talk about a concept), he thought I was talking about the concept, didn’t really understand

  • Why do you need to perform two-room DISASTER recovery and when will the entire cluster fail

  • Kafka? What do you use Kafka for? How does Kafka keep messages from getting lost

  • If 10x traffic comes, can you Redis carry it?

  • Why double machine room

  • Deadlocks? Tell me

  • Multithreading? Talk about the difference between synchronized and reentrentLock

  • Write the consumer producer model

On three sides

  • Why leave
  • What kind of job are you looking for
  • Tell me about something you’ve done
  • What is good for you to understand a system
  • Mysql dateTime timeStamp
  • Inner class vs. static inner class
  • What about frequent GC
  • TCP know!
  • What are HTTP headers
  • Cube roots of floating – point numbers

conclusion

Here are the main things to note about the interviewer:

  1. Don’t interview back-to-back, preferably after the interview, and if you have a choice, don’t interview back-to-back. Because I’m tired.
  2. Don’t bad-mouth your old employer or you’ll get your interviewer fired up.
  3. Don’t come to the interview unprepared. I’ve had some interviewees who, in the middle of their answers, would break down and say they were busy and didn’t have time to study. Just because you didn’t have time to prepare for the interview, the interviewer won’t give you a pass.
  4. The foundation should be solid, if you want to enter the big factory or the company with good technical atmosphere, you must pay attention to the foundation, even if you are very familiar with the framework source code, but the general telephone or one side, is not to ask the framework.
  5. Job-hopping is frequent. When a candidate is at a loss for employment, the boss looks at his resume and finds that his previous work experience is 7 months, so he simply abandons it. One candidate had 8 years of work experience, but each job experience was just a little more than a year longer. Fortunately, he had a solid foundation, so he passed. If you are good enough, it won’t make much difference if you change jobs more often. If you are general, do not often jump, the best in a company precipitation precipitation.

omg

Thank you very much for reading here, if you think the article is good, please follow it, please like it and share it (very, very useful to me). If you feel the article needs to be improved, I am looking forward to your suggestions, please leave a comment. If there’s anything you’d like to see, I look forward to hearing from you. Your support and support is the biggest motivation for my creation!