Summary of recent internships

Table of contents

resume making

interview preparation

select offer

Internship preparation


resume making

Education background

    Fill in truthfully and speak with specific data. For example, the professional ranking Top X%, professional courses that match the position (do not need to write all of them)

    Graduation time and major must be written clearly. (I have an ordinary undergraduate degree, do not spray)

 Awards

        Fill in truthfully, it is recommended to rank down according to gold content. If there are many awards, you can't write all of them. First, choose the ones related to your work, and then choose the ones with higher gold content. It is enough to recommend 4-5 functions (here, the author only writes the experience that he thinks is more prominent on the resume). Some friends may have passed the soft test, but it is not recommended to write it on the award-winning experience, it is more appropriate to write it on the self-evaluation. For the award-winning time, just write it down roughly (if you remember, write it clearly, if you don’t remember it, roughly estimate it) 

 professional skill

        Extract the technical name as much as possible, and then expand the description appropriately

Remember: every skill and every technical term written on the resume should be familiar to you and be able to respond quickly. Don't write things that you don't know, it will be troublesome if you step on thunder. (Can be modified according to actual job requirements)

Project experience

Here I wrote a project that I am more familiar with (the autumn recruitment project on Niuke)

But during the interview, I told the interviewer about the dark horse cloud disk project, because the cloud disk project was done after making the resume and before the interview, so I didn't bother to modify it. So it is very important to have a good project.

It is divided into several parts: project name, development environment, technology used, and project responsibilities.

The most important part is to extract the technical points used in the project and express these technical terms. If the interviewer sees the technical name he will, he may ask you. Therefore, whether it is a professional technology or a project, let the interviewer see that you can ask questions on your resume, instead of not knowing where to ask.

Another important part is your responsibilities, just write the parts you are familiar with.

Because the blogger is looking for an internship job, the relative requirements are not so high. 

Explain again: The technologies and responsibilities extracted above must be very familiar to you, and you must be able to stand up to questions. Haha, although the blogger talked about another project during the interview, this project may be a bit low

Self introduction

This part is very important, do not copy from the Internet. Don't say a bunch of useless empty words. For example: I do things seriously XXX, I am XXX...

To speak with facts, you can refer to my modification for details

interview preparation

part of resume

       For the skills and extracted knowledge on the resume, this needs to be accumulated for a long time. In fact, the blogger feels that learning must be done in depth, such as a frequently tested C++ interview question.

        How to achieve polymorphism in C++, many answers only talk about the virtual function table. In fact, the blogger feels that it is not just the virtual function table. You can talk about the principle of type compatibility, virtual function rewriting, dynamic binding and static binding. Only then can it be fully understood. Including inheritance, when asked about inheritance, we should not only talk about the inheritance characteristics of the class but also add the inheritance characteristics of the structure and the essence of inheritance (the members of the subclass actually copy the members of the parent class, in fact The principle is very simple)

        What you write on your resume must be something you are very good at. When answering questions, you should expand it. Don’t just be limited to superficial phenomena, go a little deeper.

According to job requirements

        This will take some time temporarily. No special preparation is required, just take a look at it, usually about 1-2 hours.

For example, the other party's job requirements include QT-related or embedded-related. You can watch some blogs or videos first. Find out what's there in advance, you don't need to know it in depth, because it's just for the interview. You can make up for the fare after getting on the bus.

        During the interview, if the interviewer doesn't ask about it, you can guide it yourself. For example: I saw that XXX was mentioned in our recruitment requirements, and I also have some understanding of this aspect, but it is not particularly in-depth. Then Barbara tells you what you know about it.

        If you encounter something you don't know during the interview, don't think about it for a long time. It can be said that I have not studied this before, but XXXX (tell me what I know)

other request

        Just dress modestly and don't look sloppy. Be confident when speaking, so that the interviewer can feel your spirit and energy. For programmers, you must highlight your usual attitude of loving reading and blogging, and taking the initiative to learn.

In any case, the accumulation of knowledge is still very important

select offer

The opinions here may not be particularly correct, and only express personal opinions.

If you can find a development job, be sure to do it. Don't do testing (not saying testing is bad).

If the first job is development, it will be more advantageous if you want to switch to testing and IT training later. If you choose IT training or testing for the first job, it may not be so easy to switch to development later. I personally feel that doing development is the fastest growth for technology, and you will be exposed to more things (only expressing personal opinions).

For salary and development: choose a company that can provide better development space (can be big or small)

For C++ programmers, it is especially not recommended to do client development at the beginning, the development prospect is not high

Internship preparation

I have not experienced a formal internship here, although I have an offer and I have confirmed my entry. But the agreed entry time has not yet come. So here, I will talk about my requirements for myself after entering the job. (This paragraph is written for myself)

1. First review the knowledge you are not familiar with and related to your future work

2. Be mentally prepared (the traits that the company that is about to enter most expects interns to possess)

3. For tasks assigned by superiors, you should ask in advance about the specific completion time

4. Learn to express yourself actively, this is fatal for slow-burning people like bloggers. Harm, evil can constantly remind myself to express myself actively.

5. There must be work in your eyes, when you are sitting on the bench. Take the initiative to ask what can be done

6. Be humble, make humility the norm (not Versailles)

7. Praise and socialize for parallel social interaction

8. Be very clear about your own shortcomings at this stage, and make up for them in a timely manner

If you don't like XXXXX, don't spray it. If you have any supplements or suggestions, it is convenient to leave a message in the comment area below

Through this method, the blogger interviewed 7 companies and got 5 offers... Finally, he chose a company that the blogger thought was good.

The individual is not good enough and the education is relatively ordinary, and the big factories are basically useless. I am very satisfied to finally be able to enter a medium-sized enterprise (C++ development internship network security direction). I hope that I can pass the internship in sequence and stay in the company for a long time afterwards, and continue to shine

Guess you like

Origin blog.csdn.net/weixin_46120107/article/details/127041617