I serve as a board-facing member of the executive leadership team, reporting directly to the CEO and overseeing all software engineering and technical support functions for the company. Our product line includes a web-based SaaS application, significant back-end infrastructure on AWS, and an extremely popular open source project called Storybook that is used by engineering teams all over the globe.

I was a founding CTO leading development of a SaaS product based on the services manually provided to customers of a boutique consultancy and sister company. We specialized in high-performance teaming practices based on the Big 5 Personality Test, which is the gold standard in the psychological community for personality research.My role was to establish a new engineering organization from the ground up, working closely with the other business functions to define the feature set, user experience, and platform offering. Given the early nature of this venture I was also responsible for the software architecture, deployment infrastructure, and hands-on development of the systems.

I managed a team of managers within a Salesforce department called Platform Tools and Interfaces. We built and maintained the entire signed in experience for Heroku, both web and CLI, the Salesforce CLI, the oclif CLI framework, the VS Code Extensions for Salesforce, and the Code Builder online editor. I worked closely with leaders in Product and Design to define and drive the Developer Experience for Heroku and Salesforce. I also served as a member of Heroku's Engineering Leadership Team.

I ran a couple of engineering teams that primarily worked with the PR workflows and package registry. I quickly realized the role wasn't what I expected and my values didn't match up with the company's. I reached out to my former manager at Heroku and was fortunate enough to be welcomed back to my prior role.

I oversaw the evolution of the web interface and launched some fantastic features, such as streaming logs and the web console. I drove the application architecture in a direction that allowed us to significantly reduce our operational burden and focus more time on feature development. These efforts were validated by our customer usage data, which saw a shift from customers primarily using the CLI to interact with the platform to the majority of our customers using the dashboard exclusively.

My role was most analogous to a hands-on CTO for startups. I served as a development team lead for external clients, which were often small companies that did not have the resources or expertise to develop and launch a new application internally. I worked closely with them during every step of the process from initial requirements gathering through feature development to the production launch and beyond. During development I made the technical decisions for the project, including selecting service providers and designing system architecture. I also led our internal development team, pairing with other developers every day and writing code. As a project matured, I would perform interviews on behalf of the client and help them build out their own long-term team. I assisted in training their developers on our development process and their application during the final ownership transition. Most notably I was the tech lead and architect for what became Adobe’s Dynamic Tag Management product as well as the ConnectSense IOT platform.My other internal responsibilities included:- training our junior developers on Rails development and consulting- handling job applicants through the entire interview process- participating in sales calls with potential clients- representing the company at conferences, user groups, and other events around the world

I was a Java developer on both major systems within the company: the EDI processing engine and the J2EE web app. I worked with the EDI system team to implement a new HIPAA processing engine. After that, I worked on their monolithic web application, often as a single developer within a project team to implement new feature sets. My largest project was to implement the NPI mandate, which was a major time-sensitive initiative and involved collaboration with numerous individuals around the company as well as enhancements to core inner-workings of the codebases.

Started my career maintaining a series of Perl scripts and C programs that operated their back-end system. I quickly moved to the web team and helped deliver a J2EE system using Struts and Sybase to power their call centers.