How to write a resume for a career change [closed]

Question

This is a topic I've been fretting about for a couple of years now. I served in the USAF as an Aerospace Ground Equipment mechanic for 13 years and can no longer do my job due to blowing out both of my knees. I'm now studying to become an IT professional, but I don't have a clue of how to translate (or import) my years of mechanical/military experience over to the IT side of the house. This transition of trade skills is like comparing apples to oranges for me.

If anyone is interested I could do a copy/paste of my current resume that concentrates on my mechanical/supervisory skills. And no, I haven't gotten any IT certifications yet, I messed up in planning my education due to CompTIA creating a new lifecycle standard in order to keep certs current so I'm back to the beginning of studying A+.

Answer 1

You are underestimating your time in the Air Force. You probably learnt a lot of skills that are directly relevant to engineering: Solving technical problems caused by everything from bad hardware to bad configuration. You learned how to work under extreme pressure and still deliver good results (I assume you did, or else the planes would have fallen!) You learned how to deal with politics, and still do your job (this is based purely on reading books my ex-servicemen, but it seems the armed forces are not immune to politics).

Now you don't experience writing software, but that shouldn't matter. The biggest problem with CVs is the "Meh" effect. The recruiter looks at your CV and goes "Meh." Most CVs look alike, and there is nothing to separate them.

Now if a recruiter sees your CV, with your 13 years experience, and next to it is some pimply kid who worked at McD, who do you think will be called in for an interview?

You still need to have good technical knowledge to get the job, so make sure you are strong there too.

As to what to write: Write about technical challenges you solved. Something that showed how, when faced with external pressures, like broken equipment, politics and time pressures, new technology, you still managed to complete a project on time. Give examples, so the interviewer has something to talk about.

If you want more specific advice, feel free to contact me privately.

Answer 2

I've seen ex-military resumes fairly often (for software-industry roles). The successful candidates were able, through the resume and cover letter, to paint a picture of how skills transfer. Were you ever in a team-leadership position? Did you have to resolve ambiguous or inconsistent requirements? Were there customer-service aspects to the job? Did you solve challenging problems that you couldn't just look up in a manual (did you have to debug)? Did you go above and beyond the call of duty to get the job done?

Review the qualifications for the job you want, and try to make connections to the experience you have. And, of course, also list the training and projects you're now doing in the new field.

Answer 3

You can mention it briefly and concisely but it must not take a big part of your resume, that role should be taken up by what you'll be learning from IT school, and possibly your internship.

I highly suggest doing side projects too, like contributing to open source projects so you can fill up your resume nicely, but that's all in good time.

Prospective employers may bring it up if their doing an interview, you can talk about your previous job there to your heart's content, but for the resume make it short enough to pique their interest, but make sure it won't overshadow what relevant skillset/experiences you'll learn from your IT education.

Relevant question: Should I put work not related to my profile on my resume?

Answer 4

In addition to what has already been mentioned, try to include some numerical quantification to support your experiences. Seeing numbers in dollar or percentage terms helps to combat the "meh" effect referred to when an employer isn't particularly interested in your resume.