Subj : SeekJob keywords (was: How much should I charge for fixed-price...) To : comp.programming,comp.lang.java.programmer,comp.lang.lisp From : rem642b Date : Wed Aug 24 2005 09:03 pm > From: Tim X > in larger organisations, the initial culling of applications is > usually done by some junior staff member from the HR department - they > know nothing about programming, computer or IT. They have a list of key > words or criteria which they look for - those that have it get to the > next stage, those that don't get filed in the round filing cabinet > under the desk! So would you recommend the keywords be listed in logical sections, such as programming languages in one list, platforms in another list, application areas in another list, etc., or should I just mix all the unrelated keywords together in one huge alphabetical list to make it easy for the junior staff member to find the keywords he/she is looking for? Given my experience, which keywords from my various resumes should I keep, which should I flush, and which keywords do I not yet have but based on my experience I should include as synonyms for the non-keyword descriptions I already have? To save you the trouble of looking through my dozen resumes, here's the complete list currently: 1620 360/370 6502 68000 8080 acia algol altair 8800a anti-spam applet archie arpanet assembler awt bachelor of science degree balanced binary trees bitmapped image of graph to parameterized lineaments bitnet blockade puzzles for 3-yr-olds or dan quayle bnf-driven type-checking c c++ cai calculus canonical representations card input cgi class-assignment client/server telecommunications clustering cmucl cobol college graduate combinatorics computer-assisted instruction console typewriter consumerism cross-reference data compression ddt dec pdp-10 destructuring device interfaces diablo disks diet optimization differential algebra differential polynomials dm2500 emulator docindex dom eqd expert system file maintenance and indexing finger flashcard drill forth fortran four-phase iv/70 fractals frontpanel ftp gcd generalized computer dating graph hockey gui hashing heapsort help-net hermes high-level languages html hypercard hypertalk i/o device interrupt handlers ibm 1130 ibm 1620 ibm 360/370 image processing imsss indexing info-nets information retrieval and indexing intel 8080 interval arithmetic interval refinement stochastic mapping inventions its j2ee j2se java javadoc javascript jdbc jsax jsp jsys kermit large prime numbers lattice manipulation laying out text linux lisp listserv maasinfo machine language macintosh macintosh allegro common lisp macl maclisp macsyma mail mainsail mathematical research mathematical-formula printer mathematics mathprinter mensa meta-index microsoft windows mos 6502 ms-windows natural language understanding net-relaxation netnews netscout nmr relaxation note nuclear magnetic resonance relaxation numrel nutritional diets. odbc opacs os traps packet-based data communication packet-based telecommunications pacs-l payroll pcnet pdp-10 perl permutations php pnews pocket forth portable standard lisp porting pre-registration prettyprinter principal differential ideals processing and rendering remote-sensing multi-spectral images programmer/analyst proofreading proximity-hashing pseudo-random numbers psl putnam contest pvm rdrlist redhat linux reduce rlisp rmail rmi rn rsa cryptosystem rscs s-expressions sail save/restore environment sax segmat servlets sesame c shortanswertests single-step debugger sl software engineer sokoban puzzles for 3-yr-olds or dan quayle sort/merge space exploration sprouts standard lisp stanford stipple sunos svc202 commands swing syntax&semantics checking syscalls telecommunications telnet tenex terminal emulation text compression toolbox traps topindex toplevel meta-index tops-10 uci-lisp university payroll university pre-registration unix us citizen usenet uuo vb versaterm virus detection and removal visual basic visual c/c++ vm/cms waits wilbur word problems wordprob writing & public info www xml zmodem zterm So which of those are so grossly obsolete that there's no chance anyone will ever want somebody with such experience, so I should permanently delete them from my keywords list? Which new keywords did I overlook? > All of that could have been summarised as something like x years > assembler programming. Which is better keyword for that: assembler or assembly-language? Or should both be included in case the junior staff member is looking for the other one and doesn't realize they mean the same thing? (Splitting my reply here, in case anyone stopped reading at that list of keywords and wouldn't see the rest of the topics I'm discussing later in the second part of this reply.) .