Resume advice needed!

[annathepiper]

Okay, so I'm taking some strong advice from solarbird and doing the first major overhaul of my resume in several years; I'm completely rewriting it from scratch. I still want to call out my localization engineer and software tester experience, but I also want to figure out how to make my years of personal experience with Linux, courtesy of running murkworks.net, sound good.

Here's what I know how to do on Linux. How much of this should I call out?

1. I'm specifically familiar with Debian Linux because that's what we run. In days of yore murkworks.net used to run on Slackware, but I can't really call myself familiar with that flavor of Linux.
   
2. I can configure system-wide services. Examples: Apache, Mailman, MySQL, PHP, Samba.
   
3. I can do Debian package installs. I can install already built packages, and I know how to build them from source and install them locally. I can track my way through dependencies in package installs.
   
4. I can compile and install system-wide programs from scratch, given source install packages to build. Example: Pine.
   
5. I have basic competency with batch files of various flavors. Given an example of an extant shell script, I can figure out what it does and modify it and learn how to write my own.
   
6. Previous statement also applies to Perl, with which I have very basic familiarity. I haven't written anything extensive in Perl yet.
   
7. I have considerable experience coding in PHP, specifically with setting up web pages to pull stuff out of MySQL databases.
   
8. I'm comfortable with most if not all basic Linux shell commands.
   
9. Basic DNS configuration (adding new machines on the local LAN to our DNS files).
   
10. User administration, creating and deleting accounts.

Dara also says I basically need to call out "co-run small co-op ISP", which is true; it is a job, Dara and I just don't get paid for it. I have this suspicion that if I try to just stuff all this under "Skills and Qualifications", it'll get dismissed somehow as "something I've just fucked around with a bit", and that's just not true. Murkworks.net has, after all, been up for years!

So how do I take all of this and roll it into my extant 'localization/testing' resume? That overall flavor of job is still what I'm looking for, I just want to be able to leverage my Linux experience into the mix to sound good for prospective Linux testing jobs.

Comments

[howlinhobbit.livejournal.com]

My first "high tech" job was phone support at Micro$oft. When I heard about the job I had no resumé whatsoever.

However, at the time I was running a somewhat popular BBS on an antique DOS box and had learned to program in BASIC in order to write stuff for the thing.

I simply put those "qualifications" into the resumé (putting the best light spin on them I could) and I indeed got the job.

In fine, reduce the verbiage a bit but put all that in.

Just my tuppence.

HH

[annathepiper]

This is essentially what I wound up doing. I already had running murkworks.net under 'Work Experience', to try to emphasize that this is more of an unpaid job than a hugely overblown hobby (though you can easily argue the latter ;) ), but I added a new 'Debian Linux system administration' section to my Summary of Qualifications, and condensed all of the stuff I listed down into a bite-sized chunk.

Hopefully this'll help! Thanks for chiming in. :)