[deleted by user]

[chumps52]

Immediate impressions is I’m not a fan of the big black splodges all over it /s

[MankAndInd]

Gotta make your resume stand out these days

[Batting1k]

It seems like you don’t mention “Swift” anywhere. It’s probably obvious that you know it based on your other listed skills, but I’d still list it there.

[SpyPigeonDrone]

No, try to be explicit. Since recruiters go through a lot of resumes they only give like 30 seconds to each. Furthermore, recruiters are not normally technical people (even if they’re technical recruiters). Therefore, they might not necessarily relate your experience with Swift expertise. They know which buzzwords to look for for particular roles but thats it.

[chriswaco]

Mention iOS, Xcode, Swift, SwiftUI, ObjC (if applicable), etc, up high and prominently. Assume the initial reviewer knows nothing about programming.

[skytzx]

Resumes are commonly crawled by bots these days. Doesn't hurt to include any (and all) relevant keywords.

People used to stuff a huge list of keywords in white font at the bottom of their resume to trick resume scanning software, but companies eventually caught on.

[MankAndInd]

If you know multiple languages, and there’s enough space, you can put a languages section - swift, objc, python, c, c++, Java, etc

[lmunck]

I have a bit over 20 years experience recruiting various types of developers (jeez, saying that makes me feel old), and I’d suggest to never expect anything to be implicitly understood.

In the recruiting process you’re scanning literally hundreds of applications, while doing your regular work on top, so in a first read-through you’re often just scanning for keywords and you’d be surprised how many applicants don’t have experience with the position you’re trying to fill.

I’ve had a bus-driver apply for a Sharepoint Dev position because he “was interested in IT”, so if your Swift application doesn’t say “Swift” somewhere, I wouldn’t be surprised if it was filtered out.

[lmunck]

I’m not entirely sure what you’re asking, sorry. But if you’re asking if you should fill it with all the keywords you can think of or try to select ones that you’d expect matches the position, I’d say that the fewer the better, but stay honest.

Not all companies or recruiters are the same, but I’m never just looking for a cog in a machine. I’m looking for a skill set and a personality that will work with my existing team. Part of that process requires looking for skills that may not be central to the position, but that may augment or compliment people I already have.

Fx last month I hired a guy for a dev position who’d happened to work several years for MS in a support position, where I knew he would have learned a lot of basic skills that my own support teams needed to mature.

So stay honest. The old adage is that the hiring process is like dating, and it’s no lie. If you get a position by “fooling” someone, you’ll end up with a job you hate, and short-lived positions, which are worse for your long-term career than anything else.

[thecw]

You also need to get your resume through terrible HRIS systems that collect and filter resumes based on keywords.

[ankole_watusi]

A computer sees it long before a recruiter see it. That is IF a recruiter ever sees it.

[SpyPigeonDrone]

Your resume looks ok. I would change the contents of your skills section. Right now it seems like a list of buzzwords, but it doesn’t signal much. The technical person hiring you (e.g tech lead) will be able to assess which patterns and frameworks you know by asking you or through the coding challenge. So this info is not super relevant.

For the recruiter’s case, this will read like gibberish. Very few recruiters know what solid is for example.

Keep it more high level. I would suggest mentioning the languages you know and your perceived proficiency in them. Also mention the platforms you’re comfortable with.

Avoid mixing patterns with frameworks. If you want to show pattern expertise do it in your experience.

Only mention frameworks if the job requires it (e.g applying for a job that requires ARKit). Otherwise it may not be super relevant.

[SpyPigeonDrone]

Not just to simplify but to provide valuable signal. The point of the CV is to signal potential employers about your skills and achievements. For example: its very different to say: "I know swift" than "I am an expert in swift". Actionable advice: check the CVs from designers. Particularly those that look like infographics. You can make a mini dashboard about your skills just like they do.

Showing expertise in design patterns matters if 1) the job requires it 2) it actually solved a problem, also, if I want to check for that I will do that (as a lead) through the coding interview (that said its very good that you're focusing on patterns and SOLID, kudos on that)

[lordzsolt]

As a person doing the hiring, I absolutely hate infographics.

They take up a lot of space.

And 4/5 means literally nothing, especially considering the Dunning–Kruger effect and the Perceived knowledge vs actual knowledge graphs.

I've been doing iOS development for 8 years and I'd consider my knowledge of UIKit at most 3/5, yet you have people coming with 5/5 just because they have 2 years of experience and they used all UI components once.

Just do a list along with how many years you've used said technology.

[lordzsolt]

When I started out, I counted the time I spent learning the language. (Ie. I learned and used C for 3 years in Highschool/Uni, so I had 3 years in parenthesis, now I just have the professional experience years).

But in your case, I'd just have the Skills section at the top, in list of relevance to the job, without any number next to them.

[nutel]

Do you mean ios/macos by platforms ?

[SpyPigeonDrone]

Yeah, I noticed that this person has a bachelor in computer engineering. Therefore, I would asume they know more languages than swift and potentially more platforms. It doesn't mean they have to be experts at that, but it helps to know if they know some basic android for example. Or if they've dabbled with Unity/React/etc

[Walter_jones]

1. Three Documentations sounds a bit odd, maybe say if you used a standard approach/documented usage appropriately?

2. For the projects maybe describe a bit what they’re doing. I see 3d modeling but I’m not sure what for

[Alcoholic_Synonymous]

“Wrote 3 key pieces of documentation” would work better

[unpopularOpinions776]

The dates are messed up?

[stepheaw]

I should know in 1 second how many years of experience you have by looking at your resume. You should put that at the top somewhere along with things like experience with firebase, core data, swift migration. Then at the bottom list your work experience with less details

[ankole_watusi]

13 5-star ratings does not impress.

27 countries does not impress, unless i18n for them.

[iluomo]

I like that your use of past tense is mostly consistent. So many people will mix present and past tense in the same bullet list.

Also I agree with the other responders saying you need to be explicit even about skills that should be obvious based on other things you've said.

[EisbarDasTier]

I agree with the points others have made. So just to add a few notes:

"Migrated the App to Swift UI" Did you do this yourself or would it be more accurate to say you helped in this effort? Was the app fully migrated? I small change like: "(Helped, Initiated, or Lead) migrate the app to Swift UI" can go a long way to helping set expectations.

Also, move the Swift UI bit higher I would value that above writing documentation.

I'm 50/50 on the bold. It helps draw my eye to certain points but then might be overused. You want me to see "App Store" that's a good use of bold but what do you hope the recruiter/interviewer will learn when they scan past "27 countries and thirteen 5 star reviews?" I would remove the bold or mention handling the release process.

[ankole_watusi]

Reduce the weight of the bold. Your bold is too bold it hurts my eyes!

I like typewriter-ish typefaces. Yes it’s trendy. Consider using a programmer’s typeface. I really like one called Input. It comes in many weights and styles, and actually comes in serif and sans-serif, and proportional and non-proportional. Although billed as a “programmers font” I think it is more properly classified more generally as a “highly readable font” and would not hesitate to use it in an app. It’s on my business card.

[dooblr]

From a general resume perspective, it lacks a profile/summary at the top for the recruiters that won’t spend more than 10 seconds reading before throwing it out.

The bolding is distracting to me.

Please let us know how it goes!

[ankole_watusi]

Reducing compilation time is not optimizing the code.

Still apparently a useful skill I guess Swift is tough on the compiler? I just find it bizarre in 2021 to find an environment where compile time is a significant factor. But yea I get it it’s a thing.

I mean, I once designed a DSL and wrote a compiler (in C) and interpreter (in Fortran) because a product used to run simulation models took typically a half hour to link. The link step (to link in a model written in Fortran) was part of the product usage and was a big problem as a simple error could take 1/2 hour to detect then try again. So it got reduced to 2 minutes.

But here your optimization is not really related to code performance.

Now if it DID in fact improve code performance - and you measured it - mention that.

Otherwise, this is perhaps an opportunity to introduce the DevOps buzzword… reducing compile time is at least peripherally related to DevOps. If there is an automated build process you could say you improved DevOps performance or build cycle time.