[UPHPU] brasto seeks new LAMP OSS opportunities

[Brandon Stout]

Justin Giboney wrote:
> What I would do...
>
> 1) Your future employer is not going to care what revision number you 
> resume is.

The revision number is for the rare case that someone keeps a 
hard-copy.  Since the resume says to check the online version, they can 
then compare versions.  A later online version means their hard copy is 
out-dated.  I realize that most people will not bother to look up an 
online version, so that's why I have the revision number in small text.

> 2) There is no white space in the document

That's intentional.  Most resume-making documents I've reviewed say to 
avoid white space.  I therefore took painstaking time to make sure 
nearly every line wraps to another nearly-full line whenever wrapping 
takes place.

> 3) Fit you resume to the employer. For example, you said you didn't 
> want a call center job... the why put Call Center Mgmt in your career 
> summary

Good point.  I seemed easier to say than "manager over other IT people" 
but perhaps I can reword it.

> 4) I wouldn't list all those skills under career summary. In my 
> opinion, those aren't a summary of your career, they are your 
> knowledge/skills.

True.  Perhaps I should add a knowledge/skills section...

> 5) I don't know if many people care if you know every single version 
> of windows. Or, that you know how to use different types of spreadsheets.

Perhaps it also does not matter for my current ambition to obtain 
LAMP-oriented employment.

> 6) Listing these skills doesn't say how good you are at them. Try, 
> "extensive knowledge of css", or "5 years of JavaScript programming" 
> (as long as they are true)

Right.  I listed them like I did to try and squeeze everything into 2 
pages, given the fact that many believe you should have no more than one 
page.  I'll reconsider how I have these points listed.

> 7) I wouldn't consider experience with FrontPage as a benefit

I don't either.  In fact, FrontPage seems to make many people /less/ 
capable of writing good web page code.  No, I'm not joking - it really 
does.  I listed it because some jobs request experience with it.  Then 
again, since I'm looking for LAMP-based employment, I should probably 
just loose this point altogether.

> 8) Change your work experience sentences into super action statements, 
> try "Assisted 1000s of customers with server administration"

I like the way you put that.  I avoid a passive voice.  Try searching my 
resume for passive verbs ("is", "was", "were", "are") or prepositional 
phrases (e.g.: phrases that begin with "of").  You shouldn't get many 
hits.  As such, I've found I can say twice as much with half the words.  
IOW, I use an active voice.  So long as the statement is still accurate, 
I could reword a few points something like that.

> 9) I wouldn't list what my degree was.

If I'm looking for CIS employment, and I have a CIS degree, it seems 
natural to list what my degree was.  Also, given search-engine capable 
resume necessities, I'd think one should list the degree for that reason 
as well.  I'm curious what others think on this matter.

> 10) Don't list the degree that doesn't pertain to the job (Family 
> Science), unless it does.

Interesting.  I suppose one can assume I have a BS degree if I have an 
MS...  Perhaps if I remove that degree and use super action statements 
and other suggestions above, I can still squeeze this resume into two pages.

> 11) the sentences at the top of page 2 don't have bullets

I believe these sentences continue the last bullet from the previous 
page.  I'll double-check.

Brandon Stout
http://mscis.org