The interview, which is a headache for most students, can be either successful in getting into the desired company or frustrating in passing. But wouldn’t it be great to know what the interviewer is going to ask you before the interview so you can prepare for it?
Previously, the community helped us summarize the recruitment needs of 15 heavyweight companies and updated the recruitment post in the community, which also received a lot of feedback from students:
“** I sent a lot of resumes, but I didn’t get an interview **” “** The interviewer said he wanted to recruit high-level talents **” “** Ah, I feel like I have a short graduation year, the company is a small company, and the undergraduate degree is not good, so it is difficult to find a job **”
Finally, I can only conclude:
“I’m not good. I don’t even get an interview.”
It’s too south-to-south!
So how on earth to accumulate technical strength, become a senior developer of Flink, and win the offer of the desired company? Squirrel enlisted the core appeal of Flink’s hiring executives and provided a super clear, practical learning path. While none of us can read minds, there are ways to solve difficult interview problems!
** Flink 2020 Latest recruitment information please see the link below, internal promotion or recruitment needs of the company can contact The squirrel (wechat ID:Ververica2019) post JD ~
New Flink job openings for 2020: juejin.cn/post/684490…
Know your supervisor’s needs
When collecting recruitment information, Little Squirrel learned the core needs of the hiring manager and the feelings of some students after the interview, which can be summarized into the following aspects:
- Less experience, lack of experience in complex scenes
- I am using Flink to do data development, but I have no experience in low-level modification
- I want to recruit more advanced students who have in-depth research on the bottom of Flink, but it is difficult to find advanced students
- Those who need in-depth research and transformation experience are also allowed to independently complete problem solving and task tuning
Pay attention to the keywords! “Complex scene experience”, “low-level modification experience”, “advanced”, “problem investigation and tuning”, these are the expectations of Flink development students in most posts, which is equivalent to highlighting! In addition to understanding the core needs of the hiring manager, we also need to combine our own basis to find the right position direction.
02 Find the right job
The little Squirrel summarized most of the recruitment content in the market, and analyzed and integrated these positions, as shown in the table below. Generally, it can be divided into three directions:
As we all know, platform development or underlying engine development need to have the spirit of Flink research, need to continue to focus on deep cultivation, technical depth, technical principle master and even source code ability requirements are higher.
Relatively speaking, the development of business classes is more concerned with specific application scenarios, mostly based on the platform for business scenarios application development, the underlying, source code requirements are relatively low.
In general, no matter which technical direction you choose, solid language skills will be the foundation, while contributions to the open source community and in-depth understanding of Flink ecology will be a plus for Blingbling.
What skills should be mastered from xiaobai to Flink advanced development?
If you understand the differences between your core needs and those of your supervisor, or have a preference for the direction of your job, then you have successfully completed your psychological construction. The third part, little squirrel invited Apache Flink PMC Cheng Hequn (military commander) to help you solve the “from small white to Flink advanced development, should master what technology?” For this core issue, I would like to thank Apache Flink PMC Wu for your feedback and suggestions.
First, an X-mind for you! Public account background reply keyword “interview”, you can download PDF version ~
Then, we’ll learn what this mind map is made of and how to use it.
1. Dictatorship has no way to start
According to the recruitment requirements of Flink, we will focus on the following parts:
- Basic theory of big data
- SQL & Table
- Runtime
- Flink ecological
- Flink of actual combat
It integrates most knowledge points involved in the current Flink job interview and divides them into five sections. In addition to SQL & Table, Runtime and other core content, ecology and actual practice is the interview needs to focus on the content.
2. A mind map without questions is not a good question bank
- Starting with questions, each piece of content provides a review of potential knowledge points in the form of a question.
- Not only Flink, but also mind mapping for the interview may be involved in the basic theory of data organized into questions for your reference.
- Flink ecology and actual practice are not only the focus but also most of the difficulties. The corresponding parts of the brain map are also marked with smiley faces, so the difficulty level is clear at a glance.
Hope this mind map helps! You can use the Flink knowledge map to learn better
Flink Community Knowledge Map: ververica.cn/developers/…
I talked with 5 dachang students and they shared 10 real questions
The interview is similar to the large and small exams we have experienced since childhood. Although we can cram at the last minute, the most important thing is technical strength. Here are 10 real questions, all from dachang students with rich experience in production environment, hoping to help you in your interview. Here we thank five students!
BTW, the following real question is only for your reference, develop ideas, must not put the cart before the horse, the real question as the only magic weapon for interview preparation.
Set of real questions
1. Explain how Flink handles backpressure, and what is the difference between the backpressure mechanism provided by Storm and Spark Streaming?
2. Explain the three data processing semantics provided by the flow processing engine, explain how the Flink Checkpoint mechanism guarantees the Exactly-Once semantics of the results of the Flink program, and describe how the two – phase commit protocol provides the end-to-end Exactly-Once guarantee. How to build end-to-end exact-once processing with Kafka?
3. Explain the fault tolerance mechanism provided by Flink, explain the logic of distributed snapshot Chandy Lamport algorithm, and analyze the implementation process of Flink Checkpoint.
4. How to solve the problem that Flink jobs restart frequently?
5. How to optimize large-state Flink operations?
6. How do I check the Flink Checkpoint timeout problem?
7. How to deal with data skew in Flink operation?
8.Flink backpressure mechanism, how to check where the backpressure bottleneck is and how to deal with the backpressure problem?
9. What kind of join can ensure the correct join to data even when a single stream is interrupted?
10. How was watermark created and transmitted?
The above. Our goal is to “learn Flink well and find a job easily”. Whether you are an interviewer who wants to help with internal promotion or an employer who wants to recruit, please contact Xiaosquirrel (wechat ID:Ververica2019).
Click the link below to view the latest recruitment information in the 2020 community ~ juejin.cn/post/684490…