Say it in front
First of all, let's talk about my basic situation, I am an undergraduate civil engineering, BaoYan this school computer, Bao Yan because of the interdisciplinary so I was transferred to a master's degree, a total of two years, so only half a year to prepare to find a job. [Cross-insurance related experience, I have a link at the end] Our laboratory is basically doing longitudinal topics, and the training plan of master's and master's degrees is consistent, and there are not many opportunities for exposure to horizontal. Considering that it is difficult to be competitive in two years of making algorithms (actually only one year), and the internal volume of algorithms in these two years is more serious, I began my own self-taught research and development path.
Throughout the process of studying and preparing for the internship, the Nuggets and Cattle guests really helped me a lot, so after I landed, I summarized my own experience under the advice of the senior, and gave back to everyone, if you have any questions, please leave a message and a small window.
On April 8th, I received a verbal offer from Ali DingTalk internship, and my spring recruitment internship basically entered the end, and the posts on the surface were all back-end Java (bytes to go), ending with the oc of Meituan Byte Ali. The overall result was quite unexpected, because my resume did not have such a beautiful Java project as others (two projects one is my vehicle path algorithm design cpp, one is to do horizontal project web development Python), and there is no internship experience in a large factory, I think the main thing I can see in the resume is the weighted and digital model first prizes. I myself began to think about the internship at the end of January, after the third day of the Chinese New Year began to review the preparation, the overall time is even a little rushed, and as a beginning of preparation, using Java to write letcode to occasionally turn over the rookie of the doc check API, I am a little surprised that I can get to the present. Looking back on the whole process, I think I must have done something right, so I combed through my own experience and gave it to you as a reference.
Do you want to take an internship?
On the battlefield of internship recruitment, there are usually two types of people, one is the big guy who has been prepared, and when I dare not invest in the big factory, oc has already gotten the soft hand. One is a rookie chicken who is not prepared for anything and suddenly realizes whether I should test the water before the autumn move, such as me.
So the first question here, do you want to do an internship? What is the point of investing in internships if the laboratory is not put down? Will the internship interview will affect the autumn recruitment?
The first thing is to vote, even if you are not ready, you have to prepare and vote at the same time. The internship interview experience is very important, even more important for the students who are not ready, not ready for the usual state, such as I do not have the internship experience in hand, have not seen the real questions of the big factory, and have not felt the process of the big factory interview. In this case, the internship recruitment in the spring is your resurrection A, can not lose money and can not be deceived, blood earns no loss. If you don't vote at this time, the autumn move will really run naked on the battlefield, the internship 0offer is terrible or the autumn trick 0offer is terrible, everyone should have to measure.
For example, many laboratories in our school do not put internships, and the process of chatting with friends often encounters this situation, our laboratory is also theoretically not to put internships, but I think internships are important, for students without internship experience, the internship interview experience is also very important, like Ali, who can't come to the internship can also go straight to the end of the situation, really very friendly. Therefore, even if the lab does not put it, I highly recommend to take a shot and precipitate the interview experience. If it is over, if you receive oc can not go to refuse, communicate with hr well, it is said that people will come to ask you for intentions (not pigeon offer, pigeon offer may be blocked)
Then the interview is brushed off without affecting the autumn moves, the big factories I have faced, are replied to have an advantage in the autumn moves that have been recorded, and if they do not pass, they will not be affected. I've even seen the big guy's sharing before, saying that ali's children's shoes have more than one interview record, whether they can pass is closely related to ability, department situation, luck, and on-the-spot performance, too much does not mean strong, but it does not represent nothing.
To sum up, the internship interview is a very low-cost trial and error opportunity, and everyone should seize such a stable opportunity to make money.
Interview preparation
Next, let's talk about my preparation for the interview, two months to prepare at the same time, it is relatively rushed, but it is also very suitable for students who are not ready at present.
Computer foundation, operating system, networking and data structures. I went through the textbook before the interview and wanted to summarize, some of which I used my previous notes, and some of which moved some blogs and github content. This part of the review took about 15 days, during which time I also brushed the algorithm questions every day. Have their own knowledge points summary, followed by a process of checking and filling in the gaps, the questions seen on the cattle will not be, find the answer to add in, high-frequency questions, take out the answers to prepare, and go through it before each interview. Refer to my github, note_md high-frequency part, in addition, I recommend that you can learn from this summary of CYC2018 on GitHub to sort out the knowledge points. My own project was mentioned above, but it is really not as good as cyc, and the link will be given at the end of the article.
Computer basics are the top priority of big factory interviews, and don't memorize the answers, it is useless to memorize them. Ali's interview as an example, the operating system and algorithm part, some places I can't remember, the interviewer prompted it, I showed the interviewer the idea of pushing out the complete knowledge points, I think the process is actually more than directly giving the answer.
The algorithm problem to brush, my order is twice the sword finger, pick out the optimal solution that will not be, and then go over again. Then the suitecode question bank of CYC2018 brushes the data structure part first, and then brushes the algorithm part. The interview hand tear original question hit rate is very high. When brushing questions, I encounter unfamiliar ones, such as I am unfamiliar with dp and trie dictionary trees, systematically turn over textbooks to learn to take good notes, and do some targeted algorithm problem consolidation. Algorithm problem ah, there is no need to die, when you first brushed 20 minutes completely clueless is normal, read the answer again, tomorrow back to write it yourself. I have three brushes on the fingers of the sword that can't remember the optimal solution, and don't force it if you can't remember it. Start with an hour and a half a day and start with half a day every day.
Then there is the java foundation, this part is more complicated, I recommend to find a more complete java knowledge point mind map, master the check, unfamiliar first from high frequency to low frequency preparation, and then the knowledge on the map one by one to fill the hole, the preparation process is not to find the answer to the high frequency question on the line, it is best to read the source code (not enough time can look at the source code analysis blog, and then with their own learning of the operating system / network knowledge point string a string). Learning materials and order, JavaSE I recommend "core java volume 1", thicker, the first six chapters must be seen, the back of the on-demand jump to see, it is best to compare with "Java Programming Ideas", I think the latter is more clear. jvm as long as you look at the most classic "deep Java virtual machine" that book, my own review of the Java basics is mainly to see the blog + source code, and this part has to see the Chinese version of "Java concurrency in practice", but it is ok to look directly at the blog + source code. If you don't have enough time, don't be too nostalgic for the difficulty, I have not read through AQS completely until now, the preparation process should be written demo, the memory of the things that run through will be much deeper, and at the same time, you must write a blog or take notes, and this will be the external memory of your knowledge system in the future.
Then back to the basics of computers, the high-frequency questions asked and the resume extensions are relatively easy to prepare. The difficulty is the open question, I can't prepare to rely on my own computer foundation to try to give the answer, but it may also be that my own foundation is not solid or the accumulation of limited knowledge is not enough. But my overall advice is to contact the operating system you've learned and the solutions you've learned to migrate. This part really relies on daily accumulation.
How to prepare a resume
The first is strategy and attitude, you are responsible for every word of your resume. If you prepare them carefully, that's your highlight, or the interviewer catches your hole. The resume is the part that you can control the whole scene the most, and you can't prepare for other problems, but the things on the resume can be prepared in advance. Each word should think about how the interviewer will take this to ask, prepare the answer according to the background, highlights, deficiencies, and directions that may be improved, and then accumulate the questions that the interviewer asks about your project during different interviews, and the resume-related things blurt out several times.
Resume without Java project how to do, I think the interview Java with Java related of course the best, but I really do not have a complete good-looking Java project, this is my short board, was Ali hr hanging hit, almost hung me. But if there is no temporary put together is not as good as a is not Java but very complete, complete to you review, and better comparison, it is best to compare the back to improve, if you do the last step this project is more complete, I only do to find excellent similar projects to compare, but also got praise. A Java project can reflect your familiarity with the language and its ecology, but an incomplete project can also leave you with loopholes in interviews.
Their own projects, used framework related high-frequency interview questions must be familiar, the source code has spare time is best to be able to read, it does not matter if you can't finish reading, never read is the attitude problem. Ask about the part of the source code that you haven't seen, you can say that you haven't seen that part, but you're looking at this part, and you're back in the field you're familiar with. I myself will secretly rub and search for some spring interview high-frequency knowledge points, but mainly for emergency, I am not in a hurry now or nibble a little spring source code every day.
Then about the resume template, there are actually a lot of friends around me to ask me for this thing, this point I actually can't think straight, this stuff should be a lot of online bar, here also to show you some of the templates I sorted out, are quite simple, there is no fancy
Students who need to forward this article + follow + private message [template] can be
Interview routines
First of all, I have recently faced so many impressions, internships do not have to have a good project, but the foundation must be solid, and at the same time, you must take the interviewer to where you are good at, and your own front line should not be too open. To give a counter-example, say that you are familiar with mysql, say that you use Spring 6, and then to zk, dubbo, the interviewer has high expectations of you, a question has not seen the source code, and then it is easy to cool down.
On the contrary, don't expect too much from the interviewer at the beginning, such as me, I know my cuisine, so when I introduce myself, I say that I am familiar with javaSE, I have used mysql, redis, Spring is still learning, and the source code may not be very familiar. Then after the interviewer starts asking within the scope of your circle, once you ask about the part you have carefully prepared, you can set up a serial set for him, and the interviewer may be impressed by you. For example, hashmap set concurrent HashMap set volatile, if he follows the prepared question, on these three I chat source code can be said to be more than 40 minutes, similar in mysql, redis, and other JavaEE frameworks These technically also have the point of frequently asked to prepare to talk about, the points that are not often asked are not impossible to say, and the basic disk of an interview is set up. Interviewer he may jump out of the circle you draw, for me such as asking about javaEE related, if you happen to be prepared, the same is to answer a knowledge point, the interviewer's feelings under different expectations should be different.
In addition, encounter will not be knowledge points, but you have your own speculation, it can be said that this part I am not very familiar with, if I come to do it may xxx, because I think (speculative reasons), I will go down to understand this part. In my limited attempts, there are still quite a few cases where the interviewer nods here, mainly because I guessed correctly. For the kind of one that either is or isn't or you can't make up a reason even if you guess it, honestly sorry this part is a bit mushy. On the one hand, you need to show that when you encounter a problem, you are more active in thinking of a solution, on the other hand, you must also be honest, but if you will not say too much, it is estimated to be cool. For example, my mushroom street, I said that recently I wrote a demo to make a relatively simple web server, said more than a reference to the tomcat source code, and then was caught asking a bunch of tomcat I am not familiar with, it is gone.
Strategy and mindset
I realized the importance of the noodle internship from the cattle sticker, and most of the internships I found on the cattle and nuggets, as well as the noodle scripture. See everyone has an offer, I was very uncomfortable every day at that time, did not dare to brush the cattle nuggets, felt that the difference between people and people is really too big, and there is no confidence in themselves, the face is either cold or no news, every night at one or two o'clock do not dare to stop learning, do not dare to sleep, lying in bed will also doubt life.
My own mental attitude in the preparation process is indeed not good enough, very anxious, but I think there is still a merit in strategy. Interview preparation on the combination of points and surfaces, high-frequency questions are points, computer basics are surfaces; When choosing a company, when you have no interview experience, it is appropriate to invest more, and the company you want to go to is a little behind. Again, whether one side or both sides have a positive effect, if not, it will not affect the autumn move, bai prostitution a favorite factory trial and error opportunities. It's also possible for someone like me to go in face to face, and I'm a real rookie.
btw。 Choosing the computer industry means that to a certain extent, the technology to settle down, opportunism must not be reliable, to do a good job of long-term planning and continuous integration, such as my lack of distributed related knowledge and project exercises, I will also make up for it as soon as possible in the near future, and strive to become a real big guy.
Then play an advertisement, Ali DingTalk urgent lack of resume, other bu hung up the opportunity to fish, java back end and front end, base Hangzhou / Beijing, ball ball, I also have to find resume kpi, there are currently more than thirty hc, everyone walked by, throw a resume, I can also sell art online to help change resume, and Ali senior help to change and make suggestions, timely follow up I know the result after each round of face up to a day, a week to complete the process, people are super good.
I landed really a lot of luck and the help of seniors, as well as the interviewers in each round of interviews were very equal to me to exchange technical discussion questions, did not give up on me because I did not have a good Java project, many questions were very difficult but also very enjoyable.
For those who are interested in us or seeking fishing, you can send me a private message of "name + telephone + mailbox + college + delivery position", and then send an internal push email to these students, and then fill in the email to complete the delivery. You can also scan the QR code to deliver, remember to say to me in a private message, I will help you dock here.
The above is what I think of for a moment, and then swing a wave of resources
Book list (also the chapter i found from other big guys to verify by myself, other chapters should be read slowly)
- The sword points to the offer
- An in-depth understanding of the Java Virtual Machine Chapter 2 Chapter 3 Chapter 7 Chapter 12 Chapter 13
- Mysql must know must know + leetcode-database title
- High Performance mysql Chapter 1 Chapter 5 and Chapter 6
- redis design and implementation dictionary hop table expiration mechanism persistence event replication Sentinel cluster publish and subscribe transactions
These books should also be found online, lazy to find friends can find me, pay attention to + private message [study books] can be
Project resources
- spring boot
- Spring cloud microservices
These hands-on projects, if you can't think of what to imitate, but I still recommend that you think about the project yourself, such as imitating spring to write an IoC container, imitating tomcat to implement a small web server, these are the choices of a rookie like me, the big guy detours.