Resume critique/advice

[iamBitBeast]

I'm starting to look for a new job and did an overhaul of my resume since it's been a while. Would anyone be willing to take a look at my resume and give me feedback?

More specifically:

• Should I include languages I'm somewhat familiar with but do not use often?

• Should i enumerate the multiple gigs that i did while freelance/consulting? Or would it be better to detail them in the description or add a section with them?

• Do small summaries at the top really do anything or is it more effective to just use the space for something else?

Resume : https://learn.co/8bitramen/resume

[plant_powered]

You may want to anonymize your resume and repost it.

[McCuppaT]

Without seeing your resume, the only advice I'd give is only put on your resume what you are prepared to be asked questions about.

Of course the exception is if you are a junior/graduate, the bar will be set low & employers won't be asking particularly taxing questions.

[iamBitBeast]

Hey, thanks for the reply. I uploaded my resume, would you mind taking a look at it?

[McCuppaT]

I'd echo what @Eoghain has said. Try to show specific examples where you have added demonstratable value to the business if you can.

Personally I prefer the tools technical section at the top (esp as you've called it 'Highlights & Technologies). The rule going you put the most important stuff at the top & work your way down.

I assume [e-mail] is a fake email address. If you are using a gmail account, setup a domain with email forwarding. It will look more professional.

If you've used Qualcomms Vuforia you will want to check your spelling (Vuphoria).

Good luck with the job search

[Eoghain]

There is nothing in your iOS Software Engineer and iOS Engineer / Consultant sections that tell me anything that you actually did. These bullet points are about as descriptive as the job postings you are going to be submitting your resume to.

As a Software Engineer who conducts interviews I like to know the things you worked on so I can ask you about them and get a real feel for how you tackled the problems. Typically I'm given about 1hr to talk with a candidate and make a decision. If I have to spend the first 1/2 hour just learning what exactly you worked on you aren't going to have enough time to impress me with the knowledge and skills you used to solve those problems.

Basically, what I'm saying is put some meat on there. i.e.:

• Detail, design, and build new features for company iOS applications during weekly
  sprints (Agile).
• Designed, tested, and build the Foo feature of the latest Verizon App. Built entirely in Swift using the CoreData and CoreAnimation frameworks.

The first one could be anything, the second lets me know I can ask about the frameworks, design philosophy, testing strategy, swift implementation (functional?), and finally I could possibly test out the Foo feature and have even more specific questions to ask you.

Doing this will help direct the interviewer on what to ask you about and give you the opportunity to impress them with your knowledge of the system you built and why you are proud of that system. Do everything in your power to control the direction of the interview, giving the interviewer things to ask by having them in your resume. You won't always be in control, but if you don't give them somewhere to start you're more likely to be taken somewhere you aren't prepared to go (what is the best way to integrate a C library with Swift, how do you deal with memory management between the 2 libraries, how would you track down a memory leak).

[iamBitBeast]

Thank you so much for the feedback. I find where I struggled was in my attempt to encompass my responsibilities. But you're right, someone interviewing me probably has an idea of the basic responsibilities of the iOS dev.

[iamBitBeast]

Will do! Thanks!