Jonathon Smith

(555) 555-5555
[e-mail address]
[LinkedIn/GitHub]
[personal website]

[Address]
[Address]

SUMMARY OF QUALIFICATIONS

This area should directly address the positions requirements.

If its not directly relevant to something they mentioned, it shouldnt be on your resume but it
definitely shouldnt be part of your summary of qualifications.
Youre simplifying their job. They dont want to filter the noise out of your resume.
And you shouldnt make them because they might throw out the baby with the bath water.

PROFESSIONAL EXPERIENCE
[Company Name], [City], [State]
[Position Title] at [Type of Firm]

[Start] Present

Each point should be a quantifiable deliverable. Start with those most related to the job at hand.
If you want to change positions, show them that youve done similar work at previous jobs.
Remember to get away from statements that surround your responsibilities.
Refactor, refactor, refactor. Your resume mirrors your code. If your resume is hard to read and
more complex than necessary, your code probably is to.

[Company Name], [City], [State]

[Position Title] at [Type of Firm]

[Start] [Stop]

You dont have to write down everything you ever did at every company.
If theres not much relevance, dont be afraid to leave it off.
Try and show growth between and across projects. Youve been doing bigger and better things

[Company Name], [City], [State]

[Position Title] at [Type of Firm]

2005 2009

Dont include work youve done before high school. If you need more experience, take on side
projects and attach those.
Finding a way to combine your hobbies with your job is a great signal. You love to code and you do
it outside the hours of 9-5.

[Company Name], [City], [State]

[Position Title] at [Type of Firm]

2001 2005

If youre writing it on your resume, be ready to talk about it. Any experience is fair game, so make
sure that you remember the work you did, the technologies you used, etc.
While you should not include references on your actual resume, have people that you could contact
if you need to.

TECHNICAL SKILLS
Web Tools:
Servers:
Databases:
Protocols:
Platforms:

Breaking down your skills like this makes it easier to read

Like with roles, dont include it unless you could use it without reading
documentation/answer questions about it during an interview
Limit your skills to those that might be applicable
If you have skills that arent asked for but could apply, include them.
Feel free to change this template however youd like. This is just one way to think
about it, but that doesnt mean its the only way or the best way for every position.

EDUCATION

[BA/BSc.] [Major (even if its not CS)] [Month] [Year]

[College/University] [City, State]

[GPA]