Click on the top of the blue word to follow me, knowledge will give you power

In this series, let’s talk about interviews.

As an interviewer, I have to find work, also interviewed by others, as an interviewer, I interviewed a lot of people, also believe that these two years, a lot of people have such complaints, less and less mobile developers, a position for half a year are often can’t find a suitable candidate, investigate its reason, what is it?

In this series, we are going to talk about interviews and job interviews. This is the first part of this series. Let’s take a look at how we interview from the interviewer’s point of view.

Interviews and interviews

First of all, the interview is a two-way process, when you are in the interview others, actually you’re also in the interview, how to say, in general, the team at the time of hiring, will let some of the more senior members as the interviewer, the interviewer when communicate with the interviewer, actually can probably know each other a technical level, communication ability, etc., For the interviewer, the level of the interviewer, almost represents the level of the team, if lost in front of the interviewer, the probability of the team is also more humiliating, so, before two-way selection, everyone is equal.

Therefore, the interviewer’s self-cultivation is very important, which is the face of a team, so our team needs to recruit what kind of people?

First, the interviewer should keep in mind that you are recruiting, not recruiting.

People have flaws, in other words, perfect developers won’t be on your team. So, hiring team before, need to have a look at team, our team will recruit people, what is a person, ability to need to how much, is just to work, still need to acquire, is very potential, is already very senior, is on the business development omniscient, or have a depth study on technology, after understanding these factors, then go to the interview, We don’t need the perfect candidate, we need the most suitable candidate.

Second, interviewers should raise the level of questioning, because there is a good chance that your questions will turn the candidate against you.

The first element is to avoid asking “Eight-part prose”. There are several ways of writing anise in anise beans. Questions like this don’t make sense. Everyone’s knowledge is not complete, and it is possible to encounter blind spots or forgotten places. These questions should be changed to more in-depth questions.

  • How do you typically implement singletons?

  • Does this implementation have thread safety in mind?

  • If lazy singletons must be used, how can they be thread-safe?

  • I have this usage scenario, how do you design a singleton pattern?

Try to ask progressive questions to get the interviewer thinking step by step. Most of the time, the interviewer is not looking for an answer, but to hear how the interviewer is thinking.

A cow weighs 800 kg. A bridge can bear 700 kg. How do you cross the bridge?

I mean, that’s a pretty confusing question. What is it?

Think about it calmly, the result is not important, the interviewer wants you to think about the process, what would you say?

  • First of all, let’s understand the specific requirements of cattle crossing the bridge. Do we need live cows or dead cows to cross the bridge? Are you going to eat beef, or are you just doing nothing and hurting your balls?

  • If it can be a dead cow or beef, then it is easy to deal with. It can be decomposed and transported. Or, can we find a replacement cow across the bridge?

  • If it is live cattle, then the problem now is 800kg and 700kg, either compressed cattle or reinforced Bridges

  • So for those two things, we can think about how to reduce the weight of the cow, like a hot air balloon? Let the cow lose some weight? Invent quantum transport channels?

  • As for the bridge, we can consider whether to temporarily strengthen the bridge, or build a new bridge?

  • The rest of the content is nothing more than meeting minutes, scheme review, project approval, development, launch, summary.

Dubious! Isn’t that what we talk to product managers about? It seems that this interviewer has a lot of trouble with the product manager.

Between the lines

The interviewer’s questions are often very purposeful, and it’s better to read between the lines and hit the nail on the head than to give a long, rambling answer.

This is test the interviewer’s emotional intelligence, you know, a lot of the implication, it is known as the implication, that’s really it is not too can be understood, not looks like, the good luck body is in the mountain, a lot of times, the interviewer feel he had the problem of the implication point very clear that the interviewer still don’t know what is the meaning with a clueless look on his face, There may be questions from the interviewer, there may be questions from the interviewer, but it’s a two-way process.

For example, you have a functional module that is old code from a former colleague, and now you have a new requirement to develop on this basis. Tell me your development idea.

It may seem like a silly question, but if you think about it, we can pick up a few key words:

  • Old code: Don’t ask, this is the pit, dangerous pit

  • New requirements: may launch tomorrow, urgent, online, etc

❝

Insert an advertisement, China Literature Group – Qidian Reading project team (Shanghai) urgently looking for iOS development, you know

❞

So, is the interviewer trying to see how the candidate handles this situation?

  • For this kind of problem, I usually come up with refactoring, garbage old code, is a piece of shit, old man writing code, is a shuttle, garbage all have to kill

What will an interviewer think when they hear that? Oh my god, this is the rhythm of P0 accident ah, although the old old code, but the line ran N year not out of the pot, to a new demand, direct all reconstruction, this risk, not controllable, and the interviewer to solve the problem is not clear, no priorities, even if the technology is very cow force, as the interviewer, will also worrying.

  • First of all, I will clear up the logic of this part of the code

  • Then see if the new requirements can be completed based on the old code

  • If you can, prioritize the requirements and then make a recommendation to the team to refactor that piece of code appropriately

  • If it cannot be completed, the team Leader needs to explain the reason clearly and strive for more resources to complete the requirement

Just what I wanted.

❝

The interviewer didn’t read between the lines, don’t blame the interviewer, after all Chinese extensive and profound, the interviewer is likely to be standing in the look up their position, so some obscure is also normal, an experienced job seekers, the best thing to do is to ask questions at this time, induced by the interviewer to specific problem, let the implication, casual surfaced.

❞

The more senior you are, the more you should think carefully before you answer, because the more senior the interviewer is, the implication may be more profound.

luck

It must be said that luck is part of strength, but strength is not so important against absolute luck.

The process of the interview is really a lucky, met the interviewer lovers more than half sentence, this is the luck, vacancies in half a year, now hiring, so to reduce some of the requirements, this is the luck, the content of the interview was done, yes, this is also luck, but sometimes you interview, may not be your own problem, is likely to be the problem of luck, or that sentence, two-way choice.

I would like to recommend my website _xuyishisheng. Top /_ click the original one key direct

Focus on Android-Kotlin-Flutter welcome to visit

Phase to recommend

  • Wing pass 2.0

  • Gossip – Issue 3

  • Material Components Tour — MaterialButton

  • Google Dig a hole for later generations -ViewBinding(1)

This article original public account: Qunyingchuan **, authorized reprint please contact wechat (Tomcat_xu)****, authorized, please reprint 24 hours after the original publication. **

< END >

Author: Xu Yisheng

Wing preach

Qunyingchuan focuses on Android, Kotlin and Flutter development technology, and also provides internal promotion and interview sharing for developers

166 original content

The public,

More text is not easy, point “three even” support 👇

This article uses the article synchronization assistant to synchronize