[原]Technical skills, or other?

Or, in other word, are technique and ability which excluding technique the same?

I've been working at current company for 2 years, as an software engineer and haven't got any promotion.(I downgraded to work as a software engineer when I joined this company, because I thought in this company senior engineer must be an technique expert.) I thought it's my fault, but now it proves that I'm totally wrong.

Recently 2 engineers were promoted to senior engineer, and one has only 2.5 years of experience (In this company, senior engineers usually have at least 5 years of experience). These 2 guys cannot do any technically hard work. I knew this because my team and I raised some defects which were a little bit technically hard, these 2 guys cannot resolve them. Dramatically, the only one can fix this is a software engineer, in a lower grade. What a poor guy! From them I know, technique is nothing (my ex-boss said), is totally true.

I was thinking about this for a while and found the reason. They have something in common: both are familiar with the dev env of our daily work, and know how to make themselves be heard by boss. The less experienced guy's first assignment was to manage dev board, dev devices, laptops, lab facilities.

Others who don't get promotion also have common figures: they are silent, unwilling to deal with the damned dev env, and skillful.

So now the problem is: what does a senior engineer require? Technique or other abilities such as communication, management, etc., or both? Absolutely, the answer is "both". But what's the reality? It's unfair.