Saturday, October 31, 2009

Career Path

There is no such thing as career path.

I’m talking about a career path for an engineer, or those who want to focus and stay technical in computer networking field, for example, for the rest of his work life.

In some organization this can be seen as crystal clear. There isn’t any path at all for technical person. It just doesn’t exist, especially in an organization where IT is considered as secondary team, formed just to support the mainstream of the company’s business. Once an engineer becomes senior and wants to go to higher level he needs to switch to a managerial level, let’s say by becoming a technical manager. And this means he needs to start dealing with other stuff outside the engineering scope: manage people, budget, P&L per head in his team and so on. In this type of organization if one is keen to stay with the current scope as engineer, then he’s going nowhere. It may be even worst since some organization prefers to “refresh” the engineering division aka removing the old timers and put the younger workforces in order to lowering the monthly pay slip.

How about the technology solution company? It has been said many times that the engineering division is the core key of such company. Technical solution by engineer leads to sales that brought the income to the company hence it must be a haven for engineers to work for such organization? Not necessarily. The key here is still the ‘sales that brought the income’. We need to understand that it’s difficult to quantify an engineering work and get promoted. For example, as sales person in the company one can be given a number of annual targets of sales and if he can achieve or even over achieve the number within several years in the row, the promotion certainly awaits. How can we measure how successful an engineer is using a similar measurement? By looking at the number of US patents he produces or IETF RFC’s he has been involved each year? I’m talking about the engineers who work in the field in general to support computer network systems, as many of us are not that lucky and able to sit in the lab to invent the new technology.

So is there a way for an engineer to have career path?

Yes, there is. Some technology innovation company perceives the importance of keeping good engineers to support the business by making higher technical position is always available. This is the company where an engineer can stay technical and yes he can always climb a higher level until he is called “Distinguished” engineer or even “Fellow”. But still in order to achieve such level in engineering one needs to take control and build his own path, and even may need to compromise.
And as far as I know, a good engineer never compromises :)

First of all, the engineer needs to compromise to accept the fact that the technical team is less likely to be involved in any business decision, like an organization changes. Suddenly the company decided to change the model of the way they do business, including restructuring the engineering team, and let’s just inform the engineers at a very late state. One may comeback from a nice weekend just to find out he now needs to work for another team or to report to another manager. And if it’s not enough with the difficulty of an engineer for being recognized for the works he has done, how about moving him to the new team or asking him to suddenly report to new manager, where he has to start over?

Second, the engineer may needs to compromise by manipulating a technical fact in order to support the business. A solution that may not fit the requirement is proposed due to some other reasons including the political and other non-technical stuff, and now it’s time for the technical person to make it works somehow. A young and fresh engineer may just say NO because he still likes to work with the plain truth, just as what being engineer is all about. But if one wants to climb the ladder in the organization, from an engineer moves to senior level, then to become architect, then to a position called as technical lead, or distinguished or whatever, the organization is certainly expecting him to support the business.
From the way I look at it, it’s just another compromise.

The third and the worst compromise of all, because it’s difficult to quantify and distinguish an engineer from the others, the engineer may choose the short cut by doing anything possible to stay on the spotlight. Some said, to climb the company’s ladder it’s all about making the big noise. But how if the engineer is busy making noise but not the real work? The competition among the engineers may become ugly and no real intellectual property really produced, only the noise or the efforts to be the first to announce a half-done work.

I hope the three above are just my imagination, and as the result of too much smoking Shisha while chatting with old friends last night. But unfortunately, some of them are too real.

So if I knew this all along, why bother even to write it down and discuss it? Life is a matter of preference, isn’t it?

It’s true.

The reason why I brought this up is so all of those like me who think and plan to spend the rest of our time focusing on technical, can set our expectation right. Once we choose to go down this path then we should know the consequences. That it won’t be easy and it will be full with obstacles even to move one grade higher. We have to be ready to see those who choose to be in other department, for example in sales, may climb the company ladder faster than we do.

And I also have a secret to share here. I noticed that to get the promotion as technical person, we don’t have to do great job in every task. But we have to do an extra ordinary job in only a single task. Superb work even in only a single project, in the right time and seen by the right people, can bring us much better result. Just like one great rock show can change the world, as Dewey Finn aka Jack Black said in the School of Rock. And obviously we don’t have to be on the spotlight by claiming someone’s work even if we really desperate to get the promotion.

Will it really work?

How the heck I know? I’m a kind of guy who keeps changing the organization everytime I want more. In the past, to get more salary I moved to another organization. To get a better job profile I moved to a different team. I built my own career path by keep moving from one organization to the others. I’ve never been in the same place long enough to see if my ‘secret career advice’ can really work.

So I will tell you all the result once I really get my promotion.

Disclaimer: the writing expresses my own opinion and it has no relation what so ever with the organization I currently work for. It’s based on my own experience moving from one IT organization to the others, as well as my short experience working as contractor.
And I’m not smoking anything while writing this.

10 comments:

mau said...

Agree bro...ussually if you already fellow engineer than become scientist or reseacher since you find new method or formula how to make thing better but in some circumtances your idea some how is rejexted by some "bullshit" management ...so your next career would be an enterpreneur...you set up a company basesd on your ideas.. That's how someone build company like juniper, force 10 ans so on....

Anonymous said...

Completely agree! As sales team get bonuses for targets, tech team don't even has a target! We just have to make a often bad and poor designed solution work as expected by the customer, filling all the design gaps on the fly. Nobody knows the tech skills required, learned while installing or on my free time. Maybe I'll move to pre-sales to get more $$$ but I'm in love with the command line, not with excel and project, so I try to stay here until possible. Thank you for this great post!

Raf said...

Your post made a little suprise. A few good months ago you wrote about your ideal job and now you write about your new path. I thought you had it made :) But looking at myself, I also tried the CCIE lab (but failed) and have given up on focusing on networking. I think that networking is in a way a dying career path. Look at technologies 10 years ago (ATM, Frame, etc...) now you have Ethernet and a lot is auto configured. Sure MPLS is not easy, but it's not to hard once you know visualization. As for myself, networking is paying the bills, but I'm looking to get into programming. I know there is a lot to learn and it changes quite fast, but at least you can program something for your self, start an idea, solution or business. With networking you will always be someone who just routes packets from one side to another.

Anonymous said...

I like your comment about getting rid of the old timers...I worked for this company recently, they got a contract to manage the IT department of a big organisation, but there was already staff working there, one older guy has been they forever, and basically knew everything. So I was hired on a contract, and I was told I would be working very closely with this older guy, I must learn everything he knows, it was clear to me they wanted to get rid of this old guy, because his salary was too high, then they could slot me into his position, with the peanuts they were paying me (with zero benefits). Needless to say I didn't work there long, but it was a very uncomfortable experience. I don't have time for company's that don't respect their technical staff, and think that we are simply replaceable.

tagskie said...

hi.. just dropping by here... have a nice day! http://kantahanan.blogspot.com/

Anonymous said...

Himawan,

Enjoy reading your blog - but seriously, the white text on black background is KILLING me. I see zebra stripes for 5 minutes after I read any of your posts. Would you consider making the blog easier on the eyes? :-)

I do agree with your points. It is tough to climb the ladder for those of us who *choose* to stay technical vs. moving to other roles such as pre-sales, project management (you would be surprised how much they pay non-technical project managers these days) or even scarier - management.

I think the key is to do what you love. I have had at least two jobs where I took myself away from the CLI and hated it, only to come back. Figure out what really motivates you (is it the love of learning, challenging yourself with something new, etc.) and stay with it. Money can't make up for being miserable when you show up to work.......take care.

A CCIE from RTP

Anonymous said...

I agree with the comment about white text on black background. I copy your posts and paste into Notepad to read them, so that I can read black-on-white. Great blog, though - if it wasn't good, I wouldn't bother copying and pasting.

Zakhar said...

Himawan, Hi.

Do you receive result of CCDE exam? Do you successfully pass it?

Anonymous said...

Wow, Just looked at the Cisco Certified Architect Blueprint. I'm alittle disappointed. I think that Cisco is wrong in labelling the Architect certification "the highest certification given by Cisco." These are standard presales skills that are required when justifying new equipment purchases. These type of interactions occur regularly during a channel partner to client interaction or a network manager / IT director to a CFO/CTO interaction when in-house. Pretty standard procedure. Every engineer goes thru this process. I am a triple ccie with 10+years of experience and have take the CCDE lab twice. I have found the CCDE lab experience very rewarding. Mostly because the more we engineers read about what other engineers have done in real-world case studies tackling the same design situations from different angles, the better we become. All of these certs.. the CCIE tracks, CCDE, Architect are really just equal components to a whole. Each skill is necessary. Although, I do believe that the CCIE/ CCDE tracks are the most time intensive and gruelling in terms of preparation and mastery. The technical mastery and foundation must be there before anything else. The Architect certification is not worth the $15k investment. I get this practice every day on the job for free. I think they should break off this skillset out into a separate certification called Cisco Certified Presales Expert. The Cisco Certified Architect exam should be for candidates who have achieved CCIE RS, CCIE SP, CCIE Security, CCIE Voice, CCIE Storage, CCIE WIreless, CCDE, Cisco Certified Presales Expert + 10years experience. Candidates should be grilled in front of a panel and resume validated. That to me is the definition of the best of the best and worth $15k/yr.

Fahmi Athailla said...

Infonya sangat bermanfaat, thx ya.
btw nice info nih gan ^_^, visit back ya.

harga hp

Oppo:
spesifikasi oppo n1
spesifikasi oppo r1
spesifikasi oppo find 7

Lenovo:
spesifikasi hp lenovo s930
spesifikasi hp lenovo a706
spesifikasi hp lenovo vibe x s960

Sony:
spesifikasi sony xperia z1
spesifikasi sony xperia t2

Samsung:
spesifikasi samsung galaxy s4 black edition
spesifikasi samsung galaxy s4 mini
spesifikasi samsung galaxy s5

Evercoss:
spesifikasi evercoss a28c
spesifikasi evercoss a28t
spesifikasi evercoss a12

Smartfren:
spesifikasi smartfren andromax u3
spesifikasi smartfren andromax c
spesifikasi smartfren andromax i3

LG:
spesifikasi lg g pro2

GooPhone:
spesifikasi goophone i5s

Asus:
spesifikasi asus zenfone 4

Asiafone:
spesifikasi asiafone af9888

terimakasih !!!