Mainly iOS convention houses lean to have one or two skilled
developers, besides a huge number of junior people. It is also frequent to
organize anyone with more than 3 years of experience job with Cocoa to as
'senior'. At Black Pixel, nearly all of the developers in the staff have 7
to 10 years of Cocoa experience, and several of them are ex-Apple product
engineer. Only some 'junior' developers would be measured very senior somewhere
else.
It's decisive that the people take on are good sufficient to
continue with the rest of the team. We are living at a fast pace, and a fresh
hire that can't keep up will make things tougher for their people we're working
with. It is not actually just right to throw someone into the bottomless end of
the pool without giving them some plan of how tough they are going to have to
work in sort to grasp up with everybody else.
This is not at all complete list of questions, but it is
good enough to get an idea about what you are going to asked:
·
How will you work with asynchronous networking?
·
Did you work with multi threaded Core Data?
Which approach you used and how was it?
·
Did you work with Core Animation? Give some
details about kind of animations?
·
Do you know something about Core Graphics? If
yes, what kind of graphics do you know about?
· Did you ever packed any demonstrated issues
against Apple frameworks on radar? Describe some
·
Differentiate and compare between NSNotification
vs KVO? When will you use one or another also describe some allusion of using
them.
·
Did you ever work with NSOperationQueue, for
which purpose you used it?
·
Give some details about Core Text Experience
·
How will you use NSURLConnection on background
thread?
·
On which things you should be careful about when
you are working with blocks?
·
Did you ever made any custom frameworks or
libraries?
·
Which is your preferred method for working on
application in parallel with a library?

Comments
Post a Comment