>How do you go from the "new clueless person at work" to "oh hey Mike, I'll need your help this afternoon"?
There's a people aspect to it, a time aspect, and a technical skills aspect.
For people, you need to develop rapport. A lot of struggle at the beginning is getting to know the right people. This is easier in the office where introductions are more fluid and you run into people.
On the time front, you become an expert on the systems a company employes as your tenure increases. You help design systems and understand the tradeoffs in the decisions that are made rather than walking in and saying "This is odd and I've never seen it before. Why is it done this way?", with answer quality varying on how long ago the decision was made. I've worked at multiple companies where people retire to start collecting their pension and come back a few weeks or months later working as full time consultants because they have deep knowledge of why things are setup like they are, the hiccups that will be encountered during a system change, etc.
You seem confident in the technical aspect, but certainly if you put out work product that doesn't perform well or isn't documented well, people aren't going to proactively be coming to you with questions.
There's a people aspect to it, a time aspect, and a technical skills aspect.
For people, you need to develop rapport. A lot of struggle at the beginning is getting to know the right people. This is easier in the office where introductions are more fluid and you run into people.
On the time front, you become an expert on the systems a company employes as your tenure increases. You help design systems and understand the tradeoffs in the decisions that are made rather than walking in and saying "This is odd and I've never seen it before. Why is it done this way?", with answer quality varying on how long ago the decision was made. I've worked at multiple companies where people retire to start collecting their pension and come back a few weeks or months later working as full time consultants because they have deep knowledge of why things are setup like they are, the hiccups that will be encountered during a system change, etc.
You seem confident in the technical aspect, but certainly if you put out work product that doesn't perform well or isn't documented well, people aren't going to proactively be coming to you with questions.