To me a team lead is a technical person and he or she should be in a position to lead his team members technically. When any one form your team hits a dead block, he or she should have the confidence in his team lead to get the technical guidance needed so that he or she could proceed furthur from his or her dead block. I did not quite understand your differentiation between team lead and tech lead. I doubt that many companies could afford for such numerous positions in their projects which I find totally pointless.
SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
raghuraman guruswamy wrote:Sorry. I was referring to the project lead position here.
I am not confient enough to take a technical lead position because for the past 4 years i am into production support.
If i had been into dev work for the same period, i would have probably opted for the tech lead role.
Also, i am not sure whether one can become a technical architect in Indian IT service companies.
Your views are welcome.
Being a Technical Architect does not matter if you are in the Product company or in the Services company! So given your kind of experience, better opt for Services companies which will suit your limited technical knowledge.
All these designations and roles have different meaning, different definitions in different companies. Technical Architect in product company with more than 10 to 12 years of solid experience is real Architect. Service and Captive units of MNCs call anyone Architect.
Even project leader, technical leader, solution architect, enterprise architect mean different in different companies.