Some resume' advice to pass along

killbilly

Vocals, Lyrics, Triangle, Washboard, Kittens
Use this as you see fit - I realize it may not apply to everyone. Note that this applies to a non-aviation industry, but may have some applicability.

A very talented friend of mine - a guy I would hire in a second if I could - has been looking for a new job due to changing circumstances at his current employer. He's been having a hard time getting through some of the resume' gateways, presumably due to keyword matching issues in his resume'. At least, that's what he thought, so I told him I'd try to help.

I called our corporate recruiter and had a chat with him about that and had him look at my friend's resume' as well. The recruiter pointed a couple of things out:

1) Most recruiters and resume systems do not rely on a straight keyword match for acceptance/rejection. It happens some at the level of companies who get applications/resumes by the thousands, but there is rarely rejection based on a lack of (or inclusion of) certain words and phrases in the resume'.

2) What does happen is that the software they use looks at the repeated inclusion of certain phrasing in the same document, and that inclusion frequency can increase the rank of the resume in their stack, which makes you more likely to be eyeballed sooner. Example: If they are looking for "multiple years of network security experience" then at least a chunk of that phrase needs to exist in your application/resume more than once to rank higher in the system. (note, this does not apply to every company, or all jobs, but it's something our recruiter pointed out as a trend. I would encourage you to do some homework on this.)

3) In reviewing my friend's resume, the recruiter pointed something interesting out: it did not define a career arc for the desired position. My friend has done many things - niche disciplines, if you will - within the overall IT industry. However, there wasn't a common thread in how he laid it out in the resume' indicating his career trajectory toward the kind of role he was applying for. It was inconsistent. The recruiter recommended targeting the positions and descriptions along an arc which applied to/resembled the desired position. While diverse experience shows a well-rounded candidate, that doesn't necessarily translate as a GOOD thing in the initial vetting process.

4) Finally, my friend has some military experience, which is desirable these days. But his description (commanded a tank platoon in the Army) was vague relative to the job he wanted. Again - that career trajectory thing! If you can align portions of your military experience with the job you're looking for - especially on Federal jobs you apply for (preferential hiring) - you have a better ranking with your application/resume'.

It's somewhat like being a chameleon - the folks doing the hiring want to find someone to hire - you have to give them reasons to make that phone call/send that email to bring you in. Defining an arc toward the position shows that you're more a likely fit.

I realize not all of this can adapt to an aviation resume' (at least, for a 121 airline, but maybe) but it can help in general.

Anyway. I've done hiring before and found this enlightening and figured I would pass this along.
 
Last edited:
SEO for resumes.

That's some of it. The "arc" he referred to was a greater issue, in his opinion. I'm not sure how that would translate to an aviation resume' - at least, not in the 121 world as I said. More likely in the 91/135 arena, but that's purely un-informed speculation on my part.
 
2) What does happen is that the software they use looks at the repeated inclusion of certain phrasing in the same document, and that inclusion frequency can increase the rank of the resume in their stack, which makes you more likely to be eyeballed sooner. Example: If they are looking for "multiple years of network security experience" then at least a chunk of that phrase needs to exist in your application/resume more than once to rank higher in the system. (note, this does not apply to every company, or all jobs, but it's something our recruiter pointed out as a trend. I would encourage you to do some homework on this.)

This is very true. What I have found over the years - instead of listing employment by each employer, list each project you have worked on. Detail exactly what you accomplished, for each project, listing each technology used. You will end up with an 8 to 10 page CV, and it will be very repetitive. It will also go to the top of the list just about everywhere, for the reason stated above.

Also, just about every recruiter claims not to search for buzzwords. In reality, if there is any buzzword that you don't explicitly state you have 5+ years of experience with, well, good luck.

The expectations of recruiters, technical people, and managers tend to be wildly out of whack as well. Be careful not to assume that what a recruiter told you they were looking for has anything to do what the manager is looking for, or what the job actually is. I have found it better to not repeat ANYTHING that you have been told from a prior interview with anyone else, particularly managers. Unfortunately, in modern times, most managers have never met most of their employees, and don't really have any idea what they do.
 
This is very true. What I have found over the years - instead of listing employment by each employer, list each project you have worked on. Detail exactly what you accomplished, for each project, listing each technology used. You will end up with an 8 to 10 page CV, and it will be very repetitive. It will also go to the top of the list just about everywhere, for the reason stated above.

Also, just about every recruiter claims not to search for buzzwords. In reality, if there is any buzzword that you don't explicitly state you have 5+ years of experience with, well, good luck.

The expectations of recruiters, technical people, and managers tend to be wildly out of whack as well. Be careful not to assume that what a recruiter told you they were looking for has anything to do what the manager is looking for, or what the job actually is. I have found it better to not repeat ANYTHING that you have been told from a prior interview with anyone else, particularly managers. Unfortunately, in modern times, most managers have never met most of their employees, and don't really have any idea what they do.

If someone hands me a 8-10 page resume it's going directly to the trash. Ain't nobody got time for that.
 
There is infinite advice about resumes out there. While some of those points don't help too much in the aviation world, this is by far some of the best resume advice I have ever read, and for that, Thank You!
 
If someone hands me a 8-10 page resume it's going directly to the trash. Ain't nobody got time for that.
What you upload to HR and recruiting systems never gets handed to anyone. They ended up asking for a PDF or word file when they call.

I don't like sending Word CV's, as I have seen my own turn up online with Indian-sounding names in the past...
 
What you upload to HR and recruiting systems never gets handed to anyone. They ended up asking for a PDF or word file when they call.

I don't like sending Word CV's, as I have seen my own turn up online with Indian-sounding names in the past...
Hey, Ahrash!!! That YOU bro?
 
3) In reviewing my friend's resume, the recruiter pointed something interesting out: it did not define a career arc for the desired position. My friend has done many things - niche disciplines, if you will - within the overall IT industry. However, there wasn't a common thread in how he laid it out in the resume' indicating his career trajectory toward the kind of role he was applying for. It was inconsistent. The recruiter recommended targeting the positions and descriptions along an arc which applied to/resembled the desired position. While diverse experience shows a well-rounded candidate, that doesn't necessarily translate as a GOOD thing in the initial vetting process.

4) Finally, my friend has some military experience, which is desirable these days. But his description (commanded a tank platoon in the Army) was vague relative to the job he wanted. Again - that career trajectory thing! If you can align portions of your military experience with the job you're looking for - especially on Federal jobs you apply for (preferential hiring) - you have a better ranking with your application/resume'.

I thought these two points are particularly important as a manager who does hiring. When I look at a resume I want to see a path and progression that is leading them to my desk. Something scattered and random with only calendar dates to tie the thing together in a sequential fashion is hard to look at, and it tells me a candidate hasn't really been trying to improve themselves or their skill-sets, just looking for a better opportunity. Position advancement, project management, advanced schooling are all key areas. I avoid "job-hoppers" because they represent a higher risk. That doesn't mean I won't interview them, they just have a lot more explaining to do.

The biggest problem I've seen with military resume's is that they don't accurately document a candidates progress and experience throughout their military career. They don't relate the skills, experience, attributes, aptitudes, etc. to the job they are applying for in a language a civilian recruiter will understand. "Maintained a security company" by itself doesn't translate to civilian language very well, but it certainly conveys a skill set that might be important to a potential employer. Part of the "career arc" perspective. I would advise anybody serious enough to spend the time at a job fair to bite the bullet and get a professional resume review.
 
My aviation resume is a page. My tech resume is around 8-10 pages.

When hiring in tech, if I got a resume of less than three pages, I was wary.

Know the game you're playing.

-Fox

So, one more example to prove my long held observation that in tech-land there is a surfeit of data and dearth of information. ;)
 
So, one more example to prove my long held observation that in tech-land there is a surfeit of data and dearth of information. ;)

It varies.

An eight-page resume has a lot of information to a reader who knows what they're looking at, just like a mountain of customer metadata has a ton of mining potential for if you know what you're looking for.

You'd be surprised how much I can glean from a resume. I think the '1-2 page' rule is quaint, but when in Rome, I'll work on my latin.

-Fox
 
It varies.

An eight-page resume has a lot of information to a reader who knows what they're looking at, just like a mountain of customer metadata has a ton of mining potential for if you know what you're looking for.

You'd be surprised how much I can glean from a resume. I think the '1-2 page' rule is quaint, but when in Rome, I'll work on my latin.

-Fox

Could there be a connection between this and code bloat? When is comes to code, and most other potentially useful and beautiful constructs, I tend toward the less is more school. An old Vermont farmer by the name of Occam once told me, "enough is plenty". Of course, when it came to his corn crop he was squarely of the opinion that plenty was enough. ;)
 
A more than one page resume for a pilot job goes in the trash...

My resume has stayed the same length from flight instructor to regional pilot to mainline pilot to mainline seniority list instructor.

The emphasis of experience and tailoring to the position are what have been changed over the years. Cut the BS when it comes to aviation jobs.

I've seen the mainline instructor applications from line pilots- they follow similar principles.
 
Last edited:
My firm is constantly hiring, and as I have moved up I have had to interview more and more applicants. (financial consulting firm). When HR sends me a resume (undoubtedly they are looking for things similar as in the first post), there is sadly little understanding between what we need to hire, and what HR thinks we need to hire. Resumes tend to be more than a page but less than 3 and depend on the level of the job someone is applying for. As a result, I scan through the resume looking for basic experience, gaps, or job hops. I am particularly interested as to those who work(ed) for a competitor and now want to come over to my firm. I made a similar jump from competitor to competitor and had a very logical explanation. I wanted out of one service offering and into another. While my former company promised a move, due to staffing constraints I was never allowed to move. But I know the industry and telling me "there was no room for advancement" in an "up or out" style firm does not hold water. I also look for experience managing people, as we work mostly in small teams. Anything above an entry job means you have to manage people. I cant tell you the number of people who are applying for a position that requires managing a lot of people and then have no experience with people at all. I even had someone tell me they were looking forward to trying out some techniques they read in a book.

I share this because the resume works to get you the interview, the interview gets you a second interview, and the second interview (or more) gets you the job. Knowing the industry you are applying for, common reasons for leaving, work style requirements, etc. Your resume and interview should craft a story as to what makes you the perfect candidate for the job while telling me who you are.
 
Back
Top