QQ exchange group 196800191

These days, by lowering recruitment requirements, they attract a lot of applicants! Here are my recruitment requirements:

  • Proficient in componentized architecture, strong understanding of MVP,MVVM,MVC and ROUTER;
  • Good command of Objective-C language, understand the idea of object-oriented programming, have strong design ability;
  • Proficient in APNS, UI layout, database, network and other development technologies;
  • In-depth understanding of objective-C Runtime, RunLoop and other basic principles;
  • Have an in-depth understanding of the methods of improving user experience, performance tuning, crash prevention and traffic saving of the App;
  • Good programming habit, logical, careful, good communication skills, proactive communication awareness;
  • Strong self-study ability, self-drive, strong desire to explore.

RunLoop: 50 iOS interview questions after interviewing 10 developers

When I was young, I respected every prospective friend who came to interview. I don’t bring any questions about my code or project into the interview room!

3 years iOS development experience, computer and science major, previous platform projects: played with INSTANT messaging, have a certain understanding of the bottom! I was so pleased that I arranged an interview with him at 10:30 the next morning.

I went to work at 10 o ‘clock and arrived at the company around 9 o ‘clock to prepare for the interview (because I wanted to show the interviewees that we were serious). When 10:30 arrived, he called me at 10:28 and said he would be late. (I personally attach great importance to the concept of time, because a person can not even manage time well, how can he manage his own future, and even the future of the company.) I still told HR: It’s ok, just be late, don’t worry, be careful on the road! But this guy is a bit…. 10:50 or so, and call to say: the company has something can’t come!! Oh my God, I feel like I’ve been challenged: you can’t manage your time well enough, and then you show up for an interview without taking care of your affairs! Then he did not contact this side, the interviewee is also nothing! I personally am very angry, although this person in the expression is also calculated more sincere, but I think this person can not reuse!!

Under a candidate is an on-the-job graduate student, not a computer professional, the professional I still have no rigid requirements, not because I see many English major iOS developer cow force, myself included) I gladly about the interview, directly over the HR I just interview him, there is no requirement of iOS development lead the interview, because I want to quickly find a friend! Interview begins, typical programmer: plaid shirt, backpack, curly hair (fluffy and messy). I didn’t have much of an image requirement, and then I started interviewing:

  • First I asked for a self-introduction (no more than 3 minutes), but I froze, and gave me 10 seconds to finish, what is his name, and where is he from! No, my self-introduction was very brief, and I could see that he was very nervous. I made a little fun of the atmosphere and started to discuss technology!

  • Because the project requires me to compare the learning ability of the interviewer, HOW do I arrange his spare time for him? He peremptorily very honest: open black!!

  • I asked him from the side, does he like cooking? Judging by his sense of life, he is still honest: his home is usually outside the shop.

  • I shared some of the following technical points with him without much communication, because I was not satisfied with the whole thing. No self-confidence, expression ability is not enough, there is no passion for life, the work is also estimated to be enough! I calmly told him: SORRY, you don’t meet our requirements in some aspects (I don’t like it, I don’t want it, I have to wait for the news). I talked to him about his problem and sent him out of the office!

A few days later came another candidate who impressed me especially! I have five years of iOS development, and I have a deep research in instant messaging, audio and video. I am very happy. Before he came, I talked with his resume and learned about his company and products (I did not get what I want, and comforted myself, these are not representative of anything). He came to the interview as promised and expressed himself very fluently. I give him full marks in self-introduction. I am very happy!!!! Then I started sharing techniques with him, talking about architectural patterns, layering of componentized projects, and he was a little talkative. I doubt he knows much about componentization! Then I turned to MVVM and found myself a little disappointed with such a bidirectional binding architecture. Answer what View ViewModel Model! It’s like it’s just stuck here. Later, I discussed with him about two-way binding. What did he think? He didn’t seem to understand! The RAC interview behind me will be swallowed! I moved on from architecture to network programming. I first from the simplest: socket this understanding! He’s got a socket at the network layer! I have no interest in the back…….. Oh, my gosh! You develop 5 years, I instant meng force, I am speechless, because the back of the question, sincerely answer not to force! Finally, I told him directly: Not quite, thank you for coming to the interview!

I’m stupid: after 5 years of development, these shouldn’t be required features! It’s not supposed to be visible, right?

There were a lot of interviewees in the back, and I interviewed them with an original heart – because they were all my would-be friends. It turns out that the vast majority of iOS developers with 3-6 years of development experience, the technology is too superficial, the bottom line is too deep, and multi-threaded networks are interview killers! There are many people who say that they are very familiar with architecture and framework. Found a little too false. Discuss how to study at ordinary times, very few people can answer! (Among them, there is a developer with 3 years of experience, who is not a computer engineer, who is training iOS. At the beginning, I am not satisfied with the training, but the later answer is that it is really good, whether it is low-level advanced, network, multi-threading and architecture, they are OK. Of course, I hired them, and the work in the future is also quite good.)

I think iOS developers are too smooth! A few years ago a line is high (indeed higher than other introduction to the IT industry salary) but learning ability is generally low, and there is no habit of learning (very deadly) iOS now market is relatively stable, personally think that senior iOS market scarce, but the vast majority are application layer development, rarely write articles, rarely discussed, are rarely able to keep on learning! There are also a lot of people questioned said: interview build aircraft carrier, entry screw! I think you are not enough, at least our project is very needed!

Here are some suggestions from the interview during this period:

  • Architectural patterns, programming ideas, design patterns
  • The bottom step, deep understanding
  • The tripartite framework should be known for what it is and why
  • Multithreading and Network
  • Memory management, performance optimization
  • Data structures and algorithms
  • Audio-video direction
  • The reverse direction

Finally, I hope the iOS development crowd, go, go, go!! Practical technology, serious learning ability!!!! If you like, you can give a like :+1: or follow.

As a developer, it is especially important to have a learning atmosphere and a communication circle. This is my iOS communication circle: no matter you are white or big, welcome to enter!! Topics to be shared include reverse security, algorithms, architecture design, multi-threading, network advancements, also underlying, audio and video, Flutter and more…… According to the network to comb their own development experience summary of learning methods, free to share with you. You can download it yourself if you need to. + skirt: 196800191 or + WX (XiAZHiGardenia) Get interview materials resume templates to communicate skills together