7 ms·
Majority of these questions seem to be Trivia, which can be looked up. I don't see any need to learn them. They are probably nice to know but are not helpful in
by kalyan02 12y ago
Majority of these questions seem to be Trivia, which can be looked up. I don't see any need to learn them. They are probably nice to know but are not helpful in objectively evaluating a developers iOS skills.
The important thing while talking to candidates is evaluating their understanding of technical concepts - like multithreading, GCD vs NSOperations, application lifecycle, properties, references, blocks, memory management, caches, sandboxing, responder chain.
Whats the point of someone knowing HealthKit or Voiceover or screen resolutions if they don't understand how atomic or nonatomic properties differ?
- CameronBanga 12y agoUnderstandable, I'm mostly a designer and so the first run I had a few questions like this sounded a little rough. Have a friend contributing and helping with these a bit, but still very early on this. If you have any suggested questions, I would love to add them. If you don't wanna go through the PR, etc, my email is in my profile. Feel free to send over and I will add.
- gsands 12y agoI think part of the idea of interview questions like these is that it will get a developer into those finer points, if they are in a technical discussion.
- buyfromfarm 12y agoagreed. Some are just names. It is kind to ask a technical writer if he is qualified for keeping up with the new trend.
- buyfromfarm 12y agoagreed. Some are just names. It is kind to ask a technical writer if he is qualified for keeping up with the new trend.