Internet Jobs Tips & Traps

Job Search Tips For Candidates, Recruiters,
Job Banks, and Spiders

Disclaimer: the information herein is the personal opinion of Gilbert Healton. It does not reflect any official standing of any organization.

Gilbert retains the right to revise, withdraw, or attack his previous ideas at any time without advance noice.

by Gilbert Healton

2003-06-17 14:12:07

Copyright 2002 by Gilbert Healton.
All rights reserved. Contact the author for commercial reproduction rights.

Table Of Contents

1. Audiences
2. Introduction
3. Definitions Used In This Document
3.1 Job Banks
3.2 Job Spiders
3.3 Zombie Jobs
3.4 Duplicate Jobs
3.5 Date Formats and ISO 8601
4. Tips For Job Searchers
4.1 Defending Against Zombie Jobs
4.2 Duplicate Job Awareness
4.3 Use Professional Sounding E-Mail Addresses
4.4 Don't Make Dumb Responses
4.5 Defend Yourself and Your Resumes
4.5.1 Keep Records
4.5.2 Preserve Your Identity
4.5.3 Hosts Not To Trust
4.6 Listing Resumes On The Internet
4.6.1 Where To List
4.6.2 Job Bank Listings
4.6.3 Personal Web Pages
4.6.4 Listing to Internet News Groups
4.6.5 Keep Resumes Fresh
4.6.6 Resume Blasting Services
4.6.7 Careful What You Post!
4.7 Due Dilligence Checks
4.8 Also See
5. Immediate Tips For Recruiters
5.1 Defending Against Zombie Jobs
5.2 Easy To Find Job Listings
5.3 Badly Written Job Title Lines
5.4 Nicely Written Job Titles
5.5 Badly Formatted Listings
5.6 Badly Written Requirements
5.7 Nicely Formatted Listings
5.8 Posting To Newsgroups
5.9 E-Mail Tips
5.9.1 Looks Count
5.9.2 Subject Lines
5.9.3 Message Layout
5.9.4 Cold Contacts
5.10 Confidenciality Notice
5.11 External Hosting
5.12 Review Your Postings On Major Job Banks
5.13 Also See
6. Immediate Tips For Webmasters
6.1 Defending Against Zombie Jobs
6.2 Search Engine Power
6.3 One Job Posting Per Page
6.4 Static Listings
6.5 Unique URLs
6.6 Frames Can Make Problems
6.7 Ensure Phone Number Sites Know Your Company
6.8 Track Who Is Applying
6.9 Also See
7. Immediate Tips For Job Banks and Spidermen
7.1 Stopping Zombie and Duplicate Jobs
7.2 Honor Expiration Dates
7.3 "Last-Modified Dates Can Not Be Trusted
7.4 "Verify Job" Links
8. Medium and Long Term Proposals
8.1 Resumes vs Job Postings
9. Job Site Ratings

1. Audiences

This document is intended for the following audiences.

  1. People looking for jobs on the Internet.
  2. Recruiters and Human Resource personnel posting jobs on the Internet.
  3. Webmasters for sites posting jobs on the Internet.
  4. Authors of web spiders that seek out job postings for job banks.

While this document is biased toward my own job search requirements it should still be useful to many people in computer related fields. While I am a citizen of the United States Of America I do try to pay attention to Internationalization issues. If your profession is well represented on Internet job postings this document should be useful to you.

2. Introduction

Sadly I have been one of those high-technical people looking for work since before the fall of the twin towers. Happily my compulsive writing habits tend to leave document trails on subjects not covered well elsewhere and I have followed through on a document I hope will help others in their job searches. You are about to read my personal thoughts and observations on efficient use of the Internet in several job arenas..

Each audience I have written to has their own section, or perhaps sections, in this document. Use the heading to find the sections you are interested in.

Repeating mistakes or problems at computer speeds does not help searches by candidates and recruiters difficult. Both recruiters and searches waste large amounts of time for something this author calls "zombie jobs". All people using the Job lanes of the Internet highway should know about zombie jobs. If I could fix one problem with the Internet job searches, it would be to eliminate what this author calls zombie jobs.

Hopefully I have gathered useful information from other places mixed in with my original ideas and observations. For additional links please visit my web page at:

http://www.exit109.com/~ghealton/.jobs.html

3. Definitions Used In This Document

3.1 Job Banks

A collection of jobs gathered from different points on the Internet. Most job banks, especially the comprehensive ones, gather most, if not all, of their listings from "job spiders".

3.2 Job Spiders

A program that searches the Internet for job postings. These work much like the general spider programs used by search engines, such as Google. However job spiders are specialized to look for job related information. These type of programs are also called "robots" and "web crawlers", however this author thinks "spiders" are is more fun.

Most job banks use job spiders to discover most, if not all, of the jobs listed in the job bank.

3.3 Zombie Jobs

Even half-serious job searchers with a feeble talent of observation soon become aware of the fact that many job positions listed over and over in job banks have serious problems with them. This includes a great many jobs that have been filled ages ago. Even years ago. The job opening closes, but the listings live on, complete with new post dates. This author calls such job postings "zombie jobs."

A great deal of the jobs on the major search engines are zombie jobs. Perhaps the majority of listings. Responding to zombie jobs is usually a waste for both candidates and recruiters along with a waste of disk space at job banks. Identifying and skipping postings for zombie jobs when searching for jobs is perhaps the biggest trick to saving time for. Recruiters defending their postings against becoming zombies will have many less replies to old postings.

Recipes for creating zombie jobs follow. While the following uses the names of real sites that post zombie jobs these sites were also picked because despite their zombie problems, they remain very useful sites that I frequent on a regular basis.

Many recruiters receive vast amounts of E-mail from candidates applying for these zombie jobs. For many recruiters the only defense is to simply delete the applications without any response whatever. All the time and effort put in by the applicant vanishes without a trace. During recessions I suspect there are days the fingers of some recruiters wear out pushing the delete key.

Why "zombie" jobs? Well, badly written UNIX programs can produce "zombie processes" in the computer. These are jobs UNIX is still tracking even though they are dead. Zombie jobs usually stick around forever until the system is rebooted. As I am a UNIX guy the concept of "Zombie jobs" on the Internet came naturally to me.

3.4 Duplicate Jobs

When recruiters do not have an exclusive line on a job many different recruiters may post the same job. If the words between postings are identical to the original posting the jobs may be easily recognized by the observant. If the wording is different readers can only be suspicious.

Worse is when different postings for the same job are written in ways that make job spiders think each description is a new job. Such spiders list the same position, from the same web site, as a new posting with each visit. This adds a lot of clutter to the job listings. This is perhaps the second worse plague for Internet job searchers.

3.5 Date Formats and ISO 8601

As web documents are truly international in scope, and good job banks have readers from all over the world, web pages should reflect this. A particular problem is different nations use different date formats. Confusion can occur when a person of one nation reads a date written in another nations format.

Using dates in the format yyyy-mm-dd on web pages, as in 2002-08-15, month an day always being two-digits long, is strongly suggested by this author. Such dates follow International standards for writing dates (ISO 8601).

Visit http://dmoz.org/Reference/Time/ for many useful links about ISO 8601.

Visit http://www.exit109.com/~ghealton/y2k/yrexamples.html for writings from this author on ISO 8601.

4. Tips For Job Searchers

4.1 Defending Against Zombie Jobs

When reviewing the results of a job search a few careful mouse clicks can verify if a job might be open or not.

It is very important to backtrack the job to the original web site offering the job to either the recruiter posting the job or the company itself. Backtracking the posting to yet another job bank is not sufficient. The only way to be sure you are back at the original site is to look at the address in your web browser as some job engines save the original page in their memory. Such snapshots only show the page as it was when it was spidered, and not as the page is now.

Some employment agencies and recruiters contract with a particular job bank to host their job listings rather than maintaining them on their own servers. Decent job search software is complex and having another company maintain it allows recruiters to dedicate their resources to recruiting. Going to the company home page to drill down to career opportunities will drop you into the job bank dedicated to that company. Such job bank postings can be considered to be the original postings.

4.2 Duplicate Job Awareness

The key to spotting duplicate jobs is noticing job listings posted within a few days of each other whose descriptions are virtually identical to each other. Applicants may still wish to submit themselves to both recruiters while taking particular care that only one recruiter will submit them to the actual company (the first one to offer wins!) The hazard is that having two or more submittals from recruiters is a sure way to ensure you do not get the job as hiring companies don't want different recruiters arguing over fees if you are hired. Companies tend to shy away from going with either recruiter to avoid court battles.

4.3 Use Professional Sounding E-Mail Addresses

Do not use your employer's E-mail address or web pages when seeking work. If you do not have a personal ISP you want to use go to one of the free E-mail services. E-mail addresses on resumes should professional and not be overly cute at strange. hotlipsyahoo.com may make people wonder about what type of job you are applying for.

4.4 Don't Make Dumb Responses

When responding to a job,

4.5 Defend Yourself and Your Resumes

4.5.1 Keep Records

Keep tight control and good records about what companies your resume is being sent to. Include when you sent it, what job you applied for, and to who or how you sent it. If your resume is received at a company from multiple recruiters the company may well drop you from their list rather than having recruiters arguing over who gets the fee. Expressly ask recruiters about retaining control over where they send your information if their web site does not expressly claim they keep resumes in confidence.

4.5.2 Preserve Your Identity

Preserve your identity by not posting your address on the Internet. Some state that phone numbers should not be posted as well, though anyone wanting to look up a person's phone number can to so on the Internet unless the number is unlisted.

Identity theft, and its potentially dangerous outcomes, is a serious, and growing, threat. It is so easy to do, and so difficult to recover from.

Never ever publish very private information, such as social security numbers, the size of your family, and if you are single (sadly, especially single women). Even things like the number of children can draw the attention of undesirable people.

4.5.3 Hosts Not To Trust

Be extra wary of web sites that:

4.6 Listing Resumes On The Internet

4.6.1 Where To List

While networking with people you know can still be king for any job search, technological jobs, especially computer related jobs, are well served by the Internet. The following ways are major Internet arenas for posting resume:
  1. Job Banks

  2. Personal Web Page

  3. Resume Blasting Services

  4. Internet news groups

4.6.2 Job Bank Listings

Posting resumes on job banks can be very useful. Many job banks make money by having recruiters subscribe to them to search these jobs. Here you may want to limit the places you have active resumes to a small number of locations. Another trick is to have substantially different resumes on different job banks.

Many job bank resumes are key word oriented. Getting all the important keywords into your resume as often as you can is important.

4.6.3 Personal Web Pages

Posting an account on your personal account with your personal ISP is a truly excellent idea. My current idea is to only post on job banks when you are seriously looking, which can include being seriously afraid of your job existing in the near future. But private web pages should always be active. If you are not looking, say so, in a "Search Status" heading at the top of the page. When not looking all personal information, except for E-mail address and name, should be omitted from your on-line resumes.

The reason personal web pages are so important is it takes spiders several months to find your web page during general searching. In order for spiders to find your web page multiple other web sites the spiders already know, or can find, must hyperlink to your web pages. There are also free posting services, such as http://www.ineedhits.com/, that can post your web site. In times of sudden need it is nice to have already been found.

Having something on your web tree that attracts a good number of hits each month helps raise your priority with some search engines. The subject can be hobby, professional, or other interests. Using the <META...> tags in HTML also helps some spiders better catalogue your pages. If you don't know META tags, talk to a friend that does.

If you don't want to appear to be looking for a job, but still want to have your resume found by search engines, several tricks are available.

4.6.4 Listing to Internet News Groups

The misc.jobs.resumes news group is dedicated to resumes. Before the web came into existence the news groups were the place to post resumes.. However news groups tend to be more difficult to search then web site search engines. I suspect spiders are the only ones that read all of misc.jobs.

These newsgroup posts need to use neat ASCII text as they do not take well attachments, images, pictures, Microsoft Word documents, etc. If at all. Job seekers should only occasionally post to the news groups.

Read the FAQ for the news group (Frequently Asked Questions) before posting to any newsgroup. Always following the posting guidelines if you want respect.. Reading the news group FAQs may prove helpful before beginning to build your personal web page.

Talk to your local system administrator or ISP about connecting to the news groups. If you have a blind E-mail address somewhere posting to news groups can be a very anonymous way of publicly posting your resume on the Internet.

4.6.5 Keep Resumes Fresh

Wherever you post your resumes it is important to keep them "fresh". The age of resumes in job banks, on web pages, and the last post date to any news groups, impact the search priority. The older the resume the further down it will be on the "hits" returned by searches made by people trying to fill jobs.

All web sites need to do is have one character change on them to be "fresh". Delete or add a comma. Move two skills around in your skill list. Any old change works as long as something other than "white space" changes (white space is the space between words, at the end of lines, and between lines). Changing your resumes once each week or two seems to be the popular recommendation.

If you simply save the old resume again, without changing anything on it, some places will notice nothing really changed and leave you at the old priority. Some may be smart enough to throw away only changes to white space (any I wrote would be!).

4.6.6 Resume Blasting Services

Various services, for a fee, will send you resume to thousands of recruiters. I'm not really sure how good of an idea this is and would love to get feedback from job searchers and recruiters who have used such services.

4.6.7 Careful What You Post!

Once the spiders start finding your web site anything you list will be remembered by the spiders. People searching for keywords will see your words in their result pages for many months after you delete the information. Some search sites retain information for years after it was deleted (I suspect this is a bug).

Then there are the archive sites such as http://www.archive.org/ that intentionally remember old web pages so users can surf the web the way it was. Dishonest spiders find old sites this way... And anyone can review the way your site was in the future.

The moral of this story is any place your name, and other information, appears on web pages, address books, and more, will be remembered long after you whish it was gone.

4.7 Due Dilligence Checks

A bit of "due dilligence" checks are appropriate before sending out priviate information to recruiters or companies. A lot of pirates are lurking out there under the cover of people with jobs.

Your checking should include the following Internet tests:

4.8 Also See

Section 8, Medium and Long Term Proposals, contains additional ideas on making the Internet a friendlier place for seekers and posters of jobs.

5. Immediate Tips For Recruiters

This section should serve both recruiters and Human Resource personnel posting jobs to the Internet.

5.1 Defending Against Zombie Jobs

There is no one thing you can do to prevent web search engines from making zombies from your job postings. The best defense is to use the following tips that help organize your web pages in ways spiders can extract information out of them and for canidates to easily verify jobs are still open.

Information providing very important identifiers, such as job id and a verification web hyperlink address, should be repeated in the main description of your job listings. Some spiders discard headings they do not understand. This results in information vital to preventing zombies, or recognizing those that get started, much more difficult. Having this information duplicated in descriptions makes it more likely even badly written spiders will keep it. Including such redundant information in paragraphs providing regular description text help to improve the chances preserving this critical information.

5.2 Easy To Find Job Listings

If you want people to find your jobs your web site must be easy to navigate when it comes to finding jobs. Both people and spiders must find it easy to navigate your web site.

People want to find details about potential jobs. If you have many jobs some type of search engine would be very helpful.

Spiders work best with plain web pages. If these pages are organized by so people can drill down into them by job type, so much the better. "Plain" pages are web pages that are both fairly simple in their design and are accessed by simple links without the use of forms, Flash, Java, JavaScript, or any thing else that tends to block spiders.

If web listings of your openings are provided by an outside hosting service, then have easy to find links to that hosting service on your web site. Having a link that returns "all jobs" is vital for proper spidering.

5.3 Badly Written Job Title Lines

The better sites provide a short one line title for each job. Intelligently written titles make wonderful headings for people to search by.

The following shows two titles for the second job. The second one will attract more of the talent you are looking for.

senior developer, Difficult Staffing, New York, NY

Sr. Developer, Manhattan, UNIX, perl

Help on writing good titles follows...

5.4 Nicely Written Job Titles

When writing one-line job titles attracting people with the desired talents is your goal. Think of writing talent bait, not English sentences. You are not seeking good grades from your old English teacher but responses from good people. Prioritize the information in the line so the most important requirements or qualifications come first.

A very short job title (e.g., developer, administrator, Electrical Engineer) followed by the key requirements of the job are recommended. Industry standard abbreviations may be freely used in titles. The goal is to allow titles to be quickly read yet strongly draw attention of the desired people.

If you must identify your company in the posting, put it last and keep it very short.

Note that formal job titles are intentionally being avoided. Many industries have job titles too vague to be practical. Titles like "Organic Chemist" and "Software Engineer" provide no real information about the job. Unless the job title is unusually specific (Kindergarten Teacher) effective titles need details on what is being done rather than what Human Resources calls it.

5.5 Badly Formatted Listings

Keep the subjects in your posting clearly separated. Using official web page headings can help here (top level headers show up as <H1> in HTML).

Use conventional paragraph breaks (<P>). If you use some type of fancy break the spiders may not see it and put much, if not all, of your posting into a single sentence. Such are very hard for candidates to read.

DO NOT USE ALL CAPITAL LETTERS. SUCH IS CALLED "SHOUTING" AND LARGE AMOUNTS OF IT IS CONSIDERED RUDE. MOST PEOPLE ALSO SUCH PARAGRAPHS MUCH HARDER TO READ. USE ITALIC AND BOLD TO EMPHASIZE WORDS. BULLET LISTS AND VERTICAL WHITE SPACE IS ALSO NICE. ALL CAPITAL LETTERS GOES BACK TO THE DARK AGES OF COMPUTER PRINTERS WITHOUT LOWER CASE LETTERS, AND EVEN TYPEWRITTERS. TO SERIOUS COMPUTER USERS IT REEKS OF NAIVETE.

When writing web pages make it easy to read on the screen. Spending too much effort on making printouts look nice can be counterproductive.

5.6 Badly Written Requirements

One of the worst offenders is to place "See job description" in on a web page form, or not including a requirements section. Job seekers searching "requirements" fields will never find your job unless the spider is bright enough to extract the requirements anyway.

As a job seeker I have given up searching requirements fields, or job description fields for this very reason. Full body searches are the only reliable way to go, yet many seekers only search the shorter fields and miss a lot of jobs.

5.7 Nicely Formatted Listings

When posting job openings you need to format each web page for two different audiences:
  1. Applicants: the people you are trying to recruit.
     
  2. Job search spiders: these programs scan the web to find job postings. Such postings are made available in large job banks. Dice, Excite, and Monster are among the many job banks spidering the Internet.

Job postings not properly scanned by spiders are not properly shown to the Internet at large. To ensure your postings are widely distributed follow KISS: Keep It Simple Stupid!

  1. Review: Review three or four of the major job sites to search for jobs like the ones you are posting. Observe the keywords (e.g., Requirements, Description, Location) used on most, if not all, of these sites. Using these keywords in your job postings help spiders read your postings.

    Using creative keywords or ways of describing your job to catch the attention of readers may greatly reduce the number of people reading you posting if the job spiders don't properly catalog it. If you want to be fancy one place, KISS up in another location.

  2. Format: If you want to use "table format", only use two column tables containing a keyword and the associated text. Only one item per-row in the table. A colon after the keyword can be a good idea.

    Another popular format is to have a "keyword", colon, then a description.

    Job description:
    A description of the job.

    Use a paragraph break (<P>) before the keyword to get extra spacing above the keyword. Use a simple line break (<BR>) between the keyword and the next line, if you want a break.

    However you format the posting, be consistent throughout the entire posting.

  3. Prioritize: The salary, start date, technical information about the job, location, and other subjects that applicants tend to search for should come early in all postings. Any broiler plate describing benefits, how great the place is to work at, and other quality points, should appear after the information most applications will be searching for.

    When searching for jobs with search engines many engines return summaries of the job by including the opening paragraphs of the posting. Having nothing but "standard garbage" in search results makes things difficult on your potential applicants. And this decreases the number of people that take the time to drill down to the details needed to make decisions.

  4. Keywords: Be sure to have keyword headers before each section of the job posting. Extra vertical white space never hurt anything here.

    Popular keywords follow in alphabetic order of the main keyword. You should tend to order them by importance to your posting. Obmit headings you really don't need. This author believes headings shown in bold should always be present.

    Area Code: Telephone area code. But remember it is useless in states like New Mexico that have one area code for the entire state.
    Company: Name of the company or organization posting the job opening. If you are a recruiter it may help if you end it with "(recruiter)".
    Title: A one-line heading. Rather than using an English sentence here a short list of the more important requirements may be more effective at describing what you want. More information on titles can be found in 5.4, Nicely Written Job Title Lines. Readers may find more information in the Description and Requirements sections.
    Position: The actual title of the position, as Human Resources and the rest of the industry call it. This should appear early in your detailed description. Likely before the detailed description.
    Description: A longer, detailed, description of the job.
    Education: What level of education is absolutely required. Is there an "or equivalent" option given to people with long established track records? Remember some people have been in industries before degrees were available in the field. Phrases like "fifteen years of professional experience may be substituted for a degree" can attract these experienced people.
    Job ID: Some code uniquely identifying the job. This is somewhat useful to people and enormously useful in helping spiders catalogue your postings.

    The most useful IDs are all one word, start with letters, and contain only letters and numeric digits. This makes ids look like words that regular search engines can search for. Hopefully your website provides a "find job by job id" feature or simply allows the job id to be found by your local search engine as with other keywords.

    Length: Length of contract jobs. You may omit or enter "n/a" for full time postings.
    Location: A description of the job location that is accurate enough to give potential applicants an idea of the commute time to the job. For states with area codes that cover smaller areas this may include phrases like "Area code 212". Stating the county can also help.

    Include the nation the work site is in, even if it is obvious to people. to help job spiders reading your web site. A direct hiring company may put their complete address if desired.

    Zip code and area code locations should have their own keyword, likely immediately after "Location:", as these are two keys job spiders often look for.

    Rate or Pay Rate: Pay scale. Low, high, and any bonuses are one way.
    $80,000 - 120,000 + Bonuses
    Another is to state the minimum salary: $80,000+.
    Responsibilities: A description of what the job will entail.
    Required Skills or Qualifications: A detailed list of the required skills, experience, knowledge, industries, etc., that without which applicants will not make the first cut.

    Using bulleted lists can be nice here as it makes each point stand out. It also makes each point easier for job spiders to find and catalogue. Making this list easy for job spiders to read is important as most people searching for jobs use keywords.

    If you do not use bulleted lists, be sure to separate listings with commas or semi-colons to help mark each point. Remember, dumb job spiders must be able to separate out the requirements.

    Absolutely vital requirements should also be in the title line. They may be cryptic, but there. The line should be limited to 60, maybe 70 characters, including spaces, periods, commas, etc. You may condense things by omitting spaces after commas.

    Requirements includes any industry requirements. If you only accept candidates with five years of financial experience, then at least put "finance" or "finance+5" in the title. If a specific area of and industry is desired use that in the title ("bonds") rather than the general term.

    Preferred Skills or Qualifications: Skills that are desired, but not absolutely required. Strongly preferred skills may wind up at the end of the title line.
    Tax Term: Describes how this job will work. full-time, consultant w2, corp-to-corp, 1099, etc.

     
  5. The following keywords should be used more often then they are.

    Date Expires: Date the job posting is expected to expire. Pick a date that is the expected close date. You can always extend it if needed later on.

    While not many spiders look for this right now, my hope is that if expiration dates get popular spiders will start looking for them and, when the expiration date hits, go back to verify the job is still open. Even without such spiders it will help regular people become aware that this may be a zombie job.

    Date Posted: Date the job was originally posted on your web site.
    Verify Job:
    (a.k.a. Original Posting)
    This is a hyperlink to the job posting on your own web site. If there is any one way to fight zombie jobs, both by applicants reading jobs and spiders looking for jobs, this is it.

    If the job is not there it would be wonderful if your web server was smart enough to indicate "position closed".

    This author favors "Verify Position" over "Original Posting" as "verify" sounds more in the self interest of readers than "original" and is more likely to be used by readers. This use allows your web server to better track where your effective job postings are being distributed.

    Travel: Some hint of any travel required for the job. "none", "rare", "local", or some percentage, are possible values.

To this end, having a simply formatted job posting

The following can be important to include in your text:

5.8 Posting To Newsgroups

Along with posting to your local web pages and job banks the misc.jobs news groups are also dedicated to job related information. Before the web came into existence the news groups were the place to post resumes.. However news groups tend to be more difficult to search then web site search engines. I suspect spiders are the only ones that read all of misc.jobs.

These newsgroup posts need to use neat ASCII text as they do not take well attachments, images, pictures, Microsoft Word documents, etc. If at all.

Read the FAQ for the news group (Frequently Asked Questions) before posting to any newsgroup. Always following the posting guidelines if you want respect.. Before posting anything on newsgroups recruiters are advised to search the groups to see if the job banks listing their jobs, especially any they subscribe to, have already posted their jobs to the news groups. If not recruiters may be well served by just posting their priority jobs, with links to their static job listings (see section 6.4, Static Listings) for spiders to find. Spiders should find the links to the static job page and take it from there.

Talk to your local system administrator or ISP about connecting to the news groups.

5.9 E-Mail Tips

5.9.1 Looks Count

A lot of serious Internet users collect a lot of unsolicited E-mail. Such SPAM includes scams, sexual advances, get rich quick schemes, bogus work at jome jobs, questionable business opportunities disguised as job openings, assorted pyramid schemes, morgage requests, virus attacks, and more. It doesn't take long for people getting twenty or more SPAM messages a day to simply delete anything that looks likes SPAM without even opening the message. Only the subject line and "from" address in the list of E-mail is read.

E-mail that looks like it might be valid is usually kept of rejected by what is is the first screen of the message.

If your message looks like spam pollution it may well be treated like poison. Deleted without being read.

And think about it... people who seriously use the Internet as well as working with computers on their job may be just the type of people you want to reach. So...

5.9.2 Subject Lines

Generic titles such as "About your resume", "Hot job", "hello", are to be avoided. Rather be specific about the details about the job, if you have one. Be sure the subject line looks nothing like the spam and other automatically generated E-mail that pollutes E-mail in baskets.

5.9.3 Message Layout

Any standard broiler plate text should be at the very end of the E-mail. Put the information the person deleting E-mail feel is important to read first. As far as my E-mail goes, most messages opening with hype it go directly to the trash.

Xyz Consulting is a leader in the field of...
DELETE! Nearly every company claims to be a leader in something.

Xyz Consulting provides excellent benefits
DELETE! Every serious high-tech job has some benefits.

Xyz Consulting has over $$$$$$
DELETE!
Who cares? Do you have a job that matches my skills?

5.9.4 Cold Contacts

When sending cold contact E-mail, or renewing contacts with people after passing time, looking good is more important then ever. If the people you are E-mailing to are not expecting your E-mail, it is vital to make the mail look useful to them. Better yet, actually make the opening text useful to them.

If you are E-mailing a job position to some one, if there is a deadline for submitting resumes, include the deadline in the E-mail.

5.10 Confidenciality Notice

If you are one of the "good guy" recruiters that do not distribute information found in resumes to your corporate clients without the express permission of the candidate, expressly state this where it is easy to find. This statement should be repeated on web pages visitors seeking jobs will naturally go through when using your site.

5.11 External Hosting

If you use a third party to host your job positions, the site should have a good search engine behind it. Section 6.2 goes more into search engine features.

Further static job listings on this page must allow other spiders to post the jobs if you desire the widest distribution of your postings.

5.12 Review Your Postings On Major Job Banks

Seeing what your posts look like on other job banks once the various spiders are done mangeling your original posting can be very educational. It is the only sure way to know you are formatting your postings in ways that are effecive with other spiders.

If your postings are being mangled, and job banks often mangle your pages at least a little, look at postings from other companies in the same job bank. If every posting is being mangled do not feel bad as it is the job banks problem. But if only your jobs are mangled, you better do some research on why your pages are different from other posters.

Also look at your web pages using different browsers. Different browsers treat the same pages differently so using only the browser on your desktop to review your web pages makes you blind to what many people will see. Some services, such as http://www.netmechanic.com/ not only validate your web pages to be sure the technical details are correct, they can also quickly show you what your web page looks like on different browsers. This becomes more helpful when posting computer jobs for people that use operating systems other than Microsoft Windows®.

5.13 Also See

Section 8, Medium and Long Term Proposals, contains additional ideas on making the Internet a friendlier place for seekers and posters of jobs.

6. Immediate Tips For Webmasters

The following ideas can be implemented regardless of what the rest of the web is doing. Your own bureaucracy is your own problem.

In addition to this section webmasters really should read section 5, Immediate Tips For Recruiters.

6.1 Defending Against Zombie Jobs

Webmasters have their work cut on in defending their sites against zombie jobs. This work is mainly keeping your site spider friendly and making it easy for visitors to your sites, and the copies of your site spiders cache on their own servers, to verify your jobs are still open. This later point is very important.

Many of the suggestions involve ideas that help defend against zombies.

6.2 Search Engine Power

Decent search engines have the following characteristics:
 
  1. Bad Token Parsing: Failure to extract quoted tokens, or strange tokens such as C++, can greatly degrade usefulness.
  2. Poor Boolean Search: The option to use words like AND and OR to better select keyword options. Parenthesis should also be accepted to group keywords.

    (unix OR linux OR solaris OR sunos OR aix) and (c OR c++ OR perl OR dhtml OR html OR web OR sql)

    When posting jobs for computer programmers, or other people that use "logic" in their jobs, you should really let them use it on your web site.

  3. Search Strings: Search strings should allow over a hundred characters in expressions. Only allowing twenty or so characters makes it much harder to use the search engine. Search engines should allow for nested parentheses. At least four levels of them.
     
  4. Result ordering: The search engine should be able to order searches by several options. Post date and hit ranking are the most important.
     
  5. Geographic Restrictions: Search engines should be able to control searches to areas within a state... to at least the area code or first three digits of the zip code (beware that some states have only one area code for the entire state).
     
  6. Not including job details. One of the worst offenders are sites that show very little details about the job. Readers that don't want to respond to mostly blind postings tend to abandon such sites.

6.3 One Job Posting Per Page

Readers viewing your pages should be able to drill down to additional details. The final level should have just one page per job. This should really help job spiders keep the jobs straight on your web site. Spiders can be confused by multiple jobs on a page. If you must use post multiple jobs each job should be in a division (e.g., HTML <DIV> ... </DIV>). A less useful alternative is to place a <HR> horizontal rule between jobs.

The web address (URL) to this final job posting should not be some long and ugly thing that can only be obtained from a search engine. Each posting should include an "Validate Job:" links that contains the URL to the web page listing the job. If another labels is used included text along the lines of "verify the job is still open before responding." For shorter versions "verify job" may work. On your on web site the link would be toward the same page. This helps reduce people responding to closed jobs when people respond to old copies in job banks.

It would be wonderful if attempts to view closed jobs returned an appropriate message to the visitor. Another idea: if your web server notices a reference to your job page from your job page it could give a special "position is still open" response rather than repeating the same information.

http://www.yourdoman.here/cgi-bin/view?job-number

6.4 Static Listings

A summary of all jobs needs to be available that job spiders can find. Chasing links to these jobs should wind up at the full text for the individual jobs. Making jobs available only via job searches is a great way of hiding them from job spiders, and the rest of the Internet world.

6.5 Unique URLs

Each job listing should have a unique URL. You should not have multiple URL's list the same job. This can make job spiders believe you have more jobs open than you do.

6.6 Frames Can Make Problems

Use of frames on web pages (talk to your webmaster if you do not know what a frame is) tends to cause problems for people, and spiders, wanting to come back to, or link to, your site. Frames almost always makes it unpractical to have fairly simple URLs reference each job, as described in the previous paragraph. If you must use frames, be sure the final job pages do not use them or people can find it hard to return to them.

Have you ever spent a long time exploring a site, saving a few book marks for the pages you want to come back to, only to find the book marks take you to the top level home page? You then have to drill down all over again to get the desired information, if you can remember how you got there. This problem is brought to you by unimaginative use of frames.

6.7 Ensure Phone Number Sites Know Your Company

Phone numbers posted on web pages should also be known to the major sites providing reverse phone number lookups. Sometimes jobs being passed on to people only have a phone number, maybe a FAX number, on them. This is very true for job banks that strip all web based information from what they show users.

Some sites providing reverse phone listings can also provide the URL to your corporate home page. If the phone listing provider knows all of your published corporation phone numbers, people with just the phone number can obtain the URL by a reverse search.

A major player on the Internet providing both phone numbers and URLs is http://www.anywho.com by AT&T.

6.8 Track Who Is Applying

Track the E-mail address of all people applying to a particular job. Once the position is removed from databases generating your web pages send the applicants an automated message about the position being closed.

This allows candidates to strike you off their list of companies they are expecting replies from.

6.9 Also See

Section 8, Medium and Long Term Proposals, contains additional ideas on making the Internet a friendlier place for seekers and posters of jobs.

7. Immediate Tips For Job Banks and Spidermen

In addition to all webmaster tips, the following may prove useful to authors of job banks and job spiders.

7.1 Stopping Zombie and Duplicate Jobs

One great source of zombie jobs are job banks that let other job spiders browse there listings. Besides, do you really want other job banks using the fruits of your works?

There are two defenses against this. First is ensuring your job listings only appear from cgi-bins or other web pages built dymanically based on form submissions. This is perhaps the best defense.

The second defense is to have a robots.txt file that blocks spiders from your job listings. As the names of job spider domains is always changing it is not practical to block just job spiders. Yet blocking all spiders makes your jobs unavailable to standard search engines, such as Google.

On the other side or the coin, actively determine the web addresses of other job banks and teach your spiders to stay away from them. Considering the high incidences of zombie and duplicated jobs in many job banks, spidering your competitors may not increase your listings in a useful way. Rather it may contaminate your job listings with many zombie and duplicated listings.

7.2 Honor Expiration Dates

Honor any expiration dates, either for cashing or in the job description. Allow date formats to be in ISO 8601 format. Hyphens between dates are a good key that ISO 8601 is being used, especially if the first is a four-digit year.

7.3 "Last-Modified Dates Can Not Be Trusted

Any Last-Modified dates found in the HTTPD headers returned by web servers can not be trusted. Many web servers simply plug the current date and time in them rather than the date and time for the information within the page. This is especially true for servers that generate the HTML dynamically from data bases. While dynamic sites allow the very latest information to be included in responses, the web page Last-Modified date is very misleading when trying to determine the age of the information in the page.

If using the Last-Modified dates, where available, is important, compare them against the current Date in the header. If they are the same, or within minutes of being the same, it is unlikely the date can be trusted. Any web servers reporting the date of the latest change to the information on the page will have useful dates in them.

7.4 "Verify Job" Links

Automatially generate "verify job" links in the details about a job. This would call up the original job posting for review by the reader, or hopefully get a "not found" message from the original server if the job is closed.

Before archiving an original URL you sould verify that it truly calls up the original job if you repeat it. Running this test from a different IP address would be nice to defeat any special caching in your local systems or on the spidered server.

If you are one of those sites that can not stand the thought of exposing web contact information to your readers, at least internally test the results for your readers to ensure the expected job is still in the response. You can then reply with a "job appears open" reply, even providing an "as of" date from the any date header received from the responding system.

8. Medium and Long Term Proposals

This section presents concepts that would require enough people using them to make a de facto standard, if not an actual standard, to become useful. At this time these are more in the Request For Comments (RFC) state rather than proposals. Watch this space for the results of these comments.

8.1 Resumes vs Job Postings

The following provides key facts about a position that make it much easier for regular search engines, job spiders, and even actual people, to classify the posting.

Each job posting should have some magic words near the top of the posting. The following proposals are already Internet standards for newsgroups.

  .
misc.jobs.contract Contract jobs
misc.jobs.offered Actual W2 job posting
misc.jobs.offered.entry W2 entry level jobs.
misc.jobs.resumes Resumes by people looking for job. Should include "Resume for ...." or "CV for ..." depending on what it is.

The case of the letters herein would not be significant. These should be enclosed in some type of (parenthesis), {curly braces}, or [square brackets]. An alternative is to use a heading of "Posting Type".

Posting Type: misc.jobs.resumes

This would clearly identify if the posting is a resume or job posting. Job spiders would love it if this got popular.

Additional information may follow this keyword either under their own heading or within () parenthesis. Any HTML commands within may be safely ignored by robots or other programs scanning the text. The misc.jobs.xxxx heading must not have HTML commands embedded in it to make it easier for robots and other programs to spot. The idea is to have job banks and job search engines pick up these keywords to include them in their listings.

posted=yyyy-mm-dd post date, in standard international format (ISO 8601).
expires=yyyy-mm-dd Date job posting should be considered dead. If necessary you may renew the listing on, or a few days before, this date (overlaps helps keep listing alive).
id=your internal ID Your internal id for this job (no embedded spaces). If there is a company wide id, use that. Else use your initials, extension, etc., followed by some unique number, for the position. Any reposting of the position would continue to use the same id.

If multiple positions are open, separate them by commas (again, no spaces within). You may hyperlink each position to your job site to allow candidates to quickly verify the position and see the latest details.

Multiple keywords would be separated by white space characters in the HTML file, which does not include &nbsp; escapes.

If having such on your pages offends someone, place these within an <-- comment --> so it does not appear on the page.

9. Job Site Ratings

Recently I have been thinking about a rating system that would rate services provided by different job banks in a way that would be useful to job seekers. This section contains my current (half-baked) thoughts on the subject.

Only people interesting in helping this project should read on.

Has anyone else already done something like this?

This section is not complete or finished in any way. It is still a very rough draft.

The current concept provides a rating of 1 through 5 to the reader even though the actual scoring uses a number of 0 to 100 for each point (well, maybe 0 through 10).

Any ratings for job sites should include at least the following:
 

NOTES FOR FUTURE:

 Registration: 
	0=must have paying subscription to use.
	1=must register to use, but registration is free. Nothing special remembered.
	2=will remember some of your search criteria w/o paying for subscription
	5=no registration is needed.
 Jobs:  number of jobs on-line
  Search;
0=no online search. 
1=minimal search (all AND or OR).
2=AND and OR.or Boolean w/o parentheses
3=AND and OR  with parentheses
4=full Boolean with parentheses, NOT, etc.
Results: description returned
0=job title only
1=full text only
2=job title and some text
2=select job return level
Results: sort
	0=no sorting
	1=sort by match quality
2=sort by post date
3=user selects sort by at least match quality and post date.


 
   ============================================================

   ============================================================
[home] / [writings]writings
[AnyBrowser]
NetMechanic HTML Code Excellence Award
.http://www.exit109.com/~ghealton/writings/InternetJobs.html  
 Hits since 2002-09-10: [unavailable]  $Id: InternetJobs.hmac,v 1.17 2003/06/17 18:12:06 ghealton Exp $
Last formatted 2008-10-15
(Disclaimer)