I'm leveraging my industry experience to provide career & leadership coaching for software engineers & managers.

Area lead for the *Incident* org of the Axon Productivity pillar, which has now grown beyond Axon Records. My org includes the following teams:1. Report Writing: the crux of the officer experience within Axon Records. This is how police incident data first gets into the system.2. Case Management: the main tool for detectives and prosecutors to add or share case data at the agency. Ultimately help solve crime.3. Form Builder: the internal tool to allow heavy configuration of agency forms and entities. Drastically speeds up our time to deploy at a customer agency.4. Transcription: Ingests huge amounts of bodycam videos from evidence.com and produces user-facing transcripts.5. Mobile App: another zero-to-one effort to allow officers to interact with Axon Records & Evidence on-the-go.Beyond my own org, I was part of a select group of leaders at Axon involved with the following programs at Axon:- ACE: Recruit top talent and act as a "bar-raiser" in hundreds of interviews.- Incident Commander: handle coordination and communication for very high severity production incidents that often span multiple teams/product areas and need regular updates with the customers & exec team until resolution.

In 2020, I helped to grow our team by over 50% as we prepare to launch new features and scale our product to support the majority of Law Enforcement agencies in the US. The highlight of the year includes winning the contract of a top 10 US agency: https://investor.axon.com/press-releases/press-release-details/2020/Baltimore-Police-Department-Deploys-Axon-Records-a-Cloud-Based-RMS-Solution-Agency-wide/default.aspx

I joined Axon as an Engineering Manager working on a new product in 2018. By Sept 2019, we launched Axon Records to our first major customer. I acted as the release manager - the single-threaded owner for this release. You can read about this launch here: https://www.fool.com/investing/2019/10/04/for-axon-records-the-rubber-is-hitting-the-road.aspx

I got promoted to Director came after my success leading the CI/CD efforts at Thunder. I wore many hats during this time as my team grew to include Frontend, Full-stack, test engineers as well as production designers.I participated in hiring for many roles while keeping my team focused on delivering new features and creative designs for our customers. The efforts of my team contributed directly to company revenue and won customers. In addition, I continued to drive engineering excellence and improving processes for our engineers during this time.

I joined PaperG (later rebranded to Thunder) to build the CI and Test team. Through our efforts, we were able to reduce the number of Blocker & Critical bugs that made it to production by over 60% in the first year.I was recognized as the top engineering manager based on an internal survey measuring employee engagement and manager effectiveness.

I joined the Office Web Apps team after the successful internship out of college. I was fortunate to be part of an excellent team to develop and release the first two iterations of a brand new Office product line - bringing Word and OneNote to the web!I held various roles & responsibilities during this time:(2012-2013) Automation Driver: I led a v-team of 8 engineers in an effort to improve our automation infrastructure. I also partnered with other teams in Office to further the overall web automation effort(2011-2012) Setup & Deployment Driver: End-to-end ownership of the team-wide effort for having stable on-prem server deployments, testing setup/deployment, automating the deployments and facilitating team members & partners in deploying our product on a build to build basis.(2011-2012) Browser Driver: End-to-end ownership of the team-wide effort in driving success for testing on multiple browsers. (2010) JavaScript code coverage: Owned an effort of having an internal code coverage tool for JS. Worked with other engineers and partner teams to designing, prototype, and finally handing off to the Office engineering team to have this tool adopted org-wide.In addition to the above "driver roles", I also owned E2E testing for several major product areas including Office Web Apps Server, Word Core Editor and Word Viewer.

This was my final work term/internship while attending the University of Waterloo: a 5-year program that incorporated 2 years of work experience through 6 work terms.During this internship, I learned web UI automation. I worked with both engineers on the team as well as partner teams to design and implement a shared UI object model for automation testing. I delivered UI object models that lived on as the basis for web UI automation in our team. I also learned basic web app testing during this time and acted as the temporary test owner for the "Web Ribbon UI" feature.

I was there during the acquisition of ATI by AMD!This was my last work term at the company before graduating. Highlights includes:- Learned how to use Windbg to disassemble and debug graphics driver code- Learned C# and wrote an internal tool using C# and MFC to help our team debug and fix driver code- Made several bug fixes to the ATI driver codeAll of the above paled in comparison to my extraordinary luck in winning a high-end graphics card at an employee raffle =P

I had three co-op work terms (internship) positions at ATI (prior to their acquisition by AMD) spanning a total of 1 year.In the first term, I acted as the main test contact for ATI driver testing for Microsoft Windows MCE 2005. I maintained a bug database of all driver bugs from our partner Microsoft and corresponded with offsite ATI/Microsoft contacts in Redmond on a weekly basis to discuss bugs and focus of testing. I was in charge of running both manual and automated test cases against Windows MCE and especially test cases around content protection (DRM).My second work term at ATI was more focused on in-depth driver and hardware testing. I did regular WHQL qualification tests on new ATI drivers and helped to develop automated watermark tests to detect graphics corruption. During the end of the work term, I started learning to debug driver code in kernel mode with WinDbg.