[danilocampos]

I'm afraid this isn't going to produce much beyond anxiety in your candidates. This leads to the sort of interaction where I'd end the interview early, thank the interviewer for their time, and high-tail it out of there never to return.

It's a trivia quiz. And frankly, who cares if you know what iBeacons are? What's the likelihood a project requires knowledge of both iBeacons and HealthKit?

HealthKit AND HomeKit?

HomeKit AND Apple Pay?

Why ask about something as deeply specialized as Metal, a brand new 3D graphics API, when so few projects are likely even to need it—except in game dev shops?

And in what conceivable universe does someone need to know the screen resolutions of any given piece of hardware? I've been building iOS apps for six years now, and I barely remember at any given moment.

Anyone looking for great interview questions for iOS devs should instead consult Black Pixel's excellent post here:

http://blackpixel.com/blog/2013/04/interview-questions-for-i...

It talks through concepts as much as technologies, hitting the most common cases for what a developer will actually use.