An overview of the

After a little over a month, I came back. During this period of time, many people asked me what I was doing recently, when I wrote my face, why I didn’t write more for so long and so on. Of course, recently I’ve been making a job change that I’ve been planning for almost half a year. All in all, not bad. Tell me about me. I started planning in September last year and began preparation in November. I applied to more than 100 companies and got 20+ interviews. In total, I interviewed four companies and got 3 offers.

This may not be suitable for everyone, after all, this is not a big factory. But the content may you look at at least will find themselves lacking in what knowledge points. Suitable for:

  • Degree in general

  • Intermediate level development with general skills: 1-3 years after graduation

  • Android application layer development

I’ve covered how to send out resumes and screen interviews and offers in a previous post, so I’m going to cut to the chase.

Technical reserves

First, let’s talk about what we need to know about the interview. Whether it is the Foundation of Android or Java, as well as common data structures and algorithms, these are undisciplined and must be mastered, especially non-computer major students, the interviewer is sure to ask you the foundation, if the foundation is not good, it is easy to be buckled on the foundation of the hat, the common ones are those, As long as you usually think about the interview is basically not too big problem.

As the saying goes, the interview builds the rocket, the job turns the screw. So be prepared. Some things will be forgotten if not seen for a long time, but some things will not be forgotten if not seen for a long time. So the way you learn is very important. All right, let’s get out of here. (The order of the interview questions may be different, the impression of the memory of the interview questions)

Interview the company

A Company (Offer)

The company is mainly in the data cloud, and it’s a medium-sized company.

  • The interview questions

    1. Adaptation of curved screen

    2. Should an activity have a static variable

    3. Event distribution

    4.Handler

    5. The APP

    6. User experience

    7. The two startup modes of service and their differences

    8. Bundle mechanism

    9. The Android 7.0 features

    10. Kotlin point of view

    11. The difference between listView and RecyclerView

    12. How to save data destruction

These questions were asked by the same interviewer twice. To tell you the truth, this company did not go well in the interview. The interviewer started with a question. WTF? How about introducing yourself? At that time, I was still a little muddled, but also an instant reaction, changed to follow his questions to answer. Within ten minutes of the interview, he said, I’m very pleased with you. How about salary X? WTF? I was wondering what happened. But I said I wasn’t satisfied with the salary. And he said why don’t you test you again? So, as I said before, I was asked these questions twice by the same interviewer. The interview went back and forth for about an hour. Finally, I made an offer.

B Company (over)

This company is a well-known education platform with a Series D financing, good scale and nice environment.

  • The interview questions

    1. The principle of a hashmap

    2. Java 7, 8, 9 and 10

    3. The principle of lambda

    4. Why can’t Lambda be used in Java 7

    5. Level 3 cache

    6. The setcontentview principle

    7. Gilde principle

    8. Which memory is faster, string or StringBuilder

    9. Event distribution

    Thread 10.

    11. How to learn.

This company was the one I most wanted to go to among the several companies I interviewed for, and it was the only one that was passed. But in the end, I was pretty much killed. Look at the above interview questions may also know that the difficulty factor is still a little bit. It’s almost certain, though, that the interviewer was born in Java. For example, in the first question, Hashmap, after asking how it works, what does a Hashmap store? Inside hashMap are linked lists and arrays, so how do arrays and lists store and delete data? Basically, every question you ask leads to questions about the JVM. The JVM is a nightmare for me at the moment…. So it’s straight over.

C Company (Offer)

A publicly traded company that does new retail.

  • One side

    1.IO

    2. Write array to implement queue

    3. Can you dynamically add the same layout

    4. The Handler mechanism

    5. Handwritten RxJava traversal array

    6. The scheme

    7. Expand the array

    The difference between a listview and a RecyclerView

    9.service

    10. How can threads be safe

    11. Aop thought

    12. Give yourself free rein

    13. A hashmap principle

  • Second interview

    1. Five-year plan

    2. Have you considered moving to, say, ios

  • On three sides

    What has kept you blogging for three years

    Asked about the degree, talked about the product

This company also had the longest interview, more than two hours before and after, and I was not good at the first part of the interview. However, when asked about Java content, the interviewer clearly said that I did not know what to ask about Java, just ask casually, and then mainly asked about some Android content. Basically still be on the spot handwritten, of this kind of handwritten yao, know how many handwritten how many. A second interview to talk about things is not very much, before and after half an hour. Three sides. I just went to see your Github and your blog, and I asked you how you’ve been doing it for three years. I talked about some of my views, including the background and products, I respectively said my views. Finally, I listened to him very magically. Why don’t you come to our company to make products? WTF? I was surprised. So although the technical aspect is general, but three sides chat is very nice. Finally, I got the offer.

D Company (Offer)

A company with Series C financing, o2o platform.

  • The interview questions

    1. The principle of a hashmap

    2. This principle

    3. Thread safety

    4. Principle of SParearray (subcontract)

    5. Gc mechanism

    6. Gilde principle

    7.rxjava

    8. The Ui optimization

    Performance of 9.

    Thin body of 10.

    11 have seen the framework source code, and then ask the principle

    12. Singletons

    13. Listview and RecyclerView and Scrollview nesting issues, and the difference between an RV and a LV

    14. The difference between Android2 VMS (one before 5.0 and one after 5.0)

The company asked a lot of things, met not the interviewer and I said what is what. The main reason is that I went to the C company early and took the subway for the interview for more than one hour, but I felt very sleepy all the way. So the answer is more general. At the end of the interview, the second interviewer came and said that I had no problem with technology development after the first interview, and the second interview was a specific part of my understanding of the company. A little bit of questioning. After the last said, will let HR send the offer.

Talk about non-technical interviews

The above problems are mostly technical. Let me just talk a little bit about the non-technical aspects of the interview, the non-technical interview usually tests your communication skills, presentation, emotional intelligence and so on. But it usually revolves around the direction of the company, products and so on. Therefore, only good technology or a little. For example, some companies ask, what about our products from the user’s point of view? So before the interview, it’s best to check out the company’s app. If you don’t find the app, you can also go to the company’s official website. For example, I did not find the APP of company A, but I went to the official website to see what the company does.

summary

After the interview, I should learn to summarize what my shortcomings caused XX company not to get the offer. For example, I failed to get the offer from B company because of the weak JVM and data structure. Once we find our weaknesses, we need to take the time to make up for them, whether it’s purely for the interview or for future technical precipitation. To put it bluntly, it’s all for their own good. Through this interview, I also know which aspects of my shortcomings, for future consideration, so I will spare some time to make up for this aspect.

The road of life or to their own, others give you some direction at most, but usually do good, don’t ask the future, step by step efforts will be rewarded. I hope that after reading this article, I can find my own problems, move forward, and give my future self a chance to be grateful.

Gold mining technology essay link 👉 juejin.cn/post/1

For more articles, please follow my official account: