Blast from the past: 11.5.2011 - Write Your Own Job Description

Found something in my blog that I was writing on 11.5.2011 but never published. I think it maps pretty closely to my later blog post on my personal strengths inventory.

--------------------------------------------------------------------------------------------------------------------
I'm reading J. Allard's exit email from Microsoft. It's fascinating and you can find it here.

About halfway down the page, he writes how the Microsoft interviewer challenged him to write his own job description. I've heard of this happening before in interviews and while it's never happened to me, it occurred to me that this would be an excellent exercise for someone like myself that is STILL trying to figure out what his strengths/value proposition are. In other words, if I start networking like crazy over the next month, what impression do I want to leave with people so that they have a rock-solid idea of what it is that I do and how I can be of value.

I also completed the Strengthsfinder 2.0 survey last night and while the results are interesting and definitely relevant to this exercise, I'm going to table my thoughts on those for a separate post. For now, I'm simply going to try and brainstorm a bit on what I think my ideal job would be and what my value proposition should look like.

First of all, if I look back at those jobs where I've done well, one dominant theme, or persona, comes up, that of the "cross-functional problem solver".

So, what exactly is a cross-functional problem solver? Within an organization, the CFPS is an individual that, fundamentally, has an ability to work closely with other teams and functional disciplines to get things done.

What are some characteristics of this persona?

Strong communicator
Doesn't sweat the small stuff
Strong critical-thinking ability
Broad knowledge of the various functions within an organization
Curiosity, inquisitiveness
Negotiation Skills
Ability to look at issues from the other person's perspective
Ability to work with technical people
Strategic thinker - understands the larger goals and objectives of the organization
Customer focus

Here are some of the jobs I've done where these skills and abilities came into play:

Back in the day, in the Marine Corps, things turned around for me when I took on the Orders Clerk job. That job involved a certain amount of Project Management and a lot of coordinating with other agencies, such as Disbursing and the team that handled the movement of household goods. Also, there was a fair amount of coordinating with higher headquarters units, group and wing, and various other units around the base. I shouldn't forget the interaction with various Officers and NCOs, keeping them up to speed on what was happening with their people, and also the last minute dance to get orders signed, either by the CO or one of the other officers with signing authority. Another skill involved in that job could be described as the ability to understand the logic of the bureaucracy and administrative regulations.

After college, I worked as a Technical Router at Microsoft. This was my first call center job. Mostly, this was a communications-focused role. Critical to success was the ability to communicate with the customer and the various technical teams and to develop a broad understanding of the technologies being used. I was really, really good at this job. I also did exceptionally well as a coach and trainer when the program expanded.

Next would be working at drugstore.com, first as a customer service rep and then later as an Ops Guy (various titles). My time as a CSR was fine, but not especially instructive in terms of my overall strengths, aside from customer focus. Although there is a cross-functional element to it, the basic job of a CSR is to support the customer with the tools at hand. This changed to a large degree when I went to work on the Operations Team, first as the workflow coordinator, or whatever you want to call it, and then later taking on scheduling and reporting and eventually doing the Blue Pumpkin implementation. A large part of my role during the last 2+ years at drugstore.com could very easily be described as problem solver at large for the contact center. I'll write more about that later.

After leaving drugstore, I worked a number of different contracts at Microsoft. The common theme again was problem solver. The TAP was probably the best example of this, as I entered a situation where they were close to project failure and basically rescued it. I need to do some more writing on this and try to remember all the little things I did. How did I rescue the project? What were the key elements? This was likely my very best work performance of all time. I was really, really engaged with this project.