Moved departments from Messaging to Identity and Access Management in 2014 due to my expertise in directory services (specifically Active Directory) tied in with automation with PowerShell. My current focus involves:-Maintain over 100 Github for Enterprise repositories (approximately 14 years worth of PowerShell development). Many projects have been (or still are) used to solve large enterprise projects, including M & A activities. I have also developed a custom PowerShell shell that is used by over 100 IT engineers daily. I am Qualcomm’s subject matter expert on PowerShell and I have a special acknowledgement in one of the more popular books on learning PowerShell: Learn PowerShell in a Month of Lunches 3rd edition.-Service owner for Active Directory and Azure AD (and all subservices such as FIM\MIM, AAD Connect, Microsoft 365, Conditional Access, etc.). These duties include managing a global team that includes staff in India to ensure a strong (and stable) Microsoft Identity Platform.-As the Active Directory service owner my services includes 10 different forests (with the primary corporate forest containing 7 domains). In many cases we have trusts and\or FIM\MIM connecting the forests together (including PCNS to sync passwords). -Currently my Azure AD portfolio consists of 5 different Azure AD tenants (2 are non-production). While most companies would have a single production tenant, Qualcomm engineering has specific security requirements which requires us to use additional tenants.-Design and support a complex set of Azure AD conditional access policies (that includes using Microsoft Graph API to backup\export (and possibly restore) conditional access policies).-Environments include non-Windows systems which both interact and are joined to the domain (such as Mac's and Linux hosts). I provide support when necessary given my background with Linux systems and directory services.

Achievements:-Developed a number of automated processed using PowerShell that has improved business processed and user experiences-Participated in the Exchange 2010 beta TAP\RDP. My comments and involvement are documented in the case study found here: http://www.microsoft.com/casestudies/ServeFileResource.aspx?4000013201-Participated in Exchange 2007 beta TAP\RDP that resulted in me being the lead engineer on the case study for Microsoft found here: http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=200045-Designed the migration path to Exchange 2007 from Exchange 2003\UNIX hosts (running Qpopper and Sendmail)-Mentored messaging staff on different topics. Things such as Active Directory and Exchange technical concepts, PowerShell usage, and UNIX messaging concepts.-Designed and implemented Exchange mailbox provisioning through PowerShell that integrates with identity management systems.-Designed and implemented gateway system for mail list management using PowerShell.Responsibilities:-Currently recognized as the company SME (subject matter expert) in PowerShell. I've been using PowerShell since it was in beta and my current primary focus is in automation and scripting.-Design and support Exchange infrastructure. This includes supporting Exchange 2003, 2007, 2010 servers.-Work closely with UNIX system administrators and designers to ensure that changes to the messaging architecture can adequately support their needs.-Interact heavily with directory services team (Active Directory\iPlanet\eDirectory services) to ensure provisioning processes are properly designed.-Provide tier 3 support for all messaging issues before escalated to responsible vendors (Microsoft, Sophos, McAfee, Ironport\Cisco)-Play a lead role in determining road map direction for all messaging applications (Exchange, Unified Messaging, and Instant Messaging)

Achievements:• Analyzed and improved Exchange 2003 messaging architecture.• Designed and deployed Windows 2003 Distribute File System• Designed and deployed off site Exchange 2003 disaster recovery using XOsoft’s WanSync software.• Designed and deployed off site file server disaster recovery using XOsoft’s WanSync software.Responsibilities:• Analyze existing Exchange 2003 and Windows 2003 infrastructure and make recommendations for improvement• Assist management in technological roadmap and then researching and implementing chosen technologies (one example would be the utilization of XOsoft’s WanSync software)• Provide tier 3 support for Active Directory and Exchange issues.• Act as last line of support before vendor is contacted (primarily Microsoft for Windows or Exchange issues).

Achievements:• Analyzed existing Exchange 2000\5.5 environment and made architectural improvements.• Migrated majority of company off Exchange 5.5 and UNIX mail systems to Exchange 2000 (and eventually upgraded entire enterprise to Exchange 2003)• Assisted with and helped deploy a number of large projects such as deploying PGP to customers who require it and Outlook 2003 as an email client (at the time 70% of Qualcomm used Eudora (a POP client)).• Researched and provided usage documentation for e-mail clients that were commonly used (and supported) against Exchange (namely Outlook, Eudora, Pine, Evolution, Entourage, and Thunderbird).• Designed and deployed monitoring system using NetIQ to monitor the Exchange and Active Directory serversResponsibilities:• Provide tier 3 support (24x7) for both messaging and Active Directory issues. Acting as a last line of support for Exchange issues before escalating to Microsoft.• Played a lead role on the messaging team and mentored 4 other administrators• Lead architect for messaging services of a highly complex environment that is a heavy mix of Exchange and Sendmail machines. Provided direction on where services should be placed, how they should be configured, and what kind of service to provide utilizing technologies such as Microsoft Exchange, Sendmail, Live Communication Server, and Jabber services.• As a senior engineer I was responsible for not only design and support of the messaging infrastructure, but also for road map planning and research, performing highly technical interviews for possible candidates (for Exchange and Active Directory), writing performance reviews for other messaging team members and I regularly get attached to projects that are not always messaging related, but where a senior technical engineer with general industry experience is required