Hacker News new | past | comments | ask | show | jobs | submit login

My experience is limited to technical teams in technology companies (primarily CA Bay Area based), as such what I've experienced and learned may not be as applicable to what you're getting into. That said, there are some common things I've noticed, and one is that 'new senior guy' is a disadvantageous position to start in. Generally due to the competitive nature of such places there are others in the team who probably feel they would have been a better choice to fill your new role.

Listen a lot, keep a notebook, don't go in with the idea that you are going to make the product better, go in with the idea that you're trying to find ways to make the team better at making product.

Sometimes that takes mentoring, sometimes that takes technical leadership, sometimes that takes being the person who can help others see each other's perspective.

Be really clear with your manager about what you learn your evaluation of the current situation and look for and listen to feedback to gauge your discernment accuracy.

Always ask people you meet what could you help them with, what would make it easier for them to accomplish what they are trying to accomplish.

Finally, take time to do things that a 'junior engineer' would do as part of the program of helping. People will want to know you can work at all levels and that you aren't just some 'high level thinker' who doesn't understand how things really work.

I have always advised new senior engineer hires, even though you're senior you are going to have to go through your entire career in speed run mode it seems at the new place so that people understand how you got to be senior.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: