Hello, everyone, my name is Qixi.
Recently, I took this opportunity to share with you my experience in resumes, delivery strategies and interviews.
Let me introduce myself first. My own resume is quite ordinary. I graduated from an ordinary undergraduate degree and went to a small factory after graduation. Three months later, I was laid off due to the cold winter.
Starting with such a disadvantage, it took two and a half years to successfully enter a large factory. During this period, I was abused by large, medium and small companies. Fortunately, I gained some experience.
I will tell you my effective preparation methods, skills and points of attention. In fact, these contents are common to both large and small factories.
This article has a total of 6k+ words, I hope it will be helpful to everyone.
Now, I will start to talk about the first piece of content - resume. Here I assume that everyone has written this thing, so here are mainly 7 small suggestions.
It is recommended that you choose a simpler template, not too fancy. As long as you can let HR and the interviewer know your key information clearly and quickly, it is enough to be too fancy and easy to distract others.
Resume must use PDF, do not use word document. Because different computers are prone to style problems when viewing word documents
The question of whether or not to post photos should be a common question for students who are just preparing to enter the workplace. For technical posts, photos are generally not posted. Of course, handsome guys and beauties please feel free.
Regarding the format of the file name of the resume, I personally am like this - name_education_post_mobile number.
Frankly speaking, although this is about to be rotten, so far, I have come to the friends who have come to my internal push, and some people have written the file name quite casually. ), this bracket 1 is a bit showy, too careless.
When it comes to this, some friends may think, I graduated from a famous school, would it be too much of a loss to just write a degree.
Here I'd say -- it's a little bit, and if that's the case, you can confidently write 985 or 211. If you are a famous school such as Tsinghua and Peking University, you can write the name of the school. This is your advantage, and you can be confident.
If your education is not very good and you have a certain number of years of work, you can also replace the position of education with your years of work.
1.5 Professional skills
Describe the professional skills, if you have only read a few articles, you can write to understand. Then there is familiarity and mastery, and finally mastery.
After that, my advice is to rewrite mastery with caution. It is not recommended to write unless it is really researched.
The reason is easy to understand. It is to write about the proficient skills. Unless this professional skill is not used at all in the company you are interviewing for, it must be a place to "take care" of you during the interview (well, the care here is in double quotation marks). So if you can't answer, or don't answer very well, it might be a little embarrassing.
1.6 Professional terms
Professional terms must be written correctly, such as MySQL, pay attention to capitalization, if you are really unsure, you can go to their official website, and then we will know the correct way to write it.
Although this writing is correct or wrong, it does not affect our grasp of this knowledge at all, but from the people I have contacted, some people think it does not matter, but some people will care about it. That being the case, we don't need to try to step on this thunder.
Anyway, there is no harm in writing the correct term, and there may be harm in writing it wrong, so there is no need to bet on whether this thunder is a dumb thunder.
1.7 Work experience and project experience
This is the last point, and in my opinion the most important part of a resume.
From the resumes I have contacted, many people will write some large and comprehensive descriptions of their work experience.
What "big and complete" description? For example: Participate in the daily development of xxx products and online problem handling, be responsible for the development and maintenance of xxx systems, and realize xx functions.
Just here, have you noticed that these contents generally appear in your project experience, so is it repeated here?
Therefore, I personally suggest that if your resume has enough space, the above content can be omitted.
We all know that our resumes are generally 1-2 pages, and for the sake of beauty, it is best that the content can just fill these 1-2 pages.
Therefore, if the large and comprehensive descriptions above can just be filled up without writing them, but it will take an extra page to write them, then in this case, there is no need to write them.
Going a step further, I also recommend that you write new resume content instead of repeating content.
As far as I am concerned, the work experience space in the resume is very small. I only write the company name, industry, tenure, and position. A company occupies 1 line of content, 2 or 3 lines are done, leaving more space for project experience.
For project experience, this piece of my resume is composed of the following 4 parts. They are: project name, project description, technology involved and responsible content.
If you write it like this, you must review the technology stack in the technology involved. After all, what you write there is actually telling the interviewer - you can ask me about these technical points, I have used them all.
This part of how to write responsible content should be the most bald part.
Some people on the Internet say that the star rule is used to describe it, that is, in the background of xx, what is your mission, and finally achieve the effect of xx through the xx method. In fact, everyone has the same idea. I feel that there is too much content to write in this way, and it takes up too much space on the resume, so I refined it.
I organized this part with the following structure - using the xx + yy technique to achieve the xx effect .
This effect is best supported by data. If not, then see if you can describe it in some professional terms, such as: flow peak clipping, stability, idempotency, etc.
After all, the interviewer doesn't know what business we do. If we only write about the function, the interviewer doesn't necessarily know what questions to ask us.
So think about it from another perspective, use technical points + data (if any) + technical terms to give the interviewer some opportunities to ask questions, and also reflect the technical value of what we do.
In addition, if there is no such thing as data, there is no need to force it . After all, there is no way to make it up, and some technical content does not have data. For example, distributed locks are used to prevent repeated processing. What data comparison do you say it has? Well, isn't it.
For scenarios that can be measured with data, we only hope that data will be better.
So when you usually do optimization, remember to record the data comparison before and after optimization. After all, if you want to see if optimization is useful, there must be a before-and-after comparison.
Therefore, I hope that everyone has encountered a scene that can have data quantification, don't miss it. Even if you don't change jobs, you can still use it when writing promotion materials in the future.
So here, I understand the truth, how did the data come from? I didn't record it before, what should I do if I missed it?
If this is the case, then you can try to see if some data can be calculated.
Like the data that can be known from the interface design itself, for example, we have optimized the request merging for a high-frequency interface. The program can only process a maximum of 100 requests at a time after merging, while the previous interface had a maximum of 500 QPS.
Then we can say "The xxx function uses the request to merge, from 500QPS to 100 QPS"
Another example: "The xx function uses the strategy pattern and the factory pattern, which improves a certain development efficiency." This improvement in efficiency can actually be evaluated, that is, how many man-days are needed to make this requirement with and without design patterns, which is more intuitive than writing "improve a certain efficiency".
2. Delivery strategy
Okay, I've finished the big content of the resume. Let's talk about the delivery strategy. Here are 3 small strategies to share with you.
2.1 Find the training company first, then the target company
The first one: first find 1 or 2 companies to practice your skills, find out the interview feeling, and then go to the company you want to go to
- Practitioner company: You won’t go even if you get an offer, or you are the bottom of your group of target companies
- Interview feel: Familiarize yourself with self-introduction and interview rhythm, understand what questions are generally asked about your project, strengthen your memory and formal expression of basic principles
2.2 According to personal circumstances, decide which companies to invest in successively
The second: according to personal circumstances, decide which companies to invest in successively.
For example, Byte and a certain factory are my target companies, but my algorithm is not good, then if I go to a company that requires an algorithm such as Nian Byte, the possibility of overturning is relatively high.
In order to save energy, you can put the bytes later and then invest, and go to those companies that do not take the algorithm or the exam is not difficult, so that the possibility of landing will be higher.
As for which company likes to test what content, this will use everyone's network and search ability. Here comes the third point - if you can push inside, push inside
2.3 If you can push inside, push inside
First of all, internal referral is a win-win thing. If you successfully pass the interview, the internal referral will be rewarded, so you don’t have to worry about letting others internalize you will trouble him, and others are eager for someone to ask him to internalize.
As for the benefits of internal push, it is possible to help with progress and feedback results.
Based on my current understanding, for junior high school senior positions, basically what headhunters can do, we can also do the same with internal referrals.
If it is a more advanced position, such as a supervisor, then this is my knowledge blind spot, and I dare not say more.
In addition to the benefits mentioned above, we can also ask the internal pusher how the department's atmosphere/business is, how the leader is, and what are the common tests for interviews. Sometimes you don't even have to ask, the person who helped you with the referral will take the initiative to tell you what to prepare, or how the overtime work of a certain department.
Many people are concerned about the atmosphere of the company/department they are investing in. I myself will ask people about this, or go to the pulse and look at the reviews online. However, the information of small factories is very likely to be very small, or even no information. After all, there are not many people, and even fewer will come out to speak.
Finally, if you don't know anyone at this company, but you want to find someone to recommend. Then you can go to some job search software, such as boss, pull hook, Maimai, etc., or ask your friends if they know anyone.
If you still don't have it, you can go to the recruitment software just mentioned to find a headhunter or hr to help.
Finally, for internships and school recruiting students, it is recommended to go to Niu Ke or Maimai to find people for internal referrals.
Ok, let's talk about the last big point - the interview.
The first is self-introduction, which I personally think is about 1-2 minutes, but if you are looking for internships and school recruitment, you can’t write much, so in this case, you can choose according to your own situation.
Before the interview, please be sure to familiarize yourself with your self-introduction. Practice speaking several times in the state of the interview. It is useless to think in your head.
Don't hesitate to speak clearly during the interview, this will really affect your impression score.
In addition, it will happen that the self-introduction is interrupted. Don’t panic. When I met the director of a large factory, I was interrupted 3 times because of the interview environment, so this situation requires more familiarity with my own. introduced myself.
3.2 Technical aspects
Regarding the technical aspect, whether you go to a small factory or a large factory, you need to focus on preparing for the basics and projects . Basically, you will be asked in every round of interviews.
Medium and large factories have at least 3 technical rounds, and there will be more high-level positions.
In the last round, managers such as directors usually come and ask different questions. From my experience, the content of being asked includes technology, project, business and life chat.
The first two rounds will ask about basic principles (the so-called eight-legged essay), project and scene design. If there is an examination algorithm, then you will definitely be asked to write here.
If you are in a face-to-face management position, you will naturally ask less about the basics and more about business, team management, or life.
Here are some tips and suggestions to share with you. You can refer to the following, and you can implement them according to your own situation:
The first one, I just talked about the algorithm. As for the algorithm, everyone knows to go to leetcode to brush the questions. If you have limited time, I personally recommend that you only brush the sword offer and the top 100 popular questions. There are more than 100 questions in total.
It's not over yet, the next step is to learn to give up. Because time is limited, what we need to pursue is efficiency, and the more topics that are more likely to be investigated in the shorter the time . so
- hard 难度可以忽略 - 解法只能用数学公式解决的忽略 - 题解代码量很多的忽略 - 看了好几遍题解都不知道在说什么的忽略
To emphasize again, the above are all for interviews, time-limited coping methods.
If you have enough time, in addition to the sword offers and the top 100 popular, you can choose what type of questions you need to practice to brush selectively. There are tags and categories on the leetcode, which is very convenient.
3.2.2 Scenario Design
The second one is about scene design. First of all, it should be clear that scenario design does not necessarily have the best answer, because talking about design out of business scenarios is a hooligan. The main purpose here is to examine our ability to solve problems .
When everyone is asked, don't think about coming up with the perfect plan all at once. It's unrealistic and time doesn't allow it.
If you were the interviewer, and you just looked at the candidate for 1 or 2 minutes without saying a word, what would you think? Especially on the phone face, when others can't see your face, it's even more difficult to judge.
So my personal suggestion, you can think about it first, give an imperfect plan first, and then say to the interviewer: "I just thought about doing this, but time is limited, there may be some unreasonable places. Then blablabla will Said the plan.”
The back is the PK between you and the interviewer back and forth, and the originally imperfect plan is naturally improved in this process. Finish first, then perfect .
Of course, coming up with a solution is a good result. There is also a time when you can't think of it, or when there are multiple implementations but you don't know which one to choose.
In this case, my suggestion is to think about as much as you want, and it doesn't matter even if only some functions are implemented.
After finishing speaking, if you don't know it, you can tell the interviewer frankly, "There is still part xx, because I haven't thought of the place xx, can you give me some hints?" Don't pretend to understand.
The same is true of not knowing which option to choose, so speak up and include the reasons for your difficulty in choosing.
As for the preparation of this piece of content, on the one hand, it comes from the accumulation in your usual work, and on the other hand, you can take a look at the facebook on the Internet.
The requirements for school admissions will not be too high, and some companies will not even ask, mainly for social recruiting students who need to pay attention.
As I have encountered myself:
- How to design a short-chain service
- How to design the dynamic, such as WeChat Moments or Weibo
- How to design a spike
- In a high-traffic scenario, the service can't support it, how can it be optimized?
- How to design the RPC system and what are the key points
In the same sentence, focus on the ability to solve problems, and it doesn’t matter if the plan is not the most correct.
After all, how can I possibly know how WeChat Moments are designed? If I can understand what other people do as a team just by looking at the product functions, it will be heaven.
3.2.3 Encountering questions that you do not understand/unsure about
The third tip is what to do when we are asked questions that we do not understand or are uncertain about.
If it is not clear, you can ask the interviewer to repeat it;
If you don't know what the interviewer is asking, I usually ask him back and make sure he wants to hear about xx.
For example, the interviewer asked about the principle of the thread pool. This can be said about the meaning and rational use of construction parameters, how to reuse threads, and the handling of exceptions in the thread pool. A lot can be said, time does not allow.
At this time, you can ask him, "I'm sorry, do you mean thread reuse this piece of content, or xxx content". In short, it is necessary to clarify the question, give the interviewer multiple choice questions, and narrow the scope of the question.
Of course, don't mention this option if you don't know how.
After that, we can detour a little bit about the knowledge points we don’t understand, and try not to say no directly, which will just lie down.
We can say "I don't know much about this, but I guess it's like this, blabla", or "I don't know much about xxx, but I know yyy is similar to it, and it can also serve the purpose of zzz"
Save it like this, maybe the interviewer will follow the new things you just said and ask you, and this is the content you are familiar with, isn't it delicious?
ok, the 3 skills are finished, and the remaining key play is the project. There are 2 points that I hope everyone can prepare in advance, which are high-frequency problems.
- What are the difficulties or highlights of sorting out your own projects?
- In the project, why use xx technical points, can you use yy ones? Or why is it designed this way?
Regarding the first point, even if the interviewer did not ask, we can express it in the self-introduction
If you feel that your project is really nothing great, it is the curd of the business. Then pick an optimization worth talking about, or a design solution.
After all, only a few people have access to high-level things, and they all understand it.
Next on the second point, this is a question I get asked a lot to see if the understanding of my project is really what it is, or if I'm just a ruthless curd machine.
By convention, when the interview is over, the interviewer usually asks if we have any more questions.
I don't know what questions everyone has prepared, but I will have the following answers myself. This is for reference only according to your own situation, and it will definitely vary with experience and interview situation .
- If jd didn't write the department or business, I would ask what kind of business this position does and how many people in the team.
- Just from the interview just now, what do you think I need to strengthen?
- How is the team atmosphere? What time do you usually commute to get off work?
- No more, thank you (dog head save your life)
3.2.6 Problems you don’t understand should be solved
Finally, let me add that if you encounter a question that you don’t understand or answer poorly during the interview, remember to understand it after the interview. What if you are asked repeatedly in the next interview? I have had this experience myself.
3.3 hr face
If the technical aspects are passed, and finally to the hr interview, it is basically to talk about life, the other company's situation and salary.
In terms of salary, the industry generally has a card increase of 30%.
But this is not absolute, especially for friends with low bases, if your salary in this company can’t reach the lower limit of the other party even if it increases by 30%, then there is no need to aggrieve yourself, just raise it according to the salary level of the other company .
If you feel that the other party is not enough, and you have other offers. Then you can say that you already have other offers, the other party gave xxx, but you want to come to your company, and hope that the salary can be given to yyy.
In addition, if this company is one of your target companies, please also pay attention to things related to your own interests. For example: the company's salary structure, commute and lunch break time, provident fund basis and ratio, etc.
The above are some basic information. If you have multiple offers, these are the basis for your choice. For things that float like year-end bonuses, remember to look at the minimum level, not the average level.
Because we need to manage our own psychological expectations, otherwise, if you accept an offer, you will not get so much by then, which will greatly affect your mentality.
4. The last nagging
Whether the interview is successful or not is actually strength + luck.
For example, whether the company has opened hc, whether the interviewer was in a good mood on the day of the interview, and whether the questions asked were just prepared by himself.
These are all luck and we can't change them. The only thing we can change is strength. The higher the strength, the lower the influence of luck.
Finally, I hope everyone can successfully get their ideal offer, thank you.
"This article participated in the SegmentFault Sifu essay " How to "anti-kill" the interviewer? ", you are welcome to join. "