Resumes

[Japher]

Don't list skills, give examples of when you utilized them.

I have a 2 pager and a 1 pager... I like my 1 pager better and use it more often, I get good responses.

Functional resumes suck, stick with Chrono

[Wiglaf]

Anything you can say in two pages you can say in one. At the professional level you make them longer to show your experience and you call it a CV to get away with it. In high school and college anything more is presumptuous.

My resume is great if anyone wants to see it, it is a list of all I have done in my life and yet I keep it to ONE PAGE.

[loinburger]

Skills is relatively long, since I have a lot of those .

Are you doing one skill per line, like "skill1" (hard return) "skill2" (hard return)? If you are, then don't. People already know what the skills are by their names alone, there's no need to add descriptions - my resume says "C, C++, C#," not "C: A low-level language. (hard return) C++: Some object-oriented-ish crap put on top of C. (hard return)"

[Hauldren Collider]

Mainly it's long because this particular job (which was posted at my school's career center so basically they're looking specifically for students from my school) asks to have a list of relevant classes, relevant = electronics, CS, math, any APs, and I have a bunch of those and I was tired of ****ing with columns and crap so it's a bunch of short lines.

[DaShi]

Yup, at your age and point in career, a long resume only demonstrates that you can't present things concisely. Keep it one page, keep your points short and easy to read. You can always elaborate in the interview.

[Hauldren Collider]

Are you doing one skill per line, like "skill1" (hard return) "skill2" (hard return)? If you are, then don't. People already know what the skills are by their names alone, there's no need to add descriptions - my resume says "C, C++, C#," not "C: A low-level language. (hard return) C++: Some object-oriented-ish crap put on top of C. (hard return)"

Lol no programming languages are all in one line but I probably have things I don't need to mention, so I'll try and get rid of them. Most spacewasters are under sysadmins because there's a crapload of systems that I work with/know how to use.

[loinburger]

Relevant Classes: CS101, CS102, etc. All on one line (barring word wrap). If they want details on the classes they can check the course catalog.

[Hauldren Collider]

Relevant Classes: CS101, CS102, etc. If they want details on the classes they can check the course catalog.

There's not really a course catalog. I'm at a high school remember.

Yup, at your age and point in career, a long resume only demonstrates that you can't present things concisely. Keep it one page, keep your points short and easy to read. You can always elaborate in the interview.

good point, fair enough. Maybe some of it should go in the cover letter?

[Ming]

It's ok to have a "clean/simple" resume that is a good summary of your skills/abilities.
You can use a "personal" cover letter to include specifics that address the actual job you are using it for.

If you are only doing a resume for a single job, and have no intention of using it for anything else, then personalize it for the job.

AND USE COLUMNS... a bunch of short lines looks like crap.

[loinburger]

There's not really a course catalog. I'm at a high school remember.

Somebody knows what the course descriptions are, and whoever's reading your resume ought to know who that person is.

[Ecofarm]

Any job description should include specifics about how exactly you helped or improved the company or system/part with which you were involved.

[Ben Kenobi]

AND USE COLUMNS... a bunch of short lines looks like crap.

This. Word.

[Hauldren Collider]

By the way, thanks for the advice everyone...I've never really done this before, so I hope I don't seem TOO stupid. But I probably do regardless . Thanks again.

[giblets]

No, you don't seem stupid.

[Ming]

The fact that you are asking for help instead of thinking you know everything even though you have never done it before is a good sign