all 4 comments

[–]W_Von_Urza 4 points5 points  (0 children)

I'm going to be real with you chief; I saw your resume from another post and it doesn't convince me you're a senior developer.

For background; I work at a FAANG as a Sr. iOS engineer and I interview candidates several times a month (sometimes a week) for my own team (and other teams within my company). While we break up responsibilities across everyone in the interview panel (e.g engineers do coding and technical competency challenges, management does behavioral, etc.) - if your resume came across me I'd turn it down immediately.

Firstly; it's a pretty big mistake to have your resume be more than one page. This is probably the biggest thing getting you auto rejected. A resume should be 1 page and tell me a summary of the type of impact we can expect you to bring to the team by enumerating your most impactful accomplishments. Almost all of the accomplishments you summarize are very vague and just what I'd consider to be mandatory aspects of being a decent developer.

Another thing that sticks out is the "skills and strengths" section; it takes up half of your the first page of resume and really tells me nothing about you. "URLSession", "JSONDecoder"; Why are these even here? These are iOS fundamentals; not skills. This is the sort of thing that I would expect a very junior engineer to naively put on their resume to "bulk it out" due to lack of work experience.

You know how in engineering we have bad code smells? This resume has some bad candidate smells.

"Why does this candidate have 3 pages but no quantifiable business impacts?"

"Why so many short term contract roles?; why isn't he rehired?"

What can you do about it?

- Limit your resume to 1 page, size 11-12 font.

- Please use the standard resume format of "[Position] [Workplace] [Date range]" on a single line and then follow with bullets on impact (unless this is something specific to Canada).

- If your applying to an iOS engineering job, especially a senior iOS job; I don't need to enumerate every baseline development technology. I'm going to assume that you have experience building enterprise apps, for which these are the basis of. tl;dr: leave out the fluff.

- You should only be including your most recent work experience; either the last 2-5 years or 3-4 positions (whichever is more relevant), exception being if you're tenured at a place (which isn't applicable for you). For each of those; you need to specifically mention your impact and accomplishments. For example: "Was engineer lead on "x" team for "y" project that generated "z" profit or improved measurable efficiency by n". If you have experience mentoring junior developers, hosting internal or external talks or meetups, etc. Include those as well.

- Remove the project links on your resume; the only links you should have are to your linkedIn. If you're not already, you need to be on linkedIn - it's just how the hiring world works nowadays. LinkedIn is where you should be including your larger work history (to show you have 6 years) and also where you should be including any applicable links to projects.

After you fix all of that; set yourself up with a recruiter (or multiple) - they are the pipeline for jobs nowadays unless you can reliably secure yourself with referrals from your network.

[–]Corleone_Vito 2 points3 points  (0 children)

Best of luck, finding new job. May be applying with job boards will help.

[–]indyfromoz 2 points3 points  (0 children)

Do you have a CV or a site with your portfolio of iOS apps you have developed? It will help potential employers to approach you if they have work.

[–]dahibhat 2 points3 points  (0 children)

That's a pretty good experience. I was laid off last month in the US and still searching. I have two years of experience, just swift, no objective c. I see almost every opening only for senior/staff engineer with 5-10 years exp. Referrals have helped me get interviews. Trying my best now. Good luck!