Dear employer:
I have over nine years of experience in the health care arena. I have worked from the bottom up and have encountered all types of personalities while assisting people in a very diverse environment. During these eight years I have found that people need treated individually, and not as a whole. There is no room for “geek speak” if nobody understands what you are saying, and that can cause frustration. Everyone from an administrative assistant to a CEO understands plain old English. Good communication is the key to get successful results in resolving their problems and requests.
I have also encountered all types of co-workers also. What I have found is that everybody has their own way of doing things. Even if they have accurate documentation they may skim over it and not completely follow the instructions. This is why scripting and staged installations are very important. This can eliminate a lot of troubleshooting by ensuring the software or operating system is the same on all systems, and you are troubleshooting a problem with the software or hardware, and not a problem with a bad configuration from an install.
When scripting does not make sense because of the limited number of installations or something is very specialized accurate documentation is vital. If it takes you a while to figure out a configuration it can save a lot of time to have it well documented for the next time you have to do the same configuration, or a team member has to do the installation. Having good documentation in a central area, and not multiple copies of the documentation detailing the same desired result but are slightly different, is very important.
Scripting can also save the enterprise a lot of money. If something that can be scripted instead of a human performing the task eliminates a lot of problems. People, including myself, make mistakes. A task that is scripted is done the same way every time, usually much faster, and human error is eliminated.
Troubleshooting is an art in my opinion. If you don't know where to start, or what could be causing the problem, then you cannot get the desired result in resolving the issue. The only way to no exactly what is causing the problem is to eliminate known goods to isolate the problem. By cutting the problem in half and isolating the problem in either of the halves, then splitting those halves and doing the same thing the problem can be found a lot faster. This is a electronics technique, but I have found that it also holds true in hardware and software issues in most cases.
I'm sure I can be a valuable asset to the company that is looking for a team player with my skill set. I love to learn new technologies and welcome any challenge that I am presented with.
Sincerely,
Keith Hagans