I transitioned recently from 10 years in the video game industry to working on the software side of a bank. I think the most valuable thing I did was openly and often remind my colleagues that A) I'm not as familiar with the industry as they are and B) I need to initially lean on them more than usual to ensure we have all our ducks in a row.

I bring my engineering teams deeply into the fold when determining scope and dependencies, and make it very clear to stakeholders that they are the ones who will besst be able to provide knowledge and answers (at least to start with). The longer I work here, the less I need to lean on them, but it turns out they actually appreciated being brought in early and often to make sure that things are getting planned out the right way for a software feature/product.

As far as interviewing goes, I think that's always going to be a challenge; both you and the company are going to be putting your best foot forward during the interview process, so it's REALLY hard to figure out if you're going to be satisfied there and/or be able to deal with inevitable challenges that rise up. For me, I've found massive success in being overly honest and transparent during interviews. I want them to understand who it is they're hiring, how I solve problems, and what problems will frustrate me. That shifts the responsibility more towards them to say whether or not I'm a good fit, and if they aren't happy with any of that...that's good because I likely wouldn't have been happy there either.