1 year, 11 months ago
What is the difference between "technical depth" and "technical breadth"?
My boss has asked me to basically write my own recommendation for a promotion which is long overdue. He asked me to describe my "technical depth" in one section, then my "technical breadth" in another, along with some other categories that I can easily address.
I'm just not sure how these two are different.
If it helps, I work in our consulting group, implementing complex systems using Linux, Virtualization, Clustering, SANs and other Enterprise solutions. I also do a bit of coding and other open source projects.
I'm just not sure how these two are different.
If it helps, I work in our consulting group, implementing complex systems using Linux, Virtualization, Clustering, SANs and other Enterprise solutions. I also do a bit of coding and other open source projects.
Separate topics with commas, or by pressing return. Use the delete or backspace key to edit or remove existing topics.
You can leave an optional "tip" with Mahalo's virtual currency, Mahalo Dollars. If you are asking a difficult question that might require some research, or if you'd like a wide variety of feedback, a higher tip often leads to more answers to your question.
M$1 Answer
Well, the operative words here are depth and breadth. Simply put, depth applies to an intense understanding of a few topics while breadth applies to a general understanding of many topics.
In discussing technical depth, you need to select a few topics at which you excel the most. The greater your experience level, the deeper your understanding should be on these topics. Personally, I find that identifying 3 to 5 depth areas works best. Explain and reflect on how you excel above and beyond in these areas.
In discussing technical breadth, you need to explain how you have a fundamental knowledge about many of the areas in which your company works and some which your company may consider pursuing soon.You should not be expected to know about all the different technologies your company uses (unless you are becoming a Chief), but breadth represents a variety of skills that can be grown into depths to make you a more versatile employee.
Finally, use this as a chance to emphasize the skills you want to use more and the skill you want to learn more about. A good manager will look for you to describe the things you are truly interested in and make opportunities in those areas available as much as possible (considering availability, demand, time, and money...).
In discussing technical depth, you need to select a few topics at which you excel the most. The greater your experience level, the deeper your understanding should be on these topics. Personally, I find that identifying 3 to 5 depth areas works best. Explain and reflect on how you excel above and beyond in these areas.
In discussing technical breadth, you need to explain how you have a fundamental knowledge about many of the areas in which your company works and some which your company may consider pursuing soon.You should not be expected to know about all the different technologies your company uses (unless you are becoming a Chief), but breadth represents a variety of skills that can be grown into depths to make you a more versatile employee.
Finally, use this as a chance to emphasize the skills you want to use more and the skill you want to learn more about. A good manager will look for you to describe the things you are truly interested in and make opportunities in those areas available as much as possible (considering availability, demand, time, and money...).
source(s):
Professional Experience
Professional Experience
You can leave an optional "tip" with Mahalo's virtual currency, Mahalo Dollars. If you are asking a difficult question that might require some research, or if you'd like a wide variety of feedback, a higher tip often leads to more answers to your question.
M$
I couldn't have said it better myself. One more point on technical depth. You should have at least one area where you are the 'go to' person as the Subject Matter Expert(SME). It is never too late to develop an expertise. Technical folks should always be a Subject Matter Experts in at least one area and have at least one emerging technology under development.
Good luck!
Recommended reading: