Hi SSapaty,
I saw the new people in Developer Advocacy listed in the Technical Community Newsletter and, always happy to see this area strengthened at the WMF, took a look at your user page. I'm very happy to see the WMF putting more resources into this area, so a big welcome from me!
PS. Taking the opportunity since I'm already cluttering up your talk page… The ongoing migration from Gerrit to hosted Gitlabs does not, as far as I've been able to determine, include the technical community among its defined stakeholders. Speaking as a contributor to several community-maintained tools, even just having documentation for how a Toolforge or WMCS-based tool maintainer could and should use the hosted Gitlabs instance for basic source control (nevermind CI or anything fancy) and collaboration would be a huge boon (and would help get community tools 1) use source control, and 2) consolidate the source control into one place instead of a random selection of outside services like Github, Bitbucket, etc.). Having a common account system (on-wiki accounts, developer accounts, and Gitlab accounts) and proper (transparent, automatic) integration between Toolforge and Gitlab would be pure awesome (Toolforge has a management tool to set up teams and co-maintainers; that should automatically get you a Gitlab repo with commit access for that team). Any hand raised, whenever an opportunity arises, as a reminder that this need exists, would be very helpful!