iOS Developer Resume Examples

Final Thoughts and Advice

And that’s a wrap for our iOS developer resume examples article!

But before you go, the team and I thought we’d leave you with some final advice.

Ricardo Rendon Cepada

• You are not your harshest critic, designers are. After you make your resume, find a designer friend and ask them for help identifying “hot zones” for your resume, layout improvements, and elegant color palettes.
• A resume is more of a formality – other things matter more. As developers, the best way to get recruiters interested in you is to have an excellent online profile, easily accessible portfolio, and proven milestones (e.g. Published apps, StackOverflow reputation, GitHub repositories).
• Live in the Bay Area! Tech recruiters are ravenous out here and there is no shortage of exciting job opportunities for developers.

Scott McKenzie

• Keep it tight; not too wordy!
• Let yourself shine through whatever format you’re asked to give your resume in.
• Give the reader what they want; easy access to information.
• Try to relate skills with something tangible; apps make this easier than traditional, internal corporate websites.
• Don’t try too hard to stand out; there’s a danger of distracting from your skills and making the reader think you’re trying to trick them.

Marin Todorov

• Bold things where appropriate. Bold your current skill set, your greatest project and highest education degree, and your name, so that it stands out at a quick glance. In fact, you might just make your name a different color, include your name also in the file name, and the email subject when you apply.
• Use hyperlinks. If anything catches the attention of an employer they should be able to click it and check it out!
• First things first. The first two paragraphs are most important, so make sure they catch the eye and make a good impression.
• Be truthful. Be sure everything in the CV is 100% true, because next step is your interview and people gonna want to know more about projects, companies, etc.

Orta Therox (Code Team Member)

Technical people can take a look at the commits themselves and debate themselves whether I’m using best practices, and by seeing how well documented my code is and how well formed commit messages are they can get a sense of what it’s like dealing with me.

Like a lot of things treating your github profile as your resume revolves around having enough content on it in order for it to be relevant, this means if you’re just getting started it can be difficult to get the ball rolling. But like with all open-source work, it self-perpetuates as you write some initial OSS you end up writing more and then a few weeks later you’re working on CocoaPods itself.

One of my workmates actually wrote about this 2 years ago too: GitHub is your new resume

• Github is my CV. At this point I’m a prominent open source developer, I got here by writing libraries and contributing to projects I felt were important. For me now github is a list of projects I’ve forked and helped out on, wrote my own and it gives an impression of how much time I put overall into projects. It says what languages I’ve worked with, for how long and usually with a a bit of additional context you can see why.

  Technical people can take a look at the commits themselves and debate themselves whether I’m using best practices, and by seeing how well documented my code is and how well formed commit messages are they can get a sense of what it’s like dealing with me.

  Like a lot of things treating your github profile as your resume revolves around having enough content on it in order for it to be relevant, this means if you’re just getting started it can be difficult to get the ball rolling. But like with all open-source work, it self-perpetuates as you write some initial OSS you end up writing more and then a few weeks later you’re working on CocoaPods itself.

One of my workmates actually wrote about this 2 years ago too: GitHub is your new resume

• Attend meetups and conferences. WRT getting jobs, _meetups_ & _conferences_ – easily the best resources IMO. You’ve got to be able to talk the talk so you can’t break into the obj-c scene with no experience there, but you’ll definitely get to meet a lot of people trying to hire. Everyone I’ve hired has been from me meeting them at a conference or meetup.

And that’s it! Huge thanks to Charlie, Ricardo, Scott, Marin, Brian, and Orta for contributing their resume, cover letter examples, and/or tips/advice to this article in the hopes that they may be of use to others.

We hope you enjoyed this second part of the series – stay tuned for part 3, where Kyle’s back to discuss iOS interview questions!

In the meantime, do you have any advice or questions about developing an iOS developer resume? Join in the discussion below!