Month: July 2011

I had a good interview yesterday afternoon. It was with a new agency I hadn't previously worked with.  They're submitting me for a support position with a healthcare provider that doesn't require any direct hospital work.  It's pretty much exactly what I was hoping for, and while the pay rate is below my desired minimum, it's a 3-month contract-to-hire gig that will undoubtedly pay more if I'm hired on as an employee.  This put me in kind of an up mood, because not only does it sound like a job I'd like, it's only about a 20 minute commute from anywhere Ben and I could conceivably settle.

The recruiter also told me she'd gotten glowing recommendations from my two past supervisors. This was not unexpected, but it was still nice to have it confirmed.

They're going to try and get me in front of the client for an interview the first of next week.

I also got a call from a recruiter in New York regarding a 3-4 month contract position working through an outsourcing company to image and roll out new PCs "for a military client." I asked if it required a security clearance, and was told no. That sounded kind of odd, but I'm not in a position now where I can just automatically dismiss things out of hand. I'm meeting with a representative from the outsourcing company (that looks completely legitimate but doesn't have an office in Denver) at a Starbucks Monday afternoon.  If I had not personally witnessed several job interviews taking place in that venue since arriving in Denver I would've though it very odd, but now…not so much. Maybe it's a Colorado thing?

But of course, I'm still hoping to hear on Monday from the recruiter who's been on vacation this past week regarding my interview from a week ago. That's the place I really want to work.

Very, very anxious.

One of two good job leads I had has dried up.  I spoke to the recruiter today and she said, "Oh, they've decided to put this on hold." Well gee, thanks for letting me know.

I'm still waiting to hear about the second.  I had what I consider to be a good interview last Friday, and the manager I met with told me that she was expecting to make a decision by Tuesday (today).  I just called the recruiter I'd been working with on this opportunity, only to discover SHE'S ON VACATION THE REST OF THE WEEK.  I asked to be connected with the Account Manger for this gig, and got her voicemail.  I left a message asking that she call me back.

So far this morning I've spoken with all the recruiters I've been working with, and none of them have anything else right now…except one.  It's a six month contract at significantly less money than I was making even five years ago, but at this point, if I don't hear anything about this other job by the end of the week I'm going to tell him to go ahead and submit me.

I have to get back to work.

I find myself wishing that Ben and I had planned financially for this move about six months earlier than we did. While I'm not down to my last penny, the balance in my checking account has fallen below my comfort level and my anxiety level is rising with each passing day. Thankfully Ben has one more student loan disbursement coming, and he officially starts teaching in about a week, so there will be money coming in, but until I get a job, we're stuck in a hotel that reeks of pot and patchouli and everything we own remains in storage.

"That was quick!"
"What do you mean that was quick?"
"It was quick! In and out, just like that! In and out!"
"Piss off and fix me some coffee, will ya!"
—Interchange between Christine Painter (Julie Walters) and Rose (Victoria Hardcastle) in Terry Jones' 1987 film Personal Services

After a month-long vacation period of unemployment, I finally landed a job yesterday.  It happened in the blink of an eye.  I got a call from a recruiter whom I'd not heard from previously who had an urgent need for a desktop tech in a healthcare company.

Ugh. Not my first choice.

Even so, I met with the guy, and while I had some strong misgivings about returning to a hospital environment, the fact that the balance in my bank accounts were starting to cause some concern overrode it, I agreed to let him submit me for consideration.  Even I had to admit that on paper I was a perfect match for what they were looking for, so it came as no big surprise when he called back late yesterday afternoon to tell me that I had been hired without so much as an interview.  Finally, a light at the end of the tunnel!

This morning I was at the agreed-upon location at the agreed-upon time, but the account rep was nowhere to be seen and was not answering his cell.  Thankfully the email I received also included contact info for the I.T. Manager I'd be working for.  I called him, and he said he was unable to come down to the lobby to meet me; he would send one of the techs to get me set up with an access badge.

That was the first warning sign. The manager, whom the recruiter said I needed specifically to dress for ("wear a tie"), didn't even have time to come down to meet me.  I can't imagine my previous director ever acting so callously toward a new member of his team, even if he was only a contractor.

The tech (whom I wasn't even going to be working with) came down and escorted me through the labyrinthine maze to the underground materials management office, where I watched with no small amount of amusement while my badge was prepared.  Apparently the woman who made the badges had some moderate OCD going on, because every time her Outlook dinged, she stopped what she was working on to check on the incoming mail. "Squirrel!"

Second warning sign: instead of being taken upstairs to perhaps then meet the supervisor, I was immediately wisked out of the building to an adjacent facility where the deployment team that I was to be a part of was working.

Third warning sign: after being introduced to the project lead and the two techs, one of the techs immediately started ragging on the customers as well as management in regards to the project they were working on.

Now I'll be the first to admit that I've ragged about my previous job on many, many occasions—as long-time readers of this blog will attest.  But never in all those posts did I name the company or call out anyone specifically.  How did this guy know that I wouldn't immediately run back to the supervisor and report his toxic negativity?

There wasn't a lot I could do other than physically hook up PCs and do a bit of work on the patch panels as I did not yet have system account set up, but that was fine. (Not surprising considering the rapidity with which all this happened; I hadn't even completed the necessary hiring paperwork at the agency.)

But as the morning progressed, I became more and more despondent. That hospital smell, the prima-donna attitude of the nurses and doctors… I felt like I'd taken a huge step backward in my career, and I started contemplating my options. The angel on my right shoulder said, "Stay the week and see how it goes. It might get better." The devil on my left said, "Cut your losses and get the hell out of here now." Or maybe their roles were reversed.  I can never tell.

All I know is that practically from the get-go, this assignment just didn't "feel" right, and I was having flashbacks of a gig I did at St. Mary's Hospital in San Francisco about fifteen years ago. Then, as now, there was a reason they were willing to pay substantially more than similar jobs, and it wasn't because they were being generous.  It should've been the big red warning sign that tipped me off before I even got started.

I had hoped that a break for lunch would help clear my thoughts.  Instead, whoever it was on the left kept screaming: "Get the hell out of this place NOW."

I returned from lunch and called the lead tech, asking where she and the others were working. "Oh, I'm in the basement, but I have to go to a meeting in about two minutes. Call Matt (Mr. Negative) and find out where he wants you." She gave me his number and hung up.  I called Matt and got the "The number you have dialed is not in service," message.  I hung up and called the lead back.  It went immediately to her voice mail.

This was the proverbial straw that broke the camel's back.  I'd had enough. This was not the place for me, even on a short-term basis.

As I was walking back to my car, I called up the recruiter and told him I was terminating my as-yet-unsigned contract.  (Yeah, I still hadn't received the paperwork that was supposed to have been emailed to me by start of business today; yet another issue.)  I explained the situation and that I was leaving and would not be returning.

Needless to say, he was a little surprised.

My phone rang several times as I drove back home. (Sad that I'm starting to refer to the hotel as "home." Must be Stockholm Syndrome.)  I returned his calls about an hour later. This time he was not surprised so much as angry and demanding that I give him specific reasons why I couldn't continue on the contract.  Since I was the second guy in as many weeks that he'd sent over to this particular hospital who didn't work out, this was reflecting very badly on him.  I told him outright that maybe it wasn't the guys he was sending over, but the environment he was sending them into. "I have several guys over there who love it!" Yeah, several guys whose names he couldn't even recall. Real professional, this one.

And he wouldn't end the call, even after I admitted that it was probably my fault for accepting another job in healthcare when I shouldn't have.

What did I learn from this horrible day?  NO MORE HOSPITAL WORK…EVER.  If it comes down to it, I will sling Cappuccinos at Starbucks before I ever return to that environment.

Several years ago, when I was first transferred over to the health plan portion of the company I worked for, I resented it.  I'd been working at the hospital for five years and really enjoyed the fact that I'd whipped the technical environment and the expectations of my users into shape and that the workload was quite manageable. Plus, the health plan had a horrible reputation.

But after having been at the health plan only six months, I realized I did not miss the hospital environment one bit, and while I had a dozen or so users I would've gladly pushed off the roof, on the whole it was a much less stressful place to work.  As six months turned into two years and talk surfaced of reshuffling support staff among the facilities, I realized that if it meant going back to hospital work it would be the impetus that would finally force me to quit.

So we're no better or worse off than we were yesterday at this time.  I know Ben's a little disappointed that he may have to use his next student loan disbursement to keep a roof over our heads instead of buying a new toy he's been lusting after, but as he said, "your sanity is more important than any job."

And as if to tell me things are never as bad as they seem, I got a call from the headhunter who sent me to that disastrous interview telling me that I (duh!) did not make the cut. I told him I was surprised to be hearing from him considering how poorly I did at that interview.  "Don't worry," he said, "everyone has bad interviews and as long as you come away from them learning something, it's all good.  And by the way, we have quite a few openings coming up soon at [insert healthcare company name] if you're interested."  "I've been rethinking healthcare," I said. "Heathcare insurance, or healthcare corporate office support is fine, but NO hospitals!" He laughed and said he'd make a note of it, and just to be clear, the jobs coming available would actually be in the corporate office. No hospital work required.

Finally got an interview today.  It wasn't anything great; just a 30-day contract, but it would've been a little extra money coming in.

But it blew it.  Bad. Probably the worst performance of my career.  I knew beforehand it was going to be a technical interview, but I wasn't prepared for just how technical.  But then, how do you prepare for that when you haven't got a clue what the questions are going to be?

First off, the agency that sent me over didn't bother to forward the interviewer my resume, so I might as well have been someone who wandered in off the street. With no clue to my background or experience I think my inability to provide answers to some of the questions made me look just plain unqualified, and I hated that.

We got on just fine, and I think we'd have a good working relationship, but rapport alone will not get my foot in the door if someone has doubts about my technical ability.

Many of the questions were what I would consider more systems admin than desktop oriented.  While I know a bit about what goes on "behind the wall," as my former supervisor used to call it, a lot of the acronyms he asked about threw me for a loop…as did the question that asked what specific port numbers were used for.  Not once in all the years I've been working have I had to mess with ports as a desktop support tech.  Maybe I've been sheltered. Maybe the fact that in all the environments I've worked desktop has been solidly walled off from systems. Maybe these things are important to desktop techs in the environment he supports, but they haven't been a part of the ones I that I have.

For the record, I now know what the four most common are (IMAP, HTTP, HTTPS, and SMTP) so in the unlikely event I'm asked about them in future interviews I won't look like a complete idiot.

He liked a lot of the answers I gave, but when he said, "based on your earlier answers I won't waste time with these other questions," I knew I was pretty much sunk.

I will be seriously surprised if I get called back. What pissed me off the most was that as I was driving back to the hotel I was thinking about some of the questions I couldn't answer and thought, "Of course! I know what that is!" Duh.

Whatever. A major part of this assignment was just going to be breaking down equipment and moving it from one room to another.  I don't think I'm going to need to know port numbers to move and reassemble PCs.

Tomorrow is a new day, and with it will come new opportunities.