Development Plans

I had a former coworker ask me what career path he should put down in one of those development plan type documents that was required for work. He mentioned a few titles such as systems engineer, project manager, analyst, etc.

It kind of dawned on me at that moment that it's extremely easy for people in the IT industry to attach themselves to a title and think that the world will come with it. Five years ago all I wanted to be was a Network Administrator. As I gained experience, I realized that was exactly what I didn't want to be.

The only reason I thought I wanted to be a net admin was because I thought that's where the money was and it was the only place for someone with my skillset to develop toward. A few years later, I know from experience that while the Network Administrator track is a perfectly viable career path, it's not for me. It's a position that rarely integrates with the business and really performs the same function no matter the company. In other words - it's technically challenging as it mostly requires updated skillsets and technology, but it is extremely easy to outsource. On the other hand, it's very easy to find consulting jobs for as well.

Anyhow - the best thing that you can do in my opinion when looking at your career path is not looking at other people and what they do. Sure, they may be making a certain amount of money equivalent to what you want to make in the future, but they aren't you. Critically think about what you like doing now, and imagine how that can develop. Imagine how that aspect of your job now that you like can turn into all you do. That's what you need to develop toward. Be it writing user guides, fixing AV equipment, talking to cell phone companies or even just teaching people about technology. Each of those has a very lucrative career path. Maybe not necessarily where you're at - but think big picture and long term.