Just ask the question. There's no sense beating around the bush. Chances are someone on the team might have the same question and didn't ask it. That's what my

Just ask the question. There's no sense beating around the bush. Chances are someone on the team might have the same question and didn't ask it. That's what my peers have told me at least. If you ask alot of "dumb" questions (e.g. junior level questions while in a senior-position role), you might not be the best for that company. Someone made a mistake down the line in hiring you, likewise you oversold yourself. If a company does not support you learning and getting up to speed with what you should know, it might also not be a great fit for you either. That's not necessarily a bad thing either. Assuming you did your research on the company, and were a good fit for the company, there is no "dumb" questions. It's the company's responsibility to hire the right person for the right seat. Many times you have to ask a question because implementing solutions can be complex. There's multiple solution paths, each with its own pros/cons. You also may not have all the contextual information you need to make a well informed decision. You need to know who to ask for what information, so fire away with questions. Sometimes you get stuck on a problem, but if you know someone already has solved something similar on your team, just ask how they did it. Likewise if someone asks you in return. Knowledge gating doesn't benefit anyone, especially in this industry