The iPhone recruiting comedy begins

Companies are staffing up iPhone projects, and as always happens with new technologies, they’re requiring levels of expertise that are highly implausible, if not downright impossible, for such new stuff.

Here’s a recent example:

1. 3-5 years previous experience developing application using Apple’s implementation of Objective C.
2. Provide at least two business applications that were developed for the Mac using Objective C.
3. At least 1 year experience development experience on the iPhone device.
4. Provide either a prototype or delivered iPhone resident application that displays data pulled from a remote Java class running on either WEBLogic or WebShere app server leveraging a backend Oracle DB.

Um, yeah. Thoughts on these points:

  1. What is this fixation that people have with Objective-C? The relevant skill-set that can be transferred from the Mac is Cocoa and the other essential frameworks. The syntax of Obj-C can be mastered in a day by any professional developer. If you’re looking for experience, then what takes time to learn is finding your way around the various frameworks, and developing a feel for the Cocoa way of doing things (design patterns like notification and KVC/KVO, etc.). The one key Obj-C thing you have to learn is reference-counting memory management, and the OS X developers can now opt out of that via garbage collection.

  2. Narrowing your focus to people who’ve delivered two shipping business apps for OS X probably gets you into the low thousands, if not hundreds, of eligible developers, world-wide. This one is just silly.

  3. The iPhone SDK was released March 6, 2008, meaning Friday is the first anniversary. Until then, the only people who can answer yes to this requirement are jailbreakers or liars.

  4. You’ve heard of web apps, right? They generally exchange data in HTML, XML, or JSON (or just with the HTTP request itself), so it generally doesn’t matter what language, app server, or database is running on the backend. In fact, I think most architects today would consider it a mistake for a client to know, care, or depend on what was actually running on the backend.

So, um, good luck with the recruiting, guys. If wishes were horses…

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.