Brooms. Not my favorite. |
"When can we set up an interview?"
"I'm available almost anytime, right now even if you were interested."
"Well, the interview is two parts but I think that should work for one of them."
"Great! I'll be there in 15 minutes."
I was already on campus for some summer classes, so I walked to where he was working and had a simple interview. He explained a few things about the position and asked me a few questions, along the lines of what things I can do. I confidently told him what I was able to do, we chatted a little bit, and he said he'd call me later about the second part of the interview.
I left excited, but a little worried I'd come off too confident or eager for the position. Evening came and went without a call, and since he had hinted at wanting to hire before too much longer I was planning on calling him sometime mid-morning or midday, but then I got a call around 10 in the morning asking me to come in around 12:30. Of course I accepted! I went home, made sure I was presentable and ready to go, ate lunch, and went to the meeting. My first time in a cubicle farm, I made my way to the back of the long room, had a brief chat with the interviewer's boss, then I was brought back to the interviewer's room and told to pull up my schedule on the computer. Simple enough. But this is where the fun began!
The computer was off, so I double checked the light and hit the power button. Nothing. Double check again, and then I check behind the computer. Hmm, the power cord isn't in. I turn to the other person in the office and ask, "Is this supposed to be unplugged?"
"Hmm, nope, I guess you can plug it in." In goes the plug, and back to the power button. Easy, right? Except instead of showing anything on the screen, I get nothing and a clicking noise. Suspecting nothing, I turn to the interviewer and tell him something is wrong with the computer, and suddenly I understand.
"That's fine, we've got some spare parts if you need them."
This simple project of pulling up my schedule was a test to see if I could find and overcome some common, planted errors that will disrupt a work sequence. They already had the schedule I gave them when I applied, I was just getting a chance to prove the skills I said I had.
Not Actual Photo |
So open up the case, look inside, and I immediately see a cable hanging unplugged. Plug that in, think I'm done, but then consider to look a bit more. Lo, there is a hard drive cable and power cord! 'Tis not proper for such to be laying about! So I located the hard drive, and after 5 minutes of trying to get access to it I got it out, plugged it in, and replaced it. Knowing there was more to check for, I looked through the case another time and saw that the RAM wasn't locked in, just placed in their slots. Alright, that was everything inside the case. I power it up, and happy there weren't any angry noises I was confronted with a screen without any input. So I check the connections of the video card and the cable, and was certainly relieved when it worked.
Then came a pause. I wasn't supposed to know it yet, but there was a network problem that prevented my supervisor from logging in with his credentials so he needed to find out what the local admin account was. Eventually that was sorted out, and welcomed by the windows screen I breathed a sigh of relief, opened up Chrome, and typed in my schools website.
Only I didn't type in my website. I typed in gibberish letters, every key leading to the wrong character. Anybody that has fallen pray to the second part of prank #7 will know what that means. While I didn't know immediately what to do, I found it and resumed my quest for my schedule. Only this time when I tried to go to the website, I got nothing but a "couldn't load page" error.
This was the low point of this test. I tried everything I could think of. Checking cables. Restarting the switch. Restarting the driver. ipconfig, ping, and IP addresses. From my research, I could tell I was connected to the network (I managed to bring up a connected printer by it's IP) so the switch and the connections were working, but I couldn't do it. After 15, 20 minutes (maybe it was less and I was just stressed) of flailing, I gave up and asked for help. After a grudging "I give up," he did a few tests, went into the settings for the device, and turned of the static, custom IP, which should only be used for certain reasons because otherwise it will do just what it was doing for me. After a mental "Duh, of course! I've even fixed this before for myself!" I got control back, once again ready to capture that elusive schedule!
Guess what? It didn't work. I mean, the network was working and I could get to the Internet, but upon trying to access the secure website we got a screen that was a lovely shade of red with a warning of an out of date security certificate. Fortunately, this was a quick fix that I have also had to do for a personal fix. A quick glance confirmed my suspicions, it was currently October 1st, 2016. Glad for the simplicity, I changed the clock and continued on my merry way, with my supervisor at my shoulder saying "And now we get to the hardest part." Expecting something, maybe a trap door with fire breathing crocodiles to open up or something, I got to the schedule to hear "That's a good looking schedule. Would you like to work for us?"
Yep, I just used a meme to express myself. |
Everything after that can be summarized with "And then I did the paperwork part of getting hired." A process
I'm still going through, but I should be working before too long. In a word, "Yes."
For bonus points, read the title to this post again after you listen to this clip.