Last week I saw the last email sent by a colleague who was let go by the company as part of the reduction program announced recently. I can't forward his email, and despite his joke in the email saying he's part of the 'winners' list who will get 6 months of advanced salary payment, I can see lots of disappointments in his other words.
His name sounds familiar, so I decided to google him. The result: author and co-author of many patents, several IETF RFCs, many Internet drafts, and speaker in International events, member of International forums, to name a few of his achievements in 5 minutes googling.
I can't stop asking myself: why can a good technical person get fired?
In a company that really focuses on new innovation?
In a company that relies on engineering excellence?
Can someone really stays technical in career?
Is it true that no one is indispensable?
After couple of days thinking, there are three reasons that I can come up of why even a good technical person can be let go by the company.
First, many companies appreciate what we did in the past, but I bet they can keep only those who can contribute for today's business and support the companies' future vision. It means even I did something spectacular in the past it may not be enough for the company today, especially if I am considered obsolete.
Second, as I mentioned in my other post it's really difficult to justify and evaluate a technical person. Sales person has a target number associated with her, if she can achieve or even go beyond that it means she's successful. How about a technical person? From the number of patents? From the feedback from the customers? From the number of initiatives?
Third, no matter how valuable I am I may still be out of the team if I'm not a team player. Unless someone has reached the top notch level, gained respectable reputation in the industry, and has become legend, no individual can survive by working alone. It's about making connection.
I may be wrong. I may be too naive.
You are more than welcome to share your thoughts here.
Showing posts with label Career. Show all posts
Showing posts with label Career. Show all posts
Sunday, August 28, 2011
Friday, August 12, 2011
Engineer vs. Many
"I find my manager is not useful. He is not aware about what's going on. In fact, he's not even a technical person. I'm running all the projects with the Project Manager, without my manager's interference. Why do we need manager then?"
"The project manager is useless. He's clueless, not technical, and inexperience in complex project like this. I'm making all the schedules, managing the resource, and building the plan for the project. It seems what we need just engineer and sales person"
"Our sales person doesn't sell. It's actually I as technical leader who does all the pre-sales work, convinces the customer about the solution, runs the demo and so on. It's practically a one man show, I can run the whole sales cycle from beginning until the closing by myself"
"The technical lead keeps everything for himself, he doesn't want to share his knowledge nor the information about the current setup. I have to struggle to finally understand the whole setup and the project. I'm wondering why he can be in the team."
Have you ever made any of the comments above? Don't be that guy.
You choose to be an engineer for a reason. A reason that you believe, or at least you used to believe. So be proud of being one.
And stop comparing. Because everyone has his own place.
Manager may not be technical but he has big responsibilities on his shoulder, including to manage the budget and expenses as well as to keep all the proud engineers in the team happy. Project Manager must manage the project and set the customer's expectation right from beginning, and she will be the first one who takes the heat when thing goes wrong (and something always goes wrong in every project) or when the schedule slips. Sales person carries a target number everywhere so she must know how to sell and to manage relationship with the customer, and be ready to get shouted when the engineers fail to deliver the setup. And the technical lead most likely is busy defending his design, leading the project, and coaching the younger engineers in the team at the same time, so he can't babysit someone for information that can be found easily within the project documentation.
And what I just mentioned is only a small portion of responsibilities and tasks from different roles above. Engineer may think he does the most work since he's in the field delivering the products or services to the customer. But there are lots more from the other parties that meet the eyes. Really.
But if you still think you could do better then those who are on the other side, why don't you try to switch place and prove it yourself? Try to be a manager, or a PM, or a sales person, or a tech lead and so on.
And let's see if you still can say the same comments as above.
"The project manager is useless. He's clueless, not technical, and inexperience in complex project like this. I'm making all the schedules, managing the resource, and building the plan for the project. It seems what we need just engineer and sales person"
"Our sales person doesn't sell. It's actually I as technical leader who does all the pre-sales work, convinces the customer about the solution, runs the demo and so on. It's practically a one man show, I can run the whole sales cycle from beginning until the closing by myself"
"The technical lead keeps everything for himself, he doesn't want to share his knowledge nor the information about the current setup. I have to struggle to finally understand the whole setup and the project. I'm wondering why he can be in the team."
Have you ever made any of the comments above? Don't be that guy.
You choose to be an engineer for a reason. A reason that you believe, or at least you used to believe. So be proud of being one.
And stop comparing. Because everyone has his own place.
Manager may not be technical but he has big responsibilities on his shoulder, including to manage the budget and expenses as well as to keep all the proud engineers in the team happy. Project Manager must manage the project and set the customer's expectation right from beginning, and she will be the first one who takes the heat when thing goes wrong (and something always goes wrong in every project) or when the schedule slips. Sales person carries a target number everywhere so she must know how to sell and to manage relationship with the customer, and be ready to get shouted when the engineers fail to deliver the setup. And the technical lead most likely is busy defending his design, leading the project, and coaching the younger engineers in the team at the same time, so he can't babysit someone for information that can be found easily within the project documentation.
And what I just mentioned is only a small portion of responsibilities and tasks from different roles above. Engineer may think he does the most work since he's in the field delivering the products or services to the customer. But there are lots more from the other parties that meet the eyes. Really.
But if you still think you could do better then those who are on the other side, why don't you try to switch place and prove it yourself? Try to be a manager, or a PM, or a sales person, or a tech lead and so on.
And let's see if you still can say the same comments as above.
Friday, June 03, 2011
Three Stories
There was a student doing his final year in the university. In the previous few years all he cares about was to get through to the next year. But now it's different. Soon he would graduate and need to start looking for a job. He realized it takes more than good grade to get him that. He realized he didn't even know how it looks like to work in the real world.
A young professional had been dreaming to work overseas. He didn't know how to get there but that was his target in life. He did his best to make a good resume and kept sending it to many recruiting agencies around the world without many responses so far. He wished someone was willing to give him hints and share the experience so he can just follow it.
He's been working as professional in several different countries for many years. He remembered how it was not easy to get into his current position. He could still recall all the interviews he had to go through every time he switched job. How he learned to build connection and reputation at work. Now he feels like it's time to pay back. He's planning to share his experience to others.
Do you think the three stories above are real? Any of them?
I was a student and even after I graduated I didn't know how to find a job. I always wanted to work overseas, but I didn't know how to do it or whether I had the expertise to be able to compete in International market. Good thing I passed my CCIE lab. And it was still not easy because obviously certification is not enough. Even with expertise and experience I still spent many years trying to get a job in Cisco. I had to go through many projects, had to build connection and reputation, before finally Cisco gave me a chance for the interview.
So for me the stories are real. And they are the reasons why I founded Project Avatar.
I want to build a community for professionals and students so they can help each other to achieve their target to compete globally. Experienced professional can help by sharing his knowledge to younger professional. And by doing that at the same time he demonstrates his leadership and coaching skill to the world. Professional can share his experience to the students so at least they get some clue how the working environment looks like. And by doing that the professional will become a better professional. Every time you share your knowledge you gain more. Every time you give free gift to some people they will do the same to some other people. So then we build the culture of giving gift. Students someday will become professional too and they will continue this chain of knowledge-sharing culture.
That's the value that I believe we are doing with Project Avatar.
And that's also the reason why in the beginning I self-funded this project. That's the same reason why I spend time outside my 40-hour a week for Cisco to keep the website alive. And why during the weekend night I spent my time to write this blog :)
And I believe in that value. I believe in my reasons.
What do you believe?
A young professional had been dreaming to work overseas. He didn't know how to get there but that was his target in life. He did his best to make a good resume and kept sending it to many recruiting agencies around the world without many responses so far. He wished someone was willing to give him hints and share the experience so he can just follow it.
He's been working as professional in several different countries for many years. He remembered how it was not easy to get into his current position. He could still recall all the interviews he had to go through every time he switched job. How he learned to build connection and reputation at work. Now he feels like it's time to pay back. He's planning to share his experience to others.
Do you think the three stories above are real? Any of them?
I was a student and even after I graduated I didn't know how to find a job. I always wanted to work overseas, but I didn't know how to do it or whether I had the expertise to be able to compete in International market. Good thing I passed my CCIE lab. And it was still not easy because obviously certification is not enough. Even with expertise and experience I still spent many years trying to get a job in Cisco. I had to go through many projects, had to build connection and reputation, before finally Cisco gave me a chance for the interview.
So for me the stories are real. And they are the reasons why I founded Project Avatar.
I want to build a community for professionals and students so they can help each other to achieve their target to compete globally. Experienced professional can help by sharing his knowledge to younger professional. And by doing that at the same time he demonstrates his leadership and coaching skill to the world. Professional can share his experience to the students so at least they get some clue how the working environment looks like. And by doing that the professional will become a better professional. Every time you share your knowledge you gain more. Every time you give free gift to some people they will do the same to some other people. So then we build the culture of giving gift. Students someday will become professional too and they will continue this chain of knowledge-sharing culture.
That's the value that I believe we are doing with Project Avatar.
And that's also the reason why in the beginning I self-funded this project. That's the same reason why I spend time outside my 40-hour a week for Cisco to keep the website alive. And why during the weekend night I spent my time to write this blog :)
And I believe in that value. I believe in my reasons.
What do you believe?
Thursday, May 26, 2011
Two Laws - Rewrite
Several years ago I invented something that I called 2-Law of Desperate Workers:
Law 1: To get a better job, you need to have good experience and build good working experience profile
Law 2: In order to get good experience and build good working experience profile, you need to work in a better job
So you are not happy with your current workplace because it doesn't offer good experience. You want to move to a better company, but they are looking for someone with good experience. And to get that good experience, you need to work in a better company.
You can use professional certification like CCIE to remedy the 2 Law issue. Taking CCIE lab won’t give you large scale deployment experience, but at least it’s close enough to teach you about some design aspect, setup and troubleshoot complex technology in much smaller scale. And it can show your willingness to learn, your self-discipline during the study, and your ability to tackle such difficult challenge. Obviously once you are able to move to a better job with your CCIE, you need to start getting the real good experience.
The other way is by making connection and helping others in the community like Project Avatar. Not only it can give you more experience in leadership, coaching skill, and teaming up with others, it will also make people recognize you and it would be easier for them to give you reference (remember, it's 'who knows you' that matter).
It's not easy to write to share your knowledge. It takes effort to answer other questions or to conduct live presentation over web conference. But if you are willing to do so, you will build a stronger profile and get additional experience that you may not be able to get at your current workplace. And all the experience and reference you make now may help you in the future.
So help others to help yourself. Let's start it on Project Avatar.
Law 1: To get a better job, you need to have good experience and build good working experience profile
Law 2: In order to get good experience and build good working experience profile, you need to work in a better job
So you are not happy with your current workplace because it doesn't offer good experience. You want to move to a better company, but they are looking for someone with good experience. And to get that good experience, you need to work in a better company.
You can use professional certification like CCIE to remedy the 2 Law issue. Taking CCIE lab won’t give you large scale deployment experience, but at least it’s close enough to teach you about some design aspect, setup and troubleshoot complex technology in much smaller scale. And it can show your willingness to learn, your self-discipline during the study, and your ability to tackle such difficult challenge. Obviously once you are able to move to a better job with your CCIE, you need to start getting the real good experience.
The other way is by making connection and helping others in the community like Project Avatar. Not only it can give you more experience in leadership, coaching skill, and teaming up with others, it will also make people recognize you and it would be easier for them to give you reference (remember, it's 'who knows you' that matter).
It's not easy to write to share your knowledge. It takes effort to answer other questions or to conduct live presentation over web conference. But if you are willing to do so, you will build a stronger profile and get additional experience that you may not be able to get at your current workplace. And all the experience and reference you make now may help you in the future.
So help others to help yourself. Let's start it on Project Avatar.
Monday, May 16, 2011
Who Knows You?
A friend of mine told me once: it's not what you know, it's who you know. I disagree. I think the right statement is: it's who knows you. The complete sentence is: it's who knows you, then what you know and what you have done count in later stage.
A strong connection may be able to give you a job directly (I have seen this, it's common practice in development country like in my home country). But a good connection may only land you to job interview. Hence what you know and what you have done in the past are required to pass the interview and get the job.
How to make people know you? One way is by sharing your knowledge. If you know something write it in the blog, answer people's questions, conduct presentation through web conference, and so on. Even if you think the knowledge has less value for others, because others may think otherwise! And by doing this, you make people know you.
Project Avatar provides the facilities for the community member to share the knowledge, ideas or lesson learned from past experience. Spread the knowledge even if you think it's not the greatest idea or the most complicated in the world. Something you know might be valuable information for others.
Convey, even it's only a single word.
A strong connection may be able to give you a job directly (I have seen this, it's common practice in development country like in my home country). But a good connection may only land you to job interview. Hence what you know and what you have done in the past are required to pass the interview and get the job.
How to make people know you? One way is by sharing your knowledge. If you know something write it in the blog, answer people's questions, conduct presentation through web conference, and so on. Even if you think the knowledge has less value for others, because others may think otherwise! And by doing this, you make people know you.
Project Avatar provides the facilities for the community member to share the knowledge, ideas or lesson learned from past experience. Spread the knowledge even if you think it's not the greatest idea or the most complicated in the world. Something you know might be valuable information for others.
Convey, even it's only a single word.
Friday, May 07, 2010
Leadership
"First rule of leadership: everything is your fault."
Hopper to Princess Atta, A Bug's Life.
It's really tough to lead.
You can't do it alone, so you have to delegate.
And when the resource is not skillful so you have to do most of the work, it's your fault.
You have to finish the work even the timeframe is unrealistic.
And when there is not enough resource to deliver, it's your fault.
You have to satisfy all the parties, meet the target and make everyone happy.
And when you have to screw yourself days and nights, it's your fault.
You have to maintain the reputation of the organization.
And when everything starts falling apart, it's your fault.
It's really tough to lead indeed.
But I'd prefer to do it again and again.
Because it's worth it.
Hopper to Princess Atta, A Bug's Life.
It's really tough to lead.
You can't do it alone, so you have to delegate.
And when the resource is not skillful so you have to do most of the work, it's your fault.
You have to finish the work even the timeframe is unrealistic.
And when there is not enough resource to deliver, it's your fault.
You have to satisfy all the parties, meet the target and make everyone happy.
And when you have to screw yourself days and nights, it's your fault.
You have to maintain the reputation of the organization.
And when everything starts falling apart, it's your fault.
It's really tough to lead indeed.
But I'd prefer to do it again and again.
Because it's worth it.
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.
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.
Wednesday, September 30, 2009
Ode To The Contractors
"Himawan Nugroho spent his time between jobs last year as a contractor…and discovered it offered a level of control and empowerment that he’d never had before..."
The quote above is taken from an article in this site. It refers to my previous writing about Contractor Wannabe. Well, it's good to know that someone is actually reading that kind of stuff that I wrote :)
I was a contractor, even for only few months. It was during the time when I had resigned from my previous company and before I joined Cisco. Yes, indeed, the article describes exactly how I felt at that time. And I'm discussing again this topic because during the past few projects I've worked with many contractors, and some of them are really helpful.
In this part of the world it's not easy to hire a permanent employee. It takes time and lots of paper work at least for the visa process. And once the project is rewarded we have to start the work immediately, while the process to get someone on board won't be able to catch up. The solution? Hire contractors. They are skillful and available, almost, anytime. How about the working visa? They usually will be involved for short term so business visa should be fine. How about the skill? We can look at their previous experience and even call for quick interview. And once the work has started how if the guy has issue or we are not happy with him? Get the replacement. Easy and no headache. As long as we hire the guy with the right skill and we can allocate the proper work to him, the decision to use the contractors can be really rewarding.
Once I met a guy. He may be the right description of my answer if you'd ask: what do you want to be when you grow old? Single fighter, working for short term, keep moving from one place to another. Living from one hotel to another. His car is always from rental company. He carries his gadgets and magic luggage contains all the stuff he needs to live away from home for months. He got my respect because of the expertise. Got reputation and years of experience. Jason Bourne kind of guy. My kind of guy.
So will I go back to that kind of life style? Not now, at least. Currently I work in a place that I wanted to be. Working in the right team, surrounded by the most talented people. And I have something from my current work that I can't exchange even with a freestyler contractor life: deep level access to the product and technology.
Anyway, I was just trying to build a list of what it takes to become a successful contractor (in network engineering area or technical consulting). With my limited experience as contractor, here it is:
1. Build the reputation. The most important, I believe, are the integrity and responsibility
2. Result oriented. The work must be done successfully no matter what, within the agreed timeline
3. Adaptable, flexible, able to handle the pressure and sudden changes in the project
4. Possess extensive experience in different types of project with multiple roles
5. Able to work independently, but at the same time able to work as part of the team
6. Good communication skill and can easily blend with customers from any types, anywhere, in any circumstances
7. Specialize and focus in one technology area but know other stuff to certain level. For example, expert in Core IP/MPLS network but understand as well the access layer, security, physical layer, data center and so on
8. Able to work as multiple roles: engineer, consultant, architect, project manager etc
9. Always update the skills, fast and continuous learner. Willing to invest on skill update, lab, and any tools that can assist in delivering the work
10. Know how to market yourself: social networking, keep the contacts with previous customers, always update the CV, etc
When I look at the list above, I started to think that the list is a must not only to become a contractor, but as well as to stay competitive in the market even as permanent employee! It may be the one that keep our job during the financial crisis like today. I wouldn't know for sure, but it seems like I will bookmark this post to remind me that even a Triple CCIE can be replaced anytime. And the only ones that can save my job are those 10 points.
To all contractors, this post is for you.
The quote above is taken from an article in this site. It refers to my previous writing about Contractor Wannabe. Well, it's good to know that someone is actually reading that kind of stuff that I wrote :)
I was a contractor, even for only few months. It was during the time when I had resigned from my previous company and before I joined Cisco. Yes, indeed, the article describes exactly how I felt at that time. And I'm discussing again this topic because during the past few projects I've worked with many contractors, and some of them are really helpful.
In this part of the world it's not easy to hire a permanent employee. It takes time and lots of paper work at least for the visa process. And once the project is rewarded we have to start the work immediately, while the process to get someone on board won't be able to catch up. The solution? Hire contractors. They are skillful and available, almost, anytime. How about the working visa? They usually will be involved for short term so business visa should be fine. How about the skill? We can look at their previous experience and even call for quick interview. And once the work has started how if the guy has issue or we are not happy with him? Get the replacement. Easy and no headache. As long as we hire the guy with the right skill and we can allocate the proper work to him, the decision to use the contractors can be really rewarding.
Once I met a guy. He may be the right description of my answer if you'd ask: what do you want to be when you grow old? Single fighter, working for short term, keep moving from one place to another. Living from one hotel to another. His car is always from rental company. He carries his gadgets and magic luggage contains all the stuff he needs to live away from home for months. He got my respect because of the expertise. Got reputation and years of experience. Jason Bourne kind of guy. My kind of guy.
So will I go back to that kind of life style? Not now, at least. Currently I work in a place that I wanted to be. Working in the right team, surrounded by the most talented people. And I have something from my current work that I can't exchange even with a freestyler contractor life: deep level access to the product and technology.
Anyway, I was just trying to build a list of what it takes to become a successful contractor (in network engineering area or technical consulting). With my limited experience as contractor, here it is:
1. Build the reputation. The most important, I believe, are the integrity and responsibility
2. Result oriented. The work must be done successfully no matter what, within the agreed timeline
3. Adaptable, flexible, able to handle the pressure and sudden changes in the project
4. Possess extensive experience in different types of project with multiple roles
5. Able to work independently, but at the same time able to work as part of the team
6. Good communication skill and can easily blend with customers from any types, anywhere, in any circumstances
7. Specialize and focus in one technology area but know other stuff to certain level. For example, expert in Core IP/MPLS network but understand as well the access layer, security, physical layer, data center and so on
8. Able to work as multiple roles: engineer, consultant, architect, project manager etc
9. Always update the skills, fast and continuous learner. Willing to invest on skill update, lab, and any tools that can assist in delivering the work
10. Know how to market yourself: social networking, keep the contacts with previous customers, always update the CV, etc
When I look at the list above, I started to think that the list is a must not only to become a contractor, but as well as to stay competitive in the market even as permanent employee! It may be the one that keep our job during the financial crisis like today. I wouldn't know for sure, but it seems like I will bookmark this post to remind me that even a Triple CCIE can be replaced anytime. And the only ones that can save my job are those 10 points.
To all contractors, this post is for you.
Monday, June 29, 2009
Cisco Certified Architect
You might be surprised, but many people have come to me to seek advice about the career in networking area. Yes, I know, I know. Who am I to give the advice, right? But despite the fact that I have only 10 years experience, that I don't have any computer related degree, and I have actually written down how I climbed the steps starting from the day I learned to spell 'Cisco' until where I stand today in my blog, I still get such question over the emails.
So in order for me to save the energy to write the answer over and over again, and to save the bandwidth required to exchange the emails, please allow me to introduce the levels of networking engineers career I made that I called as "Network Engineer Technical Skill Transformation". Obviously the engineer won't transform to Camaro even if the Allspark aka cube did really exist.
Please be warned that everything I write here is based on my own experience. If you don't like it, just try to do it your way and make your own levels! You don't have to agree or follow my levels. I won't give you any rewards or certifications even if you do. All I want to do is to provide some kind like brief information based on what I have been through and I have seen on my way to reach my current position. And it may be useful for those who want to start or move their career to networking area but still clueless about the path.
To make it more fascinating, I tried to link the levels with the Cisco certification program.
Level 1: Configurator
The other name for this level is Config T engineer, where ones only know how to put the configuration without having deep understanding about the concept and the reason behind it. What it takes just the ability to copy paste the configuration from Cisco website to enable the protocols or features.
If I may compare it with Cisco certification program, this level can be considered as CCNA.
Level 2: Troubleshooter
Those who don't know the concept won't be able to troubleshoot. At this level ones know how to configure the protocols/features, and the concept behind it in order to troubleshoot when there is any issue during implementation.
If I may compare it with Cisco certification program, this level shall be the CCNP or other mid-level certifications.
Level 3: Specialist
At this level, the engineers are willing to focus on a particular area in networking. This is not a pure specialist role since most probably those still have to do the common routing and switching stuff, but now they are capable to work on other technology too where they put more focus to learn.
I shall put CCIE at this level. Even those who have CCIE in Routing & Switching track can fall to this level since they put their focus on the scope of the track.
Level 4: Designer
After focusing on one particular area at the previous level, at this level ones must learn more general and broad knowledge again. The other name of this level is System Integrator, where it is required to possess the ability to combine different technology solutions, sometime it even requires to combine the products from different vendors. As a network designer, one must be able to build a complete infrastructure solution from routing and switching, security, voice, wireless etc. And it is normal for a designer to have the knowledge beyond networking: Server Operating System, Database, physical Data Center and so on.
I don't think there is certification for this level. Well, CCDE may provide the foundation of the knowledge for this. But I would say it's like CCIE with project experiences to build a complete infrastructure.
Level 5: Architect
This is the next level of System Integrator, where ones know how to build a complete infrastructure, and understand the customer business requirements, and can make sure the technology and solution provided to answer the requirements incorporate the customer business model. From technical perspective, the architects understand hardware architecture and the way the protocols work in detail, in order to know the limitation of solution can be provided. They know the standard of the protocols and fully aware about different implementation from different vendors, so they are able to fully interop the products from multiple vendors.
This is like a CCIE who likes to read the protocol standards, understand the hardware architecture, able to interop products from multiple vendors, and has extensive project experiences with important role in both technical and non-technical aspect.
Level 6: Expert
The last transformation is to the expert level, after being the architect with extensive project experience, capable to build a complex and complete infrastructure from different vendors, and understand customer business requirements and the linkage to the technology and solution provided. At this level, ones are getting specialized again. Having extensive experiences and broad knowledge, the experts now can focus on one or a few particular technology in order to contribute to the development of that technology. Experts communicate to each other to develop the standard of networking, translate a difficult concept into the words that can be understood by ordinary people, and share the knowledge and information to the others.
At this level, the possession of any certification doesn't matter anymore. The most important is to have all what the Architect level has, with focus on one of few technology in deep detail, willing to contribute to the development of the technology, and share the knowledge and information to the others.
I have to remind you again, the above levels are mine. And the linkage to the Cisco certification program is based on my own definition. I have actually written down these levels definition since few weeks ago in my other blog.
Today, Cisco announced the new certification and the highest level ever called Cisco Certified Architect. If you look at the description of this certification, it's similar with my Architect level. You need at least 10 years experience. You need to apply and must be accepted to take the exam. The format is board exam, where you have to present your solution in front of several engineers, and must be able to change it on the fly based on the additional requirements on the board. And there is a rumor flying around saying that the engineers who will sit there to test you are Cisco Distinguished Engineers :)
I took my first CCIE when it was still two days exam. I enjoyed the last 2.5 hours dedicated for troubleshooting section. And I won't forget the time after the exam to explain to the proctor why I configured something the way I did it, sometime I even needed to draw in the white board to explain. The CCIE exam today, I believe, lack those two (troubleshooting and explaining the reason of the configuration) in order to claim as the highest level for network engineers to implement and deploy the solution. CCIE is not a design exam, and there is no design aspect tested in the lab. That's why Cisco then came up with CCDE. But still with this design exam, even I haven't taken it, but I feel like it's missing some designer knowledge. For example, there is no way to test the ability to capture the requirements from the initial meeting with the customer. Or the skills to lead the design workshop. And the CCDE exam for sure will not test the designer skill to adjust the solution if the customer modify or add additional requirements in the middle of the project. That's where Cisco Certified Architect can fill the gap.
Still though, even you can pass the Cisco Certified Architect exam or get the 'Architect' as job title, I believe your life is not completed if you haven't transformed to the highest level. The expert level. This is something that everyone in this field must put his goal at. We all must aim to reach this level, to be recognized as those who help the world developing the technology.
The expert level is something that must be earned.
So in order for me to save the energy to write the answer over and over again, and to save the bandwidth required to exchange the emails, please allow me to introduce the levels of networking engineers career I made that I called as "Network Engineer Technical Skill Transformation". Obviously the engineer won't transform to Camaro even if the Allspark aka cube did really exist.
Please be warned that everything I write here is based on my own experience. If you don't like it, just try to do it your way and make your own levels! You don't have to agree or follow my levels. I won't give you any rewards or certifications even if you do. All I want to do is to provide some kind like brief information based on what I have been through and I have seen on my way to reach my current position. And it may be useful for those who want to start or move their career to networking area but still clueless about the path.
To make it more fascinating, I tried to link the levels with the Cisco certification program.
Level 1: Configurator
The other name for this level is Config T engineer, where ones only know how to put the configuration without having deep understanding about the concept and the reason behind it. What it takes just the ability to copy paste the configuration from Cisco website to enable the protocols or features.
If I may compare it with Cisco certification program, this level can be considered as CCNA.
Level 2: Troubleshooter
Those who don't know the concept won't be able to troubleshoot. At this level ones know how to configure the protocols/features, and the concept behind it in order to troubleshoot when there is any issue during implementation.
If I may compare it with Cisco certification program, this level shall be the CCNP or other mid-level certifications.
Level 3: Specialist
At this level, the engineers are willing to focus on a particular area in networking. This is not a pure specialist role since most probably those still have to do the common routing and switching stuff, but now they are capable to work on other technology too where they put more focus to learn.
I shall put CCIE at this level. Even those who have CCIE in Routing & Switching track can fall to this level since they put their focus on the scope of the track.
Level 4: Designer
After focusing on one particular area at the previous level, at this level ones must learn more general and broad knowledge again. The other name of this level is System Integrator, where it is required to possess the ability to combine different technology solutions, sometime it even requires to combine the products from different vendors. As a network designer, one must be able to build a complete infrastructure solution from routing and switching, security, voice, wireless etc. And it is normal for a designer to have the knowledge beyond networking: Server Operating System, Database, physical Data Center and so on.
I don't think there is certification for this level. Well, CCDE may provide the foundation of the knowledge for this. But I would say it's like CCIE with project experiences to build a complete infrastructure.
Level 5: Architect
This is the next level of System Integrator, where ones know how to build a complete infrastructure, and understand the customer business requirements, and can make sure the technology and solution provided to answer the requirements incorporate the customer business model. From technical perspective, the architects understand hardware architecture and the way the protocols work in detail, in order to know the limitation of solution can be provided. They know the standard of the protocols and fully aware about different implementation from different vendors, so they are able to fully interop the products from multiple vendors.
This is like a CCIE who likes to read the protocol standards, understand the hardware architecture, able to interop products from multiple vendors, and has extensive project experiences with important role in both technical and non-technical aspect.
Level 6: Expert
The last transformation is to the expert level, after being the architect with extensive project experience, capable to build a complex and complete infrastructure from different vendors, and understand customer business requirements and the linkage to the technology and solution provided. At this level, ones are getting specialized again. Having extensive experiences and broad knowledge, the experts now can focus on one or a few particular technology in order to contribute to the development of that technology. Experts communicate to each other to develop the standard of networking, translate a difficult concept into the words that can be understood by ordinary people, and share the knowledge and information to the others.
At this level, the possession of any certification doesn't matter anymore. The most important is to have all what the Architect level has, with focus on one of few technology in deep detail, willing to contribute to the development of the technology, and share the knowledge and information to the others.
I have to remind you again, the above levels are mine. And the linkage to the Cisco certification program is based on my own definition. I have actually written down these levels definition since few weeks ago in my other blog.
Today, Cisco announced the new certification and the highest level ever called Cisco Certified Architect. If you look at the description of this certification, it's similar with my Architect level. You need at least 10 years experience. You need to apply and must be accepted to take the exam. The format is board exam, where you have to present your solution in front of several engineers, and must be able to change it on the fly based on the additional requirements on the board. And there is a rumor flying around saying that the engineers who will sit there to test you are Cisco Distinguished Engineers :)
I took my first CCIE when it was still two days exam. I enjoyed the last 2.5 hours dedicated for troubleshooting section. And I won't forget the time after the exam to explain to the proctor why I configured something the way I did it, sometime I even needed to draw in the white board to explain. The CCIE exam today, I believe, lack those two (troubleshooting and explaining the reason of the configuration) in order to claim as the highest level for network engineers to implement and deploy the solution. CCIE is not a design exam, and there is no design aspect tested in the lab. That's why Cisco then came up with CCDE. But still with this design exam, even I haven't taken it, but I feel like it's missing some designer knowledge. For example, there is no way to test the ability to capture the requirements from the initial meeting with the customer. Or the skills to lead the design workshop. And the CCDE exam for sure will not test the designer skill to adjust the solution if the customer modify or add additional requirements in the middle of the project. That's where Cisco Certified Architect can fill the gap.
Still though, even you can pass the Cisco Certified Architect exam or get the 'Architect' as job title, I believe your life is not completed if you haven't transformed to the highest level. The expert level. This is something that everyone in this field must put his goal at. We all must aim to reach this level, to be recognized as those who help the world developing the technology.
The expert level is something that must be earned.
Friday, February 20, 2009
Title or Money?
According to the survey in the radio, people are more happy with their job designation compare to the salary. So it means they would rather have a nice job title even with less salary. Really? For me no, thanks, please give any title you want as long as the money is more.
But seriously, I don't think all of us agree with that survey. What's the meaning of job title? Once I refused a job offer with designation: Network Solution Architect for the whole region, because even the money was good too but the scope of the work is more in contract documentation and not doing the 'real' network solution.
So for me, it's not even the money that matters. It's more like what I do is the most important, compare to the title or the money. I want the job that makes me do things that I like, otherwise I will do it just to get survived. And fortunately we live in a strange world, where people who do things they like normally make more money :)
Just like in Batman: It's not who you are underneath, it's what you do that defines you.
Hmm, I should get a Bat Mobil instead of British 4WD.
But seriously, I don't think all of us agree with that survey. What's the meaning of job title? Once I refused a job offer with designation: Network Solution Architect for the whole region, because even the money was good too but the scope of the work is more in contract documentation and not doing the 'real' network solution.
So for me, it's not even the money that matters. It's more like what I do is the most important, compare to the title or the money. I want the job that makes me do things that I like, otherwise I will do it just to get survived. And fortunately we live in a strange world, where people who do things they like normally make more money :)
Just like in Batman: It's not who you are underneath, it's what you do that defines you.
Hmm, I should get a Bat Mobil instead of British 4WD.
Wednesday, September 03, 2008
The Road Less Traveled
Last Saturday I gave a free lecture in my former university with the topic "How to compete in global networking market by becoming a CCIE". I was invited first just to give information on how to become CCIE, pretty much to deliver the same presentation I did in Networkers Indonesia early this year. But then I thought most of the audiences are students, even though the lecture is opened for professionals too, and they may need more information about the career in networking field instead. So I called some of my CCIE colleagues to come and tell the story about their career – how did they start, what drives them to continue, how they got support to finance their CCIE lab, where are they today as CCIE, and so on – which I believe it’s more important for those students to hear.
So I started the lecture by introducing myself and share the story about my life and how I started my journey. I also mentioned that the tipping point of my life was after I passed my first CCIE lab. That made me able to start moving around and competing in the global networking market from Asia to Middle East, and finally I’m able to join Cisco Advanced Services as what I always want to. My friend who works in Cisco product development team in San Jose, who happened to be in country for vacation, shared his story about how he had to drop his master degree to pursue CCIE. But it was worth it, though. Once he passed, he’d been working in large scale projects ever since until he decided to take the offer to go to US though consulting agency. And now he has worked for Cisco Systems San Jose in few different business units. One other friend told the story of what he had to give up to finance his CCIE lab: his home. It was definitely a very hard decision since he’s married with few kids. But he took the risk, passed the exam, and moved to a bigger company that can return him his investment. The last friend shared his experience in passing CCIE lab in first attempt, then decided to stick in the same company until he became senior manager, one option that may be taken by any CCIE after they get bored abusing networking gears.
I didn’t stop only with stories. I shared my point of view of the career in networking in general, then the engineering career in Cisco Systems as what I see, I hear and I have been through. Once I believe the class has got clear picture about it, and definitely I didn’t forget to mention one way to boost the career is by passing CCIE lab, I also shared my opinion about How to Become Engineer ++, which explains on few things that every engineer should have and the way to distinguish ourselves in the global competition. Before I repeated my slide on How to Become CCIE, I did few slides on How to Start Your Career in Networking which I believe is important too since most of the time the first step to begin is the most difficult step. Those are actually based on my writings in my other blog in native language.
Does it sound lame to you? Well, for them who have seen and done many, it’s kinda waste of time to listen to such thing. But for those students who don’t know what the career in real networking world is all about , or professionals who want to switch their career to networking, the lecture may be a good information and as something to begin with. The class was full, by the way. Those folks who arrange this event must even rejected some guys to enter the class since there is no more space available even they still insist to join. And even the lecture was recorded, and it was broadcasted as well to other universities in my country, I know it’s still can’t beat the experience to have a discussion directly with the presenters. Especially since I brought some merchandises from Cisco for the raffle draw in the end of the lecture. Well, students are the same everywhere. They need free goodies :). That may be the only reason why most of them stayed for 4 hours that day.
I have to admit as much as I enjoy giving speech in public to try to convince others, deep inside I like to do this to convince myself too. I mean my journey in networking field is getting harder and harder, and I have moved to new position several times when I have reached the top level in my current position. Everytime I get comfortable, I move. And it’s not as easy as it looks like. I have to start from beginning, understand the process and build the relationship again. So giving free lecture like this offers mutual benefits; for others to hear about all decisions I took to reach my level today and learn from all my mistakes, and for me to convince myself that I have to carry on so I can continue to spread the information.
Robert Frost once wrote, I took the one (road) less traveled by, and that has made all the difference. So no matter how hard it is, somebody has to do this journey. Somebody must take the risk. And one who has done it should share the story to others. To share the information. To make the history. And, to be immortalized.
I hereby offer to anyone interested, everytime I travel and when I have spare time, I’m opened for the invitation to give similar lecture in any location to anyone without exceptions. Obviously as time goes by my story will grow longer and longer, even How to Become CCIE will still be the main part. Everyone likes to hear story and they want to get the most updated one. The most challenging, the break through, and full of new adventures as eye-opener. This mean I must not stop the journey. I should not stay in my comfort zone. I shall continue to go where there is no path and leave the trail. And in order to support this idea, I will post my schedule in the Where Am I? sidebar of this blog so anyone willing to arrange the class can get the idea of the best time to do so. For example, I will be in Brussels in mid September then Czech Republic until end of the month, then I will be in Spain during the first week of October. I'm willing to give the lecture to anyone and in any location, but please remember I can do it only in English, or in my native language of course.
I’m a pioneer. A dreamer, a blogger, a traveler.
I’m a storyteller, and this is my story.
So, free lecture, anyone?
- The things taught in schools and colleges are not an education, but the means to an education. (Ralph Waldo Emerson)
So I started the lecture by introducing myself and share the story about my life and how I started my journey. I also mentioned that the tipping point of my life was after I passed my first CCIE lab. That made me able to start moving around and competing in the global networking market from Asia to Middle East, and finally I’m able to join Cisco Advanced Services as what I always want to. My friend who works in Cisco product development team in San Jose, who happened to be in country for vacation, shared his story about how he had to drop his master degree to pursue CCIE. But it was worth it, though. Once he passed, he’d been working in large scale projects ever since until he decided to take the offer to go to US though consulting agency. And now he has worked for Cisco Systems San Jose in few different business units. One other friend told the story of what he had to give up to finance his CCIE lab: his home. It was definitely a very hard decision since he’s married with few kids. But he took the risk, passed the exam, and moved to a bigger company that can return him his investment. The last friend shared his experience in passing CCIE lab in first attempt, then decided to stick in the same company until he became senior manager, one option that may be taken by any CCIE after they get bored abusing networking gears.
I didn’t stop only with stories. I shared my point of view of the career in networking in general, then the engineering career in Cisco Systems as what I see, I hear and I have been through. Once I believe the class has got clear picture about it, and definitely I didn’t forget to mention one way to boost the career is by passing CCIE lab, I also shared my opinion about How to Become Engineer ++, which explains on few things that every engineer should have and the way to distinguish ourselves in the global competition. Before I repeated my slide on How to Become CCIE, I did few slides on How to Start Your Career in Networking which I believe is important too since most of the time the first step to begin is the most difficult step. Those are actually based on my writings in my other blog in native language.
Does it sound lame to you? Well, for them who have seen and done many, it’s kinda waste of time to listen to such thing. But for those students who don’t know what the career in real networking world is all about , or professionals who want to switch their career to networking, the lecture may be a good information and as something to begin with. The class was full, by the way. Those folks who arrange this event must even rejected some guys to enter the class since there is no more space available even they still insist to join. And even the lecture was recorded, and it was broadcasted as well to other universities in my country, I know it’s still can’t beat the experience to have a discussion directly with the presenters. Especially since I brought some merchandises from Cisco for the raffle draw in the end of the lecture. Well, students are the same everywhere. They need free goodies :). That may be the only reason why most of them stayed for 4 hours that day.
I have to admit as much as I enjoy giving speech in public to try to convince others, deep inside I like to do this to convince myself too. I mean my journey in networking field is getting harder and harder, and I have moved to new position several times when I have reached the top level in my current position. Everytime I get comfortable, I move. And it’s not as easy as it looks like. I have to start from beginning, understand the process and build the relationship again. So giving free lecture like this offers mutual benefits; for others to hear about all decisions I took to reach my level today and learn from all my mistakes, and for me to convince myself that I have to carry on so I can continue to spread the information.
Robert Frost once wrote, I took the one (road) less traveled by, and that has made all the difference. So no matter how hard it is, somebody has to do this journey. Somebody must take the risk. And one who has done it should share the story to others. To share the information. To make the history. And, to be immortalized.
I hereby offer to anyone interested, everytime I travel and when I have spare time, I’m opened for the invitation to give similar lecture in any location to anyone without exceptions. Obviously as time goes by my story will grow longer and longer, even How to Become CCIE will still be the main part. Everyone likes to hear story and they want to get the most updated one. The most challenging, the break through, and full of new adventures as eye-opener. This mean I must not stop the journey. I should not stay in my comfort zone. I shall continue to go where there is no path and leave the trail. And in order to support this idea, I will post my schedule in the Where Am I? sidebar of this blog so anyone willing to arrange the class can get the idea of the best time to do so. For example, I will be in Brussels in mid September then Czech Republic until end of the month, then I will be in Spain during the first week of October. I'm willing to give the lecture to anyone and in any location, but please remember I can do it only in English, or in my native language of course.
I’m a pioneer. A dreamer, a blogger, a traveler.
I’m a storyteller, and this is my story.
So, free lecture, anyone?
- The things taught in schools and colleges are not an education, but the means to an education. (Ralph Waldo Emerson)
Friday, February 15, 2008
Best Advice of the Day
"You don't get promoted because you work hard, or because you work long hours, and deliver superb result.. You have already been paid for that! But in order to achieve the highest level in a company you must work extra and able to distinguish yourself by volunteering and sacrificing your free time to deliver something outside your job description, to bring values for the company and people around you."
Amen, brother.
Most of us tend to believe that if we work hard then we will get noticed by the company one day and collect the rewards. That's not how it works anymore. When you are in a very competitive place, everyone works hard. Everyone works long hours. And everyone delivers superb results. So the question is: how to distinguish ourselves in order to be in the spotlight?
The answer is by doing something extra. We should do something outside our work time, to deliver something outside our scope, and willing to do so without any directions from the company. In other word, we should volunteer to do something extra. And there is no guarantee after all those things we do, we can get our reward.
What's the main point here? Do something extra for yourself and only because you like it. If you try to volunteer but expect to get something in the end, then be ready to get disappointed. Just do it for yourself. And do it because you really like it.
By the way, the advice above was from one of the few Cisco Advanced Services Distinguished Engineer. He got into what he is today because he applies this principle. And he is the living proof of his own words. Distinguished Engineer is not a position in Cisco that you can apply. Many people must recognize you and raise your name to the committee. And those people are not only from the team where you have been working with, but as well as from another team or from different organization. The only way to make people realize that you exist is by volunteering yourself to do something extra, and to deliver something outside your own scope.
So please remember next time you think that you have worked like hell, you have spent days and nights to deliver the best output, and you think you deserve to get into top notch position.
Well, think again. Everyone does the same.
And we all have already been paid for that.
Amen, brother.
Most of us tend to believe that if we work hard then we will get noticed by the company one day and collect the rewards. That's not how it works anymore. When you are in a very competitive place, everyone works hard. Everyone works long hours. And everyone delivers superb results. So the question is: how to distinguish ourselves in order to be in the spotlight?
The answer is by doing something extra. We should do something outside our work time, to deliver something outside our scope, and willing to do so without any directions from the company. In other word, we should volunteer to do something extra. And there is no guarantee after all those things we do, we can get our reward.
What's the main point here? Do something extra for yourself and only because you like it. If you try to volunteer but expect to get something in the end, then be ready to get disappointed. Just do it for yourself. And do it because you really like it.
By the way, the advice above was from one of the few Cisco Advanced Services Distinguished Engineer. He got into what he is today because he applies this principle. And he is the living proof of his own words. Distinguished Engineer is not a position in Cisco that you can apply. Many people must recognize you and raise your name to the committee. And those people are not only from the team where you have been working with, but as well as from another team or from different organization. The only way to make people realize that you exist is by volunteering yourself to do something extra, and to deliver something outside your own scope.
So please remember next time you think that you have worked like hell, you have spent days and nights to deliver the best output, and you think you deserve to get into top notch position.
Well, think again. Everyone does the same.
And we all have already been paid for that.
Saturday, August 05, 2006
Monster Gulf
Monster, claimed as the World's Leading Career Network, and the place for desperate job seekers like myself, announced Monster Gulf yesterday. This is a good news for anyone who wishes to work in Middle East.The first keyword that I typed in the search engine, obivously, is CCIE. And I couldn't stop laughing when I saw the result.
But seriously, if you are reading this and interested to apply for that job, please forward your CV to me. I can help you to forward it directly to the right person in charge.
Well, at least until the end of this month.
Happy job hunting.
Subscribe to:
Posts (Atom)