I applied for a network-administrator job through Dice and then sent the resume directly.
The second message acknowledged that the employer might receive both copies. I wrote that the automated Dice application system could be buggy and I wanted to make sure at least one resume arrived.
My pitch was straightforward. I had experience administering Windows, Linux, and Unix systems, a strong networking background, and exposure to several kinds of hardware and production environments. I attached the resume and asked the recipient to contact me about positions that might fit.
The duplicate route was deliberate. An application form could accept a submission without giving me confidence that the right person had received the attachment. Direct email gave me another path and a visible sent record.
I was working as SimAuthor's network administrator. Earlier that year, my resume described Windows and Linux administration, Active Directory, Exchange, network security, virtualization, hardware deployment, scripted installation, and consulting. I had already sent a batch of applications in March and continued following up through recruiters.
The same June 16 correspondence included a reply about a different role involving .NET. I said I had programmed in .NET but did not want to pursue it as my main direction. I was looking for infrastructure, Unix, Linux, systems, and networking work.
The archive does not identify the company behind the Dice address clearly enough to name it, and it does not show a final outcome from this application. I should not turn the message into a successful interview or offer.
What it shows is the application process I was using by mid-2006. Search the job board, submit through the system, find a direct address when possible, explain the duplicate, and state the technical range in a few sentences.
I would repeat the process later in the month for several more openings.