Imagine you’ve spent countless hours on your mobile app idea, developed some wireframes, and maybe you’ve followed my advice and had a designer prepare artwork for your mobile app.
The last thing you can afford to do at this point is end up with an app that just doesn’t live up to your vision.
Yet most people who need to hire a developer don’t have a clue what to ask them. How could they? That’s why they need the developer in the first place!
This post will give you the 8 most important questions to ask when interviewing iOS developer candidates for your mobile app. And if you’re an iOS developer, make sure you have good answers for these questions.
NEW: Want these questions, AND the answers, in an easy to read PDF format? Click on the image to get your download.
Before we get to the questions, let me explain what we are looking for in asking them.
Purpose of These Questions
The purpose of these questions is not to see who answers every single one perfectly. Many will not.
The purpose is to find an iOS developer who knows what they are doing, and will work with you through the process.
The process of building a mobile app, especially your first mobile app, takes unexpected twists and turns, and you may very well find yourself asking for several ‘small’ changes along the way.
Now imagine which of your candidates that you interviewed would you feel most confident in those situations. That is when finding the right developer for you is so valuable.
It really comes down to these 4 characteristics:
- Technical Experience – clearly, they must have the technical experience of building iOS apps, and ideally with some of the features you are asking for.
- Creativity – the best mobile app developers know there is more than one way to implement functionality or features, and they apply the best approach to that particular situation. Creativity is also helpful if they can suggest ideas that you had not considered.
- Honesty – this goes without saying, but you want someone that will be up front with you about what they can and cannot do, and to give you honest feedback about any concerns they have with your project as a whole.
- Compatibility (with you!) – You need to have a comfort level with people you work with. Take it from me — if you don’t feel that in the first 2 minutes of the interview, you need to keep looking!
Now that we’ve reviewed the purpose behind these questions, let’s get to them.
8 Interview Questions for Your iOS App Developer Candidates
- How many iOS apps have you published in the App Store? What are the names of those apps? What are your download numbers for each?
- What is your experience working with
(your feature should include any specific technologies or features in your app – accelerometer, location based services, in-app purchases (IAP), etc.)
- What’s a memory leak and how do you test for those before publishing your apps?
- What is code signing and how does it work for iOS apps?
- How do you handle app artwork and graphics?
- Tell me about your testing process. What tools do you use for app testing, and how would I be involved?
- Use this question if you plan to make money with your mobile app: What kind of app monetization methods have you implemented? What ad network APIs do you have experience with? Do you have any best practices around implementing in-app purchases?
- Please provide contact information for your last 3 clients you developed an iOS app for. What worked well in those projects? Why?
Another question to ask, not to qualify the candidate, but to understand what is covered and what is not, is this one:
Do you submit apps to the iOS App Store yourself? If not, what guidance will you provide for that process?
That bonus question can save you hours, even days, of frustration not knowing what is happening in the approval process.
Remember, these serve as a good foundation of interview questions, and you are encouraged to tweak these and add to them for your specific situation.
What other questions have you asked your app developer candidates? Share them in the comments below or on our Facebook page.
Image Credit: Kaleb Fulgham on Flickr