• Managed Data backend and Interfaces frontend engineering teams• Developed tech leads for teams• Hands-on Interim CISO• Launched new features for $---- ARR growth 2023Q4 - 2024Q2• Over $---- in operational savings via contract negotiations• Started support operations teamI joined Particle as their first dedicated software engineering manager for a smaller engineering team to help scale out process and practice at this startup. Running the data and frontend teams, in Go and React, we launched a new user interface for clinicians to more easily gain information and insights on their patients. Both of those teams now have dedicated tech leads, skilled in Scrum and agile team management practices. As an expansion of my initial efforts I lead the infosec group as acting CISO, managing security practices and running annual audits for SOC2 and HITRUST. I have also partnered with the operations team to stand up a support operations and engineering team.

• Managed two Growth teams• Successfully launched new pricing and packaging• Started growth experimentation• Developed tech leads for teams with active development towards managementHere I set out to do the same again. This time in a Ruby on Rails context instead of Golang. At Wistia we launched new pricing and packaging and ran A/B experiments to optimize growth of our SaaS services. I focused on career development of my engineers including hiring out our second growth team. There I was able to work with another engineer, who became tech lead for the team and now manager. In repeating A/B experimentation I refined my understanding of funnel analysis and the need to run multiple, simultaneous experiments effectively.

• Successfully launched new pricing and packaging• Ran multiple experiments including across pricing and trials• Created new team and developed first time manager for that team• Created mutual support group for new managersIn response to my efforts as a tech lead and engineer to develop my peers I was promoted to engineering management. From there I led projects that included redesigning Splice's pricing and packaging for subscriptions. As a team we revamped subscription management and ran trials using A/B experimentation to optimize signup and retention rates. I hired and built out a growth team to manage the first time user journey, including promoting an engineer to tech lead and then manager for the new team. I also ran the first new manager cohort mutual support group, where five of us shared our learning regularly in order to improve all of our teams as a group.

• Successfully launched checkout redesign• Successfully launched tax collection program including complex grandfathering• Improved bug triage and response process across companyI took over as tech lead for the team in July. I analyzed the remaining work for the tax collection project and determined we required a re-evaluation of project scope in order to successfully launch on time. Prior to releasing tax collection the team completed a checkout redesign in order to support the new paradigms. Tax collection was a complicated project requiring me to learn from the tax attorneys, learn tax calculation software, and learn Recurly, Stripe and PayPal payment collection and subscription software systems. With scope management in partnership with my product manager we shipped on time. As a side project I revamped how Splice managed customer experience initiated bug triage and response, cutting response and resolution times by 90%.

• Sales tax collection architecture and implementationI joined the payments team at Splice, the first project being the implementation of sales tax collection. Here I learned Go and used SQL more extensively than ever before. I had to quickly come up to speed on the complex payments landscape in order to contribute to a difficult project. I practiced empathy and distinguished myself as a leader by actively seeking out opportunities to mutually support my teammates in their careers.

• Lead automation engineer for multiple teams• Primary architect of automation test framework for cloud platformSonos is where I learned cloud computing systems. Working on the cloud platform and later cloud services teams I developed test frameworks in Java and Python to effectively simulate tens of thousands of devices for massive testing purposes. This enabled the launch of our web-based command and control system which powers Spotify and voice services. I learned Apple AirPlay in order to test AirPlay controls for Sonos devices. I lead internal Python training workshops to broaden the skills of my fellow engineers in the Python programming language.

• Lead automation engineer for multiple teams• Developed VLAN product• Solved mutually exclusive filename problems across differing filesystems• Improved ingestion applicationAt Hitachi I was both a software engineer and later SDET working on the Hitachi Content Platform, an on-prem object storage solution. One of the more interesting projects I worked on was rectifying the differences between how different filesystems restrict file naming. This enabled customers to use advanced features of NTFS for metadata storage on files. I used Java daily to develop this and other features, including a standalone ingestion application for users that had not set up an API connection, or who required an initial bulk ingestion tool. As an SDET I mentored junior SDETs and lead the software test efforts for multiple teams, using Python. This was my first real experience in leadership and building a team.

• Improved interpreter performance via profiling• Created advanced remittance distribution algorithmAs a brand new engineer I was thrown into a custom, interpreted programming language. It used an XML-like syntax! It was actually a custom version of a custom programming language using a custom extension of XML, so nothing I could've known beforehand, and it was a functional programming language. I also became an expert in its interpreter, written in C# and running on IIS 5.0. That's where I used code profiling to find that we could make a 90% performance improvement in almost every call. Among other work, before I left I wrote out a distribution algorithm that was an approximate solution to the knapsack problem, an algorithm still in use today.