Being new in team

I work in the industry for about 10 years and I realised that most of the time I worked with people I knew before. And they knew me — maybe not personally, sometimes through recommendation or my blog or social channels — anyways, I wasn’t stranger. And my employers weren’t stranger to me. And this year it changed.

It was the first time I had job interviews with people I didn’t know. I really was tested — my way of thinking, my coding skills. I made 2 not so small apps that proven I can code in Ruby or Go. I didn’t feel comfortable even though I think I’m a good programmer. I felt insecure, I felt stupid, especially when I had to talk in English, which I’m not superfluent in (as you may already noticed;)). But that’s not a problem — it was thrilling experience what will happen next.

What was more interesting is “trust” part of relationship with new employer. I had to prove my value to my new employer — maybe I’m wrong, but first months in new job are critical, not as probation period, but how you’ll actually find yourself in new team. It’s the moment when you learn new process, which may be so much different, base on different values than you have. You work with new codebase, so it’s easier to introduce new bug, which may end up with lost trust in your coding skills. You may be the source of team problems, instead of providing solutions. Your ego may hurt you — with too much confidence, lack of confidence, I-know-everything approach etc.

Outside your local market you’re almost no-one. People may not even have heard about ideas you really value, may have totally different authorities. All of this indicates lack of trust, which may end up with disaster.

How can one mitigate such problem? Do the best job she can and take a risk of trusting new team. But also note everything weird in a team, in a process — to work it out someday. Newbie’s eyes may bring much value to team.