Ask HN: Should you give unsolicited advise?

As I have become a more senior developer and started to manage, mentor and influence junior devs, I often wonder whether you should only give advice or information when asked or whether you should offer (unsolicited) advise.

This also extend for scenarios like being in an "all-hands" meeting and you see something you might know or think it won't work in another department (sales for example). Should you jump in and give your opinion?

Specially when you join a new company, sometimes it could be useful to show you do have knowledge but often you end up in a unidirectional conversation with a junior dev or not making any friends in the sales team.

So how do you handle this balance professionally (and personally)? Do you give unsolicited advise?