The expert performance that you should be bringing is not your mastery of this particular technology. Your strengths should be: - experience with infrastructur

The expert performance that you should be bringing is not your mastery of this particular technology. Your strengths should be: - experience with infrastructure, so you don't need to have underlying things explained to you - experience with team projects, so you don't get mired in irrelevant sidequests and trivia - experience exercising judgment, so you can survey alternate approaches and pick the one most likely to succeed - experience learning, so you can come up to speed quickly - wide experience, so you can apply lessons from your history in the new context Take the notes, then go back and research them. Figure out what a minimal project in the new domain looks like, and do one quietly. Familiarize yourself with the tools that the new company uses. Read research papers, technical journals, and all the in-company documentation you can get your hands on. Attend new engineer training sessions. Figure out what the schedule is for your group(s) and dig in.