Pam and I made every excuse we could for one more errand out in this sparkling, crisp (sounds like a soft drink) day. All of that rain has resulted in flowers and green everywhere, and we could see mountain ranges to the North from Broadway that I don’t think we’d ever seen before, or at least not this well.
We got lots of odds and ends, and in general, prepared for Pam’s trip that will take her to our old haunts in Boston, her brother’s family in West Springfield, Massachusetts, and a final stop in Minneapolis for the STC (Society for Technical Communication) Convention. She’ll be on the road for nearly 3 weeks. I hope none of her Koi die while under my care.
As for me, I get to continue my job search, which has continued with help from friends and a new career management company that I’ve signed on with. The latter has involved lots of definition of career goals, compiling ‘narratives’ of my work accomplishments to date, and meetings with my assigned contact at their offices. I leave off names and companies here for a reason: The meetings, and my interactions with this person are not going as well as I would hope. Why? As it turns out, the person who is to be my advocate, coach and adviser at this company is decidedly non-technical. Really non-technical, as in not knowing much about the Internet, Computers, the Web, or anything remotely related to Technology. This has proved…challenging to me and is fairly troubling. After all, how can someone advise you on your career if they have absolutely no understanding of what you do to begin with?
Case in Point: At our last meeting, they brought up their Savings and Loan’s web page on their screen, turned it to me and asked point-blank: “Is that all you do”? I was a little taken aback. “Yes, I answered, after a moment of silence where I held back the urge to lean across their desk and punch them in the face, “But that’s not all of it. It’s like asking a Furniture Designer if all they design is chairs.”
While it’s a good thing for me to make sure that I can relate to a non-technical person (which is not something I usually have a problem with; I’m a self-admitted geek but I am a result of a Liberal Arts Education), I have to say that rewriting my resumé so that all of the technological reference are either eliminated or simplified is not something I would have done on my own, and I wonder if it’s going to serve me well. Will I have a ‘David for Dummies’ version of my resumé that I trot out for someone who I think will give me a blank look if I mention the words ‘User Interface’? Then again, how would someone like that ever be interviewing me for a job in the first place?
On Tuesday, I am to appear for my meeting in formal job interview attire. According to their rules, that’s a dark suit and tie.
Techies in Vancouver: When was the last time you appeared for a meeting in suit and dark tie? It’s not that I don’t have one, or haven’t worn one in my life, but it seems to reinforce the idea that these people have no freaking clue whatsoever what tech culture is like.
If this continues to irk me and interferes with my job search, I may request a different person to work with, which may prove a bit uncomfortable for all concerned. Nevertheless, I’m going to give that some serious thought. In the meantime, it’s back to my old resumé, which I’m trying to use to create more ‘narratives’: “Once upon a time, there was a need for a clickable HTML prototype…” (*Doh!*)