All specific identifiers have been replaced by generic terms.
Boss 1: Why rank 1 for The Snake?
Boss 2 : because he worked in Proj1 and Proj2.
Boss 1: In the previous round, with less than 1 year in R&D, you mentioned that you gave The Snake rank 1 because he was rank 1 when in manufacturing.
Boss 2: Yes. The Snake is very dedicated in his job, spend a lot of time in with [project manager], fixed a few problems. He knows a lot about [a product] design, knows a lot of [US] people.
Boss 1: I know he works hard, but my perception is his technical skill is very weak. Not only me, another highly experienced HW engineer think so too.
Boss 2: Well, he was not a design engineer before this job, so it is normal that his technical skill is not the best in my team.
Boss 3: I worked with The Snake, he is a very good engineer.
Boss 2: Ya, very flexible. Can switch between projects without problem. I have plan to promote him to be expert.
BigBoss 1: Ya, I agree with Boss 2. For example, let's compare The Snake vs The Bear. Everyone knows The Bear’s technical knowledge is good, but attitude wise ..... (keep shaking head, flopping hands).
BigBoss 1: The Snake on the other hand, attitude is very good. Although his technical knowledge can be less than The Bear. When you move to expert level, you need to be able to work with others, cannot step on others toe all the time.
Lesson Learnt:
- To be a technical expert (a job level), you don't need good technical knowledge, just be able to work with others.
- It does not matter how good you are technically (which can be proven and tested), bosses can put you down by using subjective innuendoes.
- Sucking up to bosses work.
No comments:
Post a Comment