How recently did you join the company? Perhaps many of these meetings feel useless / non-relevant because you're not as "integrated" with your job yet. Once oth

How recently did you join the company? Perhaps many of these meetings feel useless / non-relevant because you're not as "integrated" with your job yet. Once other developers start depending on your deliverables and vice-versa, those meetings will be more meaningful to you. Also, whenever I (a mere team lead) am on-boarding a new developer, I tend to arrange meetings with them and the leads as a sort of training/orientation on what different teams are working on, who owns what components, and where they can go for help. It can feel overwhelming at the beginning and also not-so-relevant because its not what they are working on directly. That said, if you feel some meetings are stealing too much of your time, talk to your lead / manager about it and see what they think. They should be open and honest about what is and isn't a priority and shouldn't be offended by you asking a fair question. Since a lot of the time meeting invites can be annoyingly vague (no agenda, no notes, no list of things to read / prepare for..), I'll end up messaging the organizer on slack to ask those questions. If I don't feel its relevant I'll ask them directly if they mind if I skip it or if I can send someone else on my team that would be a better fit instead of being a proxy in between them.