The company is pretty big. Traditionally, the engineers have been contractors, but the company is now bringing more development in-house. As such, the teams are going to be growing quickly, and there is a lot of the engineer practice which is undefined. I'm newer to being a software engineer as my "day job" (my previous roles have been in product management, and a few customer-facing roles, like "pre-sales engineer").
The referrals seem to be all over the place! Since I interviewed with a few "levels" of people (engineer, product manager, engineer leadership), everyone has introduced me to a couple different "flavors" of who they consider great in the company. Different departments, titles. So far, they have all been really fun and interesting conversations - hasn't SEEMED to be a chore to folks, but I could be missing something.
"how to you envision us working together" - At the beginning of my personal intro email, I introduced my role and team/group. Since - in the end - its a technology role, I believe that everyone can envision how technology would make their life a little better. There's always something to be automated, an annoying process fixed. I write down the interesting questions people ask, and do my best to research them and follow up, or connect with someone who knows more than I do. Hoping it could help get their problem some attention, and I get to learn about "real" problems in the process.
While my role is not overly broad, I know that since we are planning to grow the team rapidly, there is expectation (I believe) to have an impact and to help scale/onboard the new team members. I am hoping to do a lot of this front-loading NOW, so when I inevitably need to help onboard a new engineer in a few months, I'll hopefully have a bunch of "you need to know this" info handy, and can help introduce them to people I found helpful when joining.
Did that fully answer your question? If not, pile on!
The referrals seem to be all over the place! Since I interviewed with a few "levels" of people (engineer, product manager, engineer leadership), everyone has introduced me to a couple different "flavors" of who they consider great in the company. Different departments, titles. So far, they have all been really fun and interesting conversations - hasn't SEEMED to be a chore to folks, but I could be missing something.
"how to you envision us working together" - At the beginning of my personal intro email, I introduced my role and team/group. Since - in the end - its a technology role, I believe that everyone can envision how technology would make their life a little better. There's always something to be automated, an annoying process fixed. I write down the interesting questions people ask, and do my best to research them and follow up, or connect with someone who knows more than I do. Hoping it could help get their problem some attention, and I get to learn about "real" problems in the process.
While my role is not overly broad, I know that since we are planning to grow the team rapidly, there is expectation (I believe) to have an impact and to help scale/onboard the new team members. I am hoping to do a lot of this front-loading NOW, so when I inevitably need to help onboard a new engineer in a few months, I'll hopefully have a bunch of "you need to know this" info handy, and can help introduce them to people I found helpful when joining.
Did that fully answer your question? If not, pile on!