There's no such thing as someone you're not going to have to train. Every single company does something different. To suggest that you're not going to have months of train up isn't feasible. I wish this mindset would go away. Training is, and should be an integral part of any workplace. It's what makes your whole team better, it's what makes everyone have a similar style, and shows people the expectations. This goes for internal code process as well as external code and tools. Embedded especially is going to be hard because it's a specialized skill set that's far harder than people realize especially once you get into space constraints.
I agree with this 100%, even as an experienced engineer I want to continue to give and receive ongoing training. Yet I've actually been told in some settings not to even mention the "T" word because it would be seen as offensive. Instead as an industry we have ridiculous expectations in hiring and an inefficient, informal training process in the form of production failures.
> There's no such thing as someone you're not going to have to train.
Not for employees but for contractors or consultants they better be able to hit the ground running. That’s why they get paid 3x and up what employees get. If you need someone right now you can pay the premium for it and get it.
my experience is that you have to babysit the senior hires a little bit more because they bring their own baggage and habits into the team even if it doesn't support the existing workflow or even goes against.
they are also more resistant to change than a fresh hire, or may be a bit more convincing when they want things to move their way (to the team's detriment).
if you want to incorporate new cultural elements into your team, especially if your team has already strong, well-developed culture, you have to be aware of what is good and what is bad within your existing team, what to keep and what to give up, and be quick to nip any unintended side effects of a cultural/workflow change in the bud.
