Focus on front end early chat and follow up 30 world conference | front-end chat early special BFF (GraphQL, unified gateway, API access management, large scale cluster, protocol conversion, security section, high concurrency, visualize, construction layout, unified stability…) 8-14 all day live, 9 lecturers, click to register for live 👉) :
Front end early chat conference, co-hosted with nuggets. Add Codingdreamer into the conference technology group, win in the new starting line, all the past have full recording, one time to unlock all the old year ticket
Introduction:
My name is Chen Shanjie. Ant Experience Technology Department is recruiting interns for class 2022. I started sending out resumes in December last year, and was rejected five times by a unicorn factory before receiving offers from Ant and Tencent. At the end of the interview, I was very confused. I was lucky enough to learn about the early talk conference, and gained a lot after paying attention to it. Finally, I successfully passed the interview of Ant and Tencent, and ants came. Thank you very much to Scott, the initiator of the Early Talk Conference, for inviting me to write an article about my experience to help more people, especially graduates.
Everyone’s interview experience is different, and it can be smooth or rough. I hope to share my relatively bumpy experience with you, if IN my past interview on the road, there have been such a reference, may be less detours. Although the experience can not be duplicated, but I will try to dig out the common things, hoping to give you a little inspiration.
background
To get into an interview, you first have to go through a resume screening process. Resume screening is all about the basics on your resume — education, internships, projects, skills.
Education experience
We don’t have much room for improvement unless we go to a better school. For the school recruitment, what we can do is to learn their professional courses well, so that some good grades. Write down the courses that you are good at and can withstand questions. For example, WHAT I wrote is: operating system, data structure and algorithm, computer network, cryptography, Linux, which will be asked about in the interview. Although the probability is not certain, but can say when asked, can be an advantage.
My school is relatively ordinary, wenzhou Kean University, a school in Wenzhou, Zhejiang province. Not 985, not 211, not provincial priority. So here, students of Shuangfei can have more confidence in themselves, and Shuangfei is not out of luck with Dafang. Although companies prefer students from good schools, technical posts are ultimately about technology. Good schools can endorse for us, for us to prove that our foundation is not bad. If schools can’t endorse us, we have to prove to businesses that we have the capabilities they need.
Internship and project experience
Internships and project experience can be a great complement if the degree isn’t particularly impressive. Tech jobs are ultimately about technology, and even if you have a good degree but haven’t written a few lines of code, you’ll still fail the interview process.
In an internship or project experience, we are often exposed to more comprehensive things, so the interviewer will have the opportunity to ask more questions from a variety of aspects. And these are the things that we’ve actually done to show the interviewer what we know more fully.
skills
HR does not necessarily understand technology, and it is safest to communicate skills to JD. Even if you don’t know the technical terms we mentioned, you can still make a good match for the keywords. JD, the same position is basically the same, more than a few, their own induction and sorting out the line.
Here’s what I wrote:
- I am familiar with HTML, CSS, JavaScript(including ES6), wechat small program development, working principle of browser, MVVM framework such as Vue and React, UI framework such as Vuetify, and front-end engineering tools such as Webpack.
- Proficient in Python(crawler, data analysis), Golang(back-end development), understanding of NodeJS, Java.
- Be familiar with SQL databases such as MySQL and PostgreSQL, and NoSQL databases such as Redis and MongoDB.
- Familiar with computer network, HTTP protocol, security, etc., with computer intermediate professional technical qualification (network engineer) certificate.
- Good command of English, able to use English as working language and read English documents.
Be realistic. I wasn’t familiar with frameworks at the time, so I just wrote an understanding. For interns, big factories actually pay more attention to the foundation, if the framework is not used, it will not ask. There is no need to puffy face to be fat, unused to write used, unfamiliar to write familiar, familiar to write proficient. If you want to write like that, you will probably be taught how to be a man by the interviewer.
The resume is like you give the interviewer to test your exam outline, although the interviewer may not refer to, but must not be their own pit.
Preparation and Failure
I had four interviews with a unicorn company, three to two, and the last to three.
I chose a relatively straightforward approach that most people would not take – an interview to check my progress. Many people don’t dare to go for an interview before they are fully prepared. But take a step back. How do you know if you’re ready until you’ve met first? Although there are a lot of interviews online can see, but there are still differences with the real interview, such as will be nervous, nervous when you can answer the same question?
Because a unicorn factory is always recruiting interns, and there is no cooling off period, you can always invest. So I prepared and interviewed, and I had so many interviews. Of course, I don’t encourage people to try it out when they’re completely unprepared. It’s ok to vote again and again, but every interview will be recorded. Because I can get to the second interview every time, the feedback of the interviewer is ok, let me feel so “billion points”, so I try again and again.
If you want to test your preparation progress through the interview, and you are afraid of leaving a bad interview record, you can first choose a few big factories that you don’t particularly want to go to, or some small and medium-sized factories that are harmless to try, test your preparation progress and accumulate experience.
Stage 1: Face to face preparation
In the first interview, my friends helped me send my resume to the leader of a group of front-end infrastructure of the factory whom I knew.
Since this is my first interview, my first interview in a big factory, and my first time in front of the audience, I don’t have any experience and ideas. When I received the interview invitation, I thought I didn’t know how long I would review, so I went first. I made the interview about the day after tomorrow, leaving more than a day for myself. Over the course of the day, I went through the basics of the front end.
The first interview felt quite magical, the interviewer’s first question actually started from the operating system, I also asked one at that time, isn’t this front end? Now that I think about it, IT seems that THIS is the first interview I was asked about operating system, and I haven’t come across it in other factories. We also asked some classic questions about event loops, CSS horizontal and vertical center, and array beat flat. Although the answer was not very good, but the interviewer said that the overall good, but also said that wait for ten minutes, the next interviewer will come right away. (I also know the efficiency of the interview from this time. It is said that you can finish the interview in one day if you are fast.)
The second interview asked some questions about the understanding of the separation of front and back ends, the difference between Vue and React, Vue two-way data binding, value transmission between components, life cycle and so on. When I was writing small programs before, I felt that template syntax was quite similar to Vue, and there was also the concept of life cycle, so when the interviewer asked me whether I had used Vue, I said yes. The fact proved that I too dish, Vue and small procedures are completely two things, so these questions directly give me the whole meng. Because of this experience, I never mentioned the framework of “Vue” in the subsequent interviews. I only asked again to understand it and never used it.
Not surprisingly, I failed my first interview. If you don’t hang up, it’s not scientific, after all, it’s just a day of preparation, if this can pass, how can other people face.
The second interview was an internal push found on the cow. I felt good in the first interview and I thought I could make it if I tried harder. So when I received the interview invitation, I arranged the interview for a week later and left a week for preparation.
For the second interview, although I felt a little prepared, IT was only when I was asked that I realized how much I didn’t prepare. One side asked a series of CSS related questions, including CSS draw a triangle, draw a square and so on. This interview is still a little flustered, very simple box model did not answer well, but the interviewer still put me into the second interview. At the end of the second interview, I was asked about a “maximum sum of continuous subarrays”, but I practiced too little to write it out. The interviewer gave me another chance to ask how to implement sleep through Promise, but I didn’t think of using setTimeout to resolve Promise. The interviewer asked two people to flip a coin in turn. One of them would flip the coin first, and the one who got heads first would win.
Just like that, the second interview failed again. After I failed this time, I began to realize how little I had prepared. I decided to expand the scope, the cattle on the factory before a few pages of the face by all the point open, all the topics sorted down, one by one understand; Start brush LeetCode, tree and list of high frequency questions have gone through; Start writing common handwritten questions, such as tremble throttling, new/create/instanceof objects, bind/call/apply, Promise, EventEmitter…
In the process of preparation, or every other week through the promotion and website delivery, finally in the year before the fishing up, have the third interview.
The third interview, because expanded the scope, the other people interview out of the questions are basically passed over, so most of the questions can be answered. However, in the second interview, I was asked about the details of setInterval and Promise, but I didn’t answer well, and I didn’t wait until the third interview. I will not have the next interview in a short time. During the New Year, I can prepare well for it.
I will summarize the process of preparing for these three interviews as: face-to-face preparation.
Stage 2: System sorting
In previous interviews, I always asked the interviewer if he or she could give me some feedback at the end of each rhetorical question. The most common feedback I get is that knowledge is not systematic enough.
Spring Festival at home, bought winter teacher “relearning front” column to see. When I started reading this column, it turned out that the entire knowledge system of the front end was like this, and it turned out that many of us didn’t really understand how to learn the front end. After reading Teacher Winter’s column, I began to build my own knowledge system consciously. Although I have sorted out a lot of topics before, I have never sorted out the relationship between knowledge points and prior knowledge points. I started to make a brain map to categorize the knowledge points THAT I could think of that might be asked in the interview, and while I was doing that, I continued to think about the connections between the knowledge points. Because I have accumulated a lot of questions before, after such a structured thinking, many knowledge points began to be sequentially linked, so that when asked again in the interview, it is easy to recall and relate to other relevant knowledge. As an example of the browser caching mechanism, the first thing that comes to mind is how strong cache and negotiated cache are implemented, which headers are used, and what status code is returned when the cache takes effect. Then we can think about what other headers and status codes HTTP has, how to avoid caching requests, the difference between GET and POST, what other methods HTTP has, CDN, HTTP/2… Whenever you see a question, think about how the interviewer may ask, think of the questions together, so that the knowledge can be linked to more and more, more and more will not forget.
It was also at this stage that I began to gradually understand the logic of interview questions from big factories. On the surface, we think, “Build rockets for interviews, screw for jobs.” But in reality, the questions behind the big factory interview are about our body of knowledge and the logic of thinking about questions. The same interview question can be answered at different levels according to the depth of the candidate’s knowledge. If the knowledge system is perfect, knowledge points and knowledge points can be connected, the interviewer can ask a point when answering to other points, gradually to their familiar direction to lead, it is not easy to be dug. Sometimes, the interviewer is not trying to give us a hard time. Maybe the interviewer didn’t think of anything to ask at the time, so they just picked the questions from the bank. Give the interviewer a sense of direction, and the interviewer is looking for highlights in the candidate. Even if the interviewer doesn’t follow up on the points you’ve made, the interviewer will know you have something.
After the Chinese New Year, I was invited for the fourth interview. This time, I got the interview when I got together with my junior high school classmates on Chinese New Year. I learned that a friend of mine had an internship in this factory, and he helped me to be the leader of the front group of their department.
This interview, finally came to the third. The second interview was a bit like the pressure side, with the interviewer saying very little and asking a few questions, the last one being implementing a scheduler (concurrency control). This topic is quite classic in this factory, interested can search online. I felt a little confused when I wrote it, but I still wrote it by mistake. The interviewer said he was surprised when the interviewer came in and finally got to the third side.
Three should be the head of the department. Maybe it was because the department head was busy. Later that day, HR called and said that the interviewer could not come temporarily, and made an appointment for the next day. Later, HR called again and said that the interviewer was not available these days, so the appointment was next Monday.
By next Monday, finally waiting for the interview. This interview should be the closest I’ve ever been to the factory. At the end of the interview, I felt that I did not have a big mistake. Unfortunately, I did not wait for the news for a few days. Finally, I received a thank-you letter.
After the replay, or can think of the place not done well:
On the technical side, how to tell if a circular reference in an object is not done well.
In terms of non-technical aspects, why did they choose the front end? The internship time is only four months, which may be a little short for them.
Phase 3: Beyond technology
By this stage, the questions that are commonly asked in the interview have been prepared to the best of their ability. After my fourth failed interview, I started to focus on something other than technology. After a chance encounter with front End early, I learned that in addition to looking at technology, interviewers also focus on:
Interest, initiative: Are you really interested in technology? Is it just a book theory, or has it actually been written? Students who are really interested in technology or have strong initiative will write some demo by themselves, whereas interviewers will think that candidates are not interested in technology or initiative enough.
Character: can’t show too strong dual thinking. When we’re kids, we’re all right and wrong, all black and white; As an adult, many things are between black and white. Candidates who are too dualistic tend to take sides at work, which is bad for cooperation among colleagues.
Attitude: Good education means good intelligence. If you have good intelligence but don’t answer the basic questions well, the interviewer will think about whether the candidate has the right attitude and studied hard in school.
…
When we pay attention to these, we will understand why the interview of big factory always ask us to “build rocket”. In recruitment, especially in school recruitment, companies often attach importance to potential on top of foundation. We may have been the P5 when the company hired us, but we were definitely expected to be more than that. The company is willing to hire P5 level us in the hope that we can achieve P6/P7 or even higher in the future. So, we need companies to see our potential. To help companies see their potential, consider the soft skills mentioned above.
At the same time, I’ve come to realize that interviews are also a lot about the right place at the right time. If there are fewer people competing for the position, you may not have to answer all the questions. If there are so many people competing for the position, it may be necessary to answer all the questions perfectly, even more than expected.
Reply disc: took what detour
Detours 1: Prepare for face warp
In my opinion, the first three interviews, which is the stage of preparation for the interview, are time-consuming and bottomless. Because I prepared based on what other people had been asked, and I didn’t know what I was going to be asked. On the surface, it is to prepare for the interview, which is more targeted. In fact, it takes more time, because it can only be prepared according to the full amount of questions. There is no focus. Although the topic finally can understand, but the solid degree is like a building without a good foundation, a tension is easy to fall.
Later, I began to comb systematically and found that my thinking was immediately clear. I knew what I needed to prepare and what I was not prepared for. Later began to see the system of the front-end course, found that read the knowledge sorted out by the big guys, than their fragments from the Internet to see much more efficient. Then he began to read the Little Red Book and read more than 50 pages a day. The little Red Book, which is less than 1,000 pages, can be finished in 20 days if you start reading it.
Therefore, learning or should find the right way, not to rush. Otherwise, a shortcut taken to save time may take more time to walk back.
Detours 2: Why the front end
In the third interview, I failed to answer the question “Why the front end?” At that time, I gave the impression to the interviewer that I didn’t want to be the front end, and being the front end was just a temporary choice. This can be fatal. Career planning is also important, especially in the end and HR. The expectation is that the candidate will be in the field for the long term, not just for the short term.
Detours 3: Base selection
During these interviews, I also received the interview invitation from the Base in Beijing of this factory, but I rejected all of them, because I wanted to base in Shanghai. If you do not have special requirements, you can choose from any base or HC. It’s a very simple logic, the more understaffed the place, the more understaffed the time, the greater the opportunity. The standard is the same, but what if they’re really short of water?
Consider: Why the front end
Why the front end? This is the school admissions in the interview is often asked a question.
I didn’t really choose the front end at first. Before this, I did both the back end and the back end, but I wanted to do the back end more. So when I first went to a unicorn factory, I was doing back-end jobs. But unfortunately, the direct resume is not. I took my resume to consult a friend who was doing the full stack. My friend said that most of the experience on my resume was the experience of the front end (small program), so it might be more suitable for the front end. And now the front and back ends are separated, so the requirements for the front and back ends are higher. The back end needs to know not only the basics (languages, databases, computer networks), but also container technology, message queues, etc. Nowadays, the competition is increasingly fierce, although JD is not written on it, more or less it will still require.
That makes sense to me. Although I am familiar with basic back-end language, database and computer network, DOCker, K8S, RocketMQ and so on have never been touched. It may not be too late to learn it now, and I may not have an intuitive feeling without a certain volume of business. In addition, I did not do the front end before, or did some. So maybe we can start from the front end, advance a big factory, and then have the opportunity to move to the back end, after all, the front end to the back end of the people are everywhere.
During the three months of studying and interviewing, I often asked myself why I chose the front end.
At the beginning, I wanted to choose the back end, because I think, as long as the back end manages the data return and the database to add, delete, change and check accurate, and the front end of the comparative metaphysics, need to solve various compatibility, adaptation problems, so I want to do the back end.
However, having this idea is a sign that I don’t know enough about the front end. Compatibility issues should not be an issue if the front end foundation is solid enough.
My first contact with Web was when I graduated from primary school. I used WordPress and Discuz to set up my own website, and also learned about domain name, DNS, CDN, MySQL, FTP and other knowledge from that time.
When I was in junior high school, I participated in the county web design competition on behalf of my school. Because has been interested in code, so in such a game is bound to play a little. At a time when most people use Frontpage for visual editing, I started with HTML and removed a lot of redundant code brought in by copy-and-paste. The page doesn’t have to be the most gorgeous, but the code does have to be the cleanest. Finally, I also won the first prize.
In my sophomore year, wechat launched small programs. After looking at the document, I feel very fun, so downloaded the developer tools to do a demo to play. At that time, the students around encountered a problem — do not know where the professor’s office, so I wanted to do such a small program, give them to query the professor’s office location. If it is an APP, download it separately; If it’s a web page, you have to go to the browser to open it. And small program, wechat home page to pull down there, is a more convenient entrance. Say do do, learn to sell now use spare time rub about two weeks on the line. After the launch, I found that many students used it, and later it was adopted by the school as an official student service mini program.
From these experiences, although I didn’t explicitly choose the front end, I was more or less always doing things related to the front end.
The reason why I did not choose the front end at the beginning was that “the front end comparative metaphysics needs to solve various compatibility and adaptation problems”. However, isn’t it also a kind of happiness to solve these so-called “metaphysical” problems, make clear the reasons and essence behind them, and find the rules in the “no rules”?
After walking through these detours, I want to tell people later, to be clear about why they choose the front end. Don’t choose the front end because it’s cheaper or faster to get started. Only if you are truly interested and genuinely want to be the front end, can you do more than others and do a good job, so that the interviewer and HR can see your potential.
Restart: The interview is off to a good start
Before has been delivered to a unicorn factory and another reason is that other big factory spring recruitment did not start, only their home is perennial recruitment. And they don’t have a cooling off period, so they can switch departments and try again. Now ali, Tencent and other big factory spring recruit also began. After thinking about the pain, I feel I can not hang dead at one tree, so began to deliver Ali, Tencent and other big factories.
After watching last year’s “Front End Interview” on how interviewers look at candidates, I learned a lot of information THAT I had never heard before. For the first time, I learned about the interviewers’ perspective on candidates, and how to answer the same question that interviewers are interested in. In the follow-up interview, because I know myself and the enemy, SO I am more calm, thinking more clearly, and naturally have a better interview performance.
The most helpful part of this year’s early chat is the 22nd “front end interview”. Since I interviewed the ant Experience technology department, the teacher on the right of this conference shared “how the Ant experience technology Department interviews candidates”, which played a considerable role. Before that, I had no idea what each interview was about. And after seen early talk to share, I learned that the two aspects of the ant experience technology is matching face, look at me and I’m going to the department of compatibility, the interviewer is all I have to enter the department supervisor, mainly inspects the past experiences, checking done projects, to observe my problem solving skills, to participate in the business of participation, familiarity, and so on. With this information, MY mind was clear and I came prepared for the interview. Later in the interview, and bending teacher also had a pleasant exchange, successfully passed the interview.
After this interview, I knew what a “match” was. Although I have heard it before, I have never had a more tangible sense of body. In the interview between Ant and Tencent, I can obviously feel that I can talk well with the interviewer and the interview went well. Maybe it is because of the “match”. In the first few interviews, you may feel that the questions are difficult because you don’t have a good match, or you can’t pass most of them.
There are many reasons for the mismatch, including educational background and technology. Companies are always looking for the best candidates who fit the bill, and if these factors don’t add up to the best of all, they may not be a good match. Understanding the department and identifying with the values of the company are also a match. So when you are looking for a job, you might as well make more efforts to learn more about the business of the department you want to work in. Job hunting is a two-way street, and it’s good for you to know the business of the department you’re joining in advance.
Summary and Suggestions
These are some of the thoughts I’ve been thinking about during my job search in the past few months. Not everyone has the same potholes, but I hope at least you won’t have to step in the ones I’ve stepped in.
And for those of you like me who don’t come from an elite school, don’t be discouraged. Shuangfei students are not without opportunities, many times we miss those opportunities because of information asymmetry. Start early, prepare early, and the stupid bird can fly first.
How “stupid” birds fly first, I put together a few suggestions for you.
Prepare early and eliminate information gaps
In fact, good students are more likely to enter dafa, not only because of the school’s signboard, but also because they often have more information and wider channels around them than we do. On the one hand, they have the experience of many seniors already in Dailang to refer to. On the other hand, enterprises will also take the initiative to go to the school to preach, many students will start to understand from the first two years, the third and fourth years are naturally prepared; Moreover, in such an environment, there will also be many students around dafang together, after the exchange of natural exchange.
There are always some people who ask “does the student have the chance to enter dafang”, and always see some people surprised “The student also has the chance to enter Dafang”. Although my school is not two books, but because it is relatively new, almost no HR has heard of it, so in HR’s eyes, it is a relatively pheasant. Danchang really prefers students who are good at school. But this does not mean that the school is not good enough students, there is no opportunity. Schools are not good enough, we can still make up for our shortcomings in other aspects, such as richer practical experience, deeper understanding of technology… And to do that, you need to start before everyone else. Otherwise, we would have gone through the first three years like everyone else, not necessarily as deep as everyone else; And then when everyone else is preparing for an interview, we start preparing for an interview, and we don’t prepare faster than everyone else, so how do we do it better?
How to prepare early? Start early and read the technical classics. It doesn’t matter what you look at, a lot of knowledge will be shared in the future. Start early on projects, not necessarily for organizations/agencies/mentors, but also for interest projects. Many people don’t start because they don’t have anyone to bring and don’t know what to do. There are plenty of interesting projects on GitHub that don’t necessarily require a mentor. Take the interest project as the actual project to do, also can do very deep. When I see some products or projects, I can also think in my mind about how the project should be made and what technologies should be used in the front end and the back end. If you can think of a plan and try it yourself, no matter what the result is, you will gain a lot in the process. You can start interviewing a little bit earlier. You don’t have to feel like you’re a freshman or a sophomore. People who are better than us can get internships in big factories before they even go to college. Even if you think your level is not up to, you can also go face to face, feel how much you are poor. Even if you don’t go to the interview, look at the job requirements and see what you need to do to prepare.
Be prepared without anxiety
Front-end school recruitment interview questions, scattered to see, we feel a lot. But when it comes to grooming, that’s all it really is. Most of the time, we feel that there are too many questions to finish the preparation, the essence is because we are too hasty. It took me no more than three months to pass the interview from the beginning of preparation. If I spread the preparation to the first two years of college, in fact, I just read a little every day. If you really follow that rhythm to accumulate, the last content will be more, master will be more solid.
Even if, like me, you start a little late, don’t worry too much. The front end is almost the same starting line for everyone because there is no specialized course in the university at present, or even if there is a technology stack, it is relatively outdated. Many non – professional students, half – way monks can also give a quick start. The only difference may be that the students in the subject class have more stamina and run faster after the middle and late periods, because the basic knowledge of some other fields will be involved in going higher. Just to get started, the threshold is not particularly high. In recent years, the demand for the front end has also been expanding, and the opportunity will be greater.
Be curious and ask questions
As mentioned earlier, DACO values our potential and our interest in technology. So as you prepare, ask yourself a few whys. As you solve a problem, see if you can think of other related problems to solve together. In the beginning, preparation may be slow because there is not too much. But later on, as you learn more and more, you learn new things faster and faster.
Why does Dafang attach importance to the foundation? When we encounter problems in daily programming, we are always used to searching the Internet. So how does the first person to come up with a solution find a solution? As engineers move up the ladder, they will eventually encounter problems that have never been encountered before, and solving these problems will depend on those basic, low-level knowledge. When faced with the same problem, the foundation is solid
Pay attention to your resume and write it well
As mentioned earlier, HR didn’t know us at all, and the only way they knew us was through a one-page resume. During the preparation process, I also read some counter examples, some of which were not clear about my experience and skills, and some of which were not clear about typesetting. You should know that the HR of a large company is often very busy, if we do not write down the experience and skills, do not arrange clearly, the HR is not interested in figuring it out for us, the result may be the resume in the trash.
To keep your resume out of the trash, make sure the key information is available at a glance so the HR can be interested in reading it. The expression of experience and skills also needs to be carefully considered. Chinese culture is extensive and profound, and there can be many ways to say the same thing, so how to say it can attract HR’s attention more. As for the layout of how to arrange, what is the law of STAR, there are a lot of information on the Internet, here will not be repeated.
Those students in good schools, they are required by the school, or on their own initiative, often in this area to do the corresponding homework, so it is not easy to step on the pit. If the school is not enough attention, their own did not pay attention to, think casually write a resume can, often planted.
Find the right channel and deliver by push
The resume is written, the experience and skills should have, why the resume is still not the sea? We may also need more efficient delivery methods.
You can see that out of the five interviews I’ve had, three of them were extrapolated. Why do you send by push?
First of all, HR, especially in big factories, receive a lot of resumes. If we want HR to see our experience, we first have to make them want to see it. HR is also an employee. In many cases, because there are too many resumes and they have to read them within a limited time, they have no time to look at the content well, so they have to sift people in batches according to the school. If it is not delivered directly, it may be passed over because it is not good enough. However, through the internal push, HR can still find time to have a look because an internal colleague has looked at it and a preliminary screening has been completed. Even if HR is too busy to remember, you can ask the person in charge to remind you. HR is willing to look at our resume, the resume highlights have a chance to be discovered.
It is a more efficient choice for both HR and candidates to deliver by push-in. For HR, there is less pressure to select candidates from within because they are viewed by colleagues from within. For candidates, HR is more willing to take a second look at their resumes because of endorsement from internal colleagues, which increases the probability of passing the screening. In the follow-up process of recruitment, I can also get more effective feedback through the inner person.
So there’s a lot of ways to look inward. Seniors, niuke, Zhihu, circle of friends, as long as you can contact the corresponding people, it is ok. It’s important to point out that the reason extrapolation works is because you can get in touch with your extrapolator. If you just find a random online push-code, but can not contact the host of the push-code, then the push-code is not much help.
In addition to the unified recruitment of the company, many teams will also take the initiative to recruit, establish some q&A groups, this is interested in the company/department/team homepage to find. Such as the ant experience technology www.yuque.com/afx/about/a… .
Early chat is also a good channel, and many TL will hire people by the way when sharing. In this way, the resume can be directly delivered to the Leader, and the delivery efficiency is higher than that of the general push. If you haven’t seen any interested team on the early chat, you can also talk to Scott privately. Scott often recommends excellent candidates in his circle of friends.
hiring
Now that we’re talking about extrapolation, there is also an extrapolation channel that goes directly to the TL.
I chose Ant, and I chose the experiential Technology department, in large part because of the second interview interviewer, the head bending teacher of our department. There’s A phrase in his Team culture called the A-Team, inspired by jobs:
A team that works for an idea is a group of talented people who get together and clash and argue and argue with each other. It makes a lot of noise, but in the process, they make each other better, they make their ideas better, and the result is these beautiful stones. So a lot of my success has come from finding really talented people. Not B or C level talent, but real A level talent. And I found that when YOU get five of these people together, they love working with each other like they never have before. They will no longer be willing to work with mediocre people, and will only be able to assemble the same good people. – Steve jobs
In A word, “A-level talents seek a-level talents as partners, and B-level talents seek C-level talents as younger brothers”. At present, I have been working as an intern in the technical department for a period of time. I really feel that all the talents in the team are good at speaking.
You will have the opportunity to get involved in a real business, solve practical business needs, and get in touch with frontline development. There are reliable supervisors who encourage efficiency, encourage not to study, and encourage colleagues who finish early to go home early.
We are the data intelligence front end team of the Experience Technology Department of Ant Group, responsible for the construction of products related to ant Big data center and ARTIFICIAL intelligence Center, and committed to maximizing the value of data. There is not only a strong open source culture, such as G2/G6/X6/F2 and other AntV visualization community works, but also the core business of the whole group, such as the data research and development center that is used by ant technology staff, the ARTIFICIAL intelligence center that serves ant’s first-line business, the industry-leading graph analysis platform, and the cutting-edge technology that is both fun and sexy. Such as the end intelligence adopted by pet cameras, intelligent visualization required by the next generation BI, etc.
For resumes, please send them to [email protected].
Stay tuned for the front end chat early, follow up to learn more about BFF/GraphQL, Please pay attention to 30th | front end early chat end interface before and after the conference special BFF – play (GraphQL, unified gateway, API access, API management, protocol conversion, unified security aspect, stability high concurrent processing, visual layout, unified construction…). 8-14 all day live, 9 lecturers, sign up to watch live 👉) :