I must admit, when I applied for my last job, I knew nothing about the organization or the type of work that I was going to perform for several years, so the job description played almost no part in why I applied for the position. I just knew I would be doing something very different from anything I had done before—and the recruiter told me that I was a great fit for the job. At the time, it was also hard to research the job because of the tight security involving large-scale assessments. Additionally, only two organizations were part of a massive contract overseen by a gigantic consortium of states. The two organizations kept a “tight lid” on all their “proprietary” knowledge, skills, and abilities concerning the actual job I would be doing. It is a bit embarrassing now; I just blindly jumped into a job without any solid information about the job or the organization’s expectations of the position.
The actual job description included some the following language: Review of items for large-scale assessments; evaluation of passages for use in large-scale assessments; interpretation of blueprints, and the construction of operational and field tests across multiple contracts. I did not even know what most the description meant in context to my experience, training, and education. As I learned the job, I found that a small part of what the job description outlined was a small part of what I did on a daily basis. The job description was about a 20% match to the work I performed.
I do not think the organization completed a job analysis as outlined in this week’s mini lectures. Not only was the job description vague, the details of what the job entailed seemed to change constantly as the contract grew, so we were always in a state or “training up.” This was not an enjoyable job, but I was promoted to a new position in the organization very quickly.