Savvy businesses know to go where the customers are, and increasingly, those customers are spending time on mobile. In 2018, Statista projects there will be 236 million smartphone owners in the U.S., a population that will grow to 257 million by the end of the decade. Those with smartphones, tablets, and other mobile devices are downloading apps at a rapid rate. App downloads, which totalled upwards of 90 billion last year, increased by 15% from 2015 to 2016, and the time users spent on them grew by 25%.
What does this mean for developers? More than ever, businesses are focused on building mobile products, and developers knowledgeable of how to work in iOS, Android, and mobile web are in high-demand.
If you’re interested in moving to mobile, be ready to answer these four questions during your interview with a hiring manager.
“Can I see some examples of apps you’ve created?”
When applying to positions as a mobile developer, come prepared to show examples of past work because it will indicate what you could contribute to the company if hired. Hiring managers will want to get a sense for what you have developed in the past, whether as the lead developer or through a supporting role, to help them determine if your skill set and experience suits their needs.
If you have them, it’s a good idea to go into the interview with a list of apps you’ve had a hand in bringing online along with links to app stores, such as Google Play or the iOS App Store, where they can be downloaded for a test-drive. If you don’t have examples of paid work you’ve completed for a company, show any mobile products you’ve built as practice.
The truth is, hiring managers care more about working apps in the App Store / Play Store than they do about code on Github. Even if it’s not an original idea, if you’ve built an app, publish it!
“What experience do you have with monetization tactics?”
Early on, businesses will have to decide whether or not they want to make money off their app. If the app is simply a mobile interface for, let’s say, an online retail store, the primary objective would be to integrate mobile display ads and make in-app purchases streamlined and intuitive. If the app is intended to bring in money for the company, then mobile developers could opt for freemium structures, pay-per-download models, or implement paywalls.
When heading into the interview, be sure to understand how various pay models could be integrated in the development process to monetize any app and, when asked, be able to explain which specific features could help the company’s app make money.
“What’s your preferred communication method during the development process?”
Because app development is a deeply collaborative process, hiring managers will want to know you can and will communicate with teammates throughout the project. You’ll need to discuss and plan everything from design to features to a timeline for release and more, making frequent and productive check-ins essential to the quality of the finished product.
Know your work style, and how you like to relay updates when asked about keeping in touch during the process. If you prefer in-person or video-conferencing meetings over phone calls and email or favor Asana over Basecamp, make sure to convey those preferences to the hiring manager so he or she can set expectations for working with you.
“What’s your typical checklist for an app launch?”
Mobile developers are responsible for building the app from the ground up and delivering it to customers, from idea to prototype to launch to app store. Hiring managers will ask how the candidate plans to put the finishing touches on the app. How will the developer test the app, fix bugs, and get it to users?
Anticipate these questions during the interview knowing that a test will require a large beta group, bugs will be fixed with app updates, and that you intend to plan for the, often long, submission process to get the app into app stores. Showing an awareness of the full process will impress upon hiring managers that you’re a mobile developer who knows how to get the job done.