Hey, Kevin! I have some thoughts on your resume.
Most of my hiring experience has been hiring for e-learning jobs in higher ed, so I can’t speak to what tech companies in particular are looking for in a resume. I’ll also leave your portfolio to be reviewed by those more suited. However, I’ve learned a good deal of resume best practices along the way that I hope can help.
I would move this section to the bottom. Your work experience is more important, and what employers will want to review first.
You don’t need your high school info.
The Portland State/Portland Community College part is confusing. I’m not sure exactly how to reconcile it without knowing the situation, but it might have some recruiters scratching their heads. I found a good blog post on how to address this. Either way, I think you should list these two colleges separately.
Self-employed Tutor/Writer: I look at this job description and my first thought is, “How has this person supported himself with such a position?” I think that because I don’t understand enough about the position itself and what you did in the position. Since you’ve held the position since 2005, I’m sure you have a lot of accomplishments and specific duties that aren’t listed here, so you’ll want to add those. While positions applicable to the jobs you’re applying for are best for increasing your chances of an interview, other positions are fine in the resume too as long as you can clearly demonstrate how you were successful in the position. This goes a long way no matter the position. You list a lot of different subjects you tutor high school and college students in, plus your work writing grant proposals, and this leads me to believe you had a substantial business here that allowed you to do a lot of different things and help a lot of people. As the description is now, though, this isn’t clear. Accomplishments, such as number of successful grant proposals written, number of students per semester, grade increase percentages for students, etc. should be here.
Self-employed Professional Guitarist and Instructor: Again, it seems like you have a substantial business here too, but there aren’t any accomplishments listed. How many bands have you worked with? How many albums or songs have you contributed to and made all on your own? Anything about sales numbers, students taught, business growth, etc.? Any other duties related to managing these job duties?
Intel Corp. Module Technician: Since this is the only tech related position, this one should really shine on your resume. Again, specific duties and accomplishments should be here. Both individual and team accomplishments work great. Expand on your work in the Emergency Response Team and the “computer programming work” you did as well. To me, this is the critical work experience for the jobs you want, so it should be clear to recruiters the work you did (clear but brief explanation of duties) and how you did it (methods used, accomplishments).
- Could you make the FCC certificates links to their descriptions? This might be helpful just in case the recruiter/company doesn’t know much about FCC.
I would combine these into one section called “Skills.”
For tech, I would list the tech you’re the most familiar with/most enjoy and the tech that’s standard or most widely used. Maybe you could even put a few under categories for types of tech or put the tech into categories based on your experience levels (beginner, intermediate, advanced). When I see long lists of software or tech in an applicant’s resume, I’m usually wary. Anyone, feel free to disagree, but a long software/tech/skills list says to me that the applicant has general knowledge in a lot of different tech but hasn’t concentrated on anything. Being able to generalize is great, but I’d want to hire someone who has dedicated themselves to becoming an expert in a few things or even one thing. It implies a certain maturity, discipline, passion, and skill level with whatever those few things or one thing are/is.
You might also want to tailor this section for each application to target just the specific tech/skills the company uses. That way your resume isn’t too long and doesn’t mention tech the company isn’t interested in.
I would remove the narrative under “Skills” and just list the tech you mention here as bullet points with the rest of the tech you have under “Technologies.” I don’t think the narrative is necessary.
- Personally, I would cut this section unless it’s specifically applicable to a job you’re applying for. I’m not sure these are skills companies are looking for in programmers, but feel free to correct me if I’m wrong.
A lot of people may disagree, but regarding objectives, I personally don’t find them necessary in a resume. If you apply for a job with my company, I assume your objective is to get that job. I also assume you have some sort of aspirations for growth beyond the position you applied for, but that kind of thing is better discussed in the interview (growth opportunities is always a good thing to ask when it’s time for you to ask the interviewers questions). If there are certain technologies you want to learn or learn more deeply, I’d rather hear about it in the cover letter.
I hope this was helpful. Good luck on your job search! From what I’ve seen of your FCC forum activity, you’d be a great asset to any company that hires you!