Career Ladders

A friend of my told me he just got his new title at Big Software Company. I was happy for him because he’s been want the new title for a while. He started talking about how he was at the point where he needed to decide if he wanted go up the technical career path or the engineering management path. My company recently rolled out the engineering career ladders which, while different in titles, was essential the same thing with a technical path and a more people/project management oriented path.
In my younger years, I would have said I’d take the technical path without a doubt. In the last couple years, I’ve considered the more management oriented path, but have still leaned toward the technical path. However, as I’ve looked at it closer, I really don’t care about a career ladder or even a career in the traditional sense.
I like building software. I like the challenges, learning, and problem-solving involved in all aspects of this endeavor. Sometimes it involves writing a specification. Sometimes it involves coordinating with other teams. What in the world does any of this have to do with a career ladder?
I guess career ladders might matter if I want raises and promotions. I like raises, who doesn’t, although I’m not sure how much raises and the career ladder are really tied. If a company wants to keep me and it’s only a matter of money, if they can’t get around the career ladder I’d bail anyway. Promotions don’t really concern me because titles don’t define my level of expertise or ability to get a development job. They would concern me if I had aspirations of being a Director or V.P. but I have no interest.
While I’m working in the world of big companies, I’ll think I’ll play outside the career ladder. When I finally get my microISV up and running, I won’t need a ladder.