Choices on the Career Path

  • Vote This Post

    1

Ok.  This post isn’t stricly aligned with BlogIdol Topic 1, but its close enough because the title uses the same words :-)

Fogive me if I don’t go all the way back to when I was a boy wanting to be a fireman…..I’ll start the story after I graduated from engineering.  After all, that’s when your career starts, isn’t it (asuuming you went to university at all)?  As an aside, can you actually have an IT career these days without going to university or college first?

Anyway, my career started right after university (no hitchhiking around Europe for me – I was keen to engineer something/anything) but I didn’t really choose where I landed, because that would have assumed I had multiple jobs to choose from (which I didn’t).  So, once you get your first job you have what might be called a career, but that’s when the fun begins – now you have to make career choices.  Is this where the phrase “random walk down the career path” fits?

And what might those choices be, you ask?   Well, one of the first might be how long to stay at this first job before moving on.  I’ve known a few people my age who stayed at one company for their whole career (they are now retired with a nice pension), but they say most engineers don’t stay on their first job more than a couple of years.  Then there’s a fork in the road – do you want to head towards management, or stay as technical as you can.  For me, I tried to keep my options open and keep one foot on each path (and funnily enough it was often painful).

For some, leaning towards management means going back to school for an MBA.  For the rest of us, there are a large number of technical certification choices to keep you busy.   I’ve seen people with lots of letters after their name!  Chasing certifications can be a lifelong endeavour (passion??).  In any case, an IT career requires continuous learning, and since you cannot know everything, some level of specialization.  I have come to the conclusion, after many years, that the more you know and the more varied your experience, the more you look like a generalist.   And that may not always be the right career choice!!

Somewhere down the path, whichever one you choose, you will starting asking “why am I still here?” and that’s often a really tough question.  Other posts on BlogIdol say “passion for technology”, some would also say “intellectual challenge” or “constant change” while still others might say “its just for the money”.  Perhaps its a little bit of all those things.  Maybe its also the feeling of being in some sort of exclusive club – no one else knows what you do, and you won’t (or can’t) explain it in layman’s terms.  The good thing about an IT career is that there are so many different IT thngs you can do that it could seem like a career  change even if its still IT.

So, are your career choices based on a 5 year plan or are they mostly opportunistic – jumping at an opportunity when it presents itself?  I would say that today, more than ever before, a roadmap for your career can be a big help in answering the question of why am I here still.  Your experiences may differ, what was your career path like?

Don Sheppard Don Sheppard (86 Posts)

I'm a Blogging Idol enthusiast who also does consulting for a living. I began my career as a railway data communications engineer. After working for a bank for 7 years, I took up the consulting challenge and I still find it challenging! I try to keep in touch with a lot of different I&IT topics but I'm usually working in areas that involve service management and procurement. I'm back into ISO standards development - in the area of cloud computing (ISO JTC1/SC38). I'm starting to get more interested in networking history, so I guess I'm starting to look backwards as well as forwards! My homepage is http://www.concon.com


  • http://turningtechinvisible.blogspot.com Kevin Pashuk

    Don, Great post. Keeping one foot on each of the management / engineering paths works until the core responsibilities diverge, then it becomes painful. With few exceptions, most of us do not look graceful doing the splits!

    This is a great topic for all of us to expand on in other posts.

  • Nigel Wimbush

    You raise some interesting points of reflection, Don, particularly for those of us who have been in the industry for a generation.

    Is University necessary? If you have a IT career target needing a degree as a prerequisite, otherwise, the effort might be better spent investigating careers in IT. Certifications are easy and quick in comparison, and current!

  • http://whyhire.me/ron_van_holst Ron Van Holst

    I’ve never been known to look graceful (see my opening post last year), but it never felt like the splits. I did go back and forth between management and technical, and I have found that a role like Product Management, allows you to be both a manager and technical. Although you do not have direct reports, you end up indirectly managing lots of people in different disciplines. Although you are not tied down to implementation details, you do need to make decisions about technical details, and must be able to drill down to any level of detail in order to solve problems. All at the same time keeping an eye on the big picture, balancing the business needs with the technology capabilities and risks.

    On the subject of specializing or becoming a generalist, that is a substantial subject in itself. There are pros and cons to both, perhaps that’s the subject of another post.

  • http://www.concon.com Don Sheppard

    Ron – To add to your comment about Product Management, you could probably say the same about Project Managers.
    When you start out in User land, its often tough to get into being a product manager in a supplier environment.