Re: Can I get some advice for writing a resume?
Maybe it's just because I'm Canadian or because my school had a really good co-op program for computer science, but my experience with internship/co-op jobs was really, really good. They actually treated you like a real employee, with actual jobs. More than proof-reading code and fetching coffee. WAY more. One of my jobs was with the Department of National Defense as *the* programmer in the operational research department; the whole department was made up of mathematicians and statisticians, so they went out and hired a CS student from the university to write software for them. Pretty awesome job, really. But I digress.
For your resume what found useful in school was to divide your technical skills into three categories: basic knowledge (i.e. you know the very basics, and know where to look when you are out of your depth, but don't expect miracle code), course knowledge (i.e. you took a course or two on this, but haven't used it much in the "real world"), and practical (or advanced) knowledge (i.e. you have used this on your own time or in a previous job; you may not be an "expert" but you're more than competent).
This gives you the ability to qualify your skills a little bit better. For example, if you regularly write your own software at home in Python and PHP, but you've only dabbled in C and C++ for a course or two you'd say something like:
Basic knowledge of: Java, Assembly (i386, MIPS, ARM)
Course knowledge of: C, C++
Practical knowledge of: Python, PHP
Fill in the blanks as necessary.
Everyone has their own resume style. It takes a while to find one that works for you. If you want you can post a censored version of your resume on here once it's written so that you can get some feedback on that too.
GCS/O d+(-@) s: a-->? C(++) UL P+ L+++@ E@
W++$ N++ !o K++ w(++) !O M(-) !V PS+(++)
PE-() Y+ PGP++ t++(+++@)* 5++ X++@ R+++@
tv+ b++(+++) DI++ D+ G+ e++>++++ h- r y?
Bookmarks