Galileo is generative AI for website and app designs using industry best practices that can then be exported to Figma or code. I was the first full time employee so had my hands everywhere even setting up much of the infrastructure and helping define the product roadmap.

One of the most impactful projects I owned was implementing export to Figma which, due to the nature of the app and the limited functionality of Figma's plugin API, required reverse engineering Figma's copy/paste functionality and writing an algorithm to convert HTML and CSS to Figma's proprietary format.

Another impactful project was implementing HTML/CSS code export for designs generated in the app. In addition, I built an integration with Repl.it which meant users could go from an idea to a fully deployed (but not super functional) website in 5 minutes.

Toward the end of my time at the company I was working on expanding the code export to support React code which required prompt engineering using GPT-4o. I was able to build a prototype but our priorities shifted so I wasn't able to complete the project.

Bento was an everboarding as a service platform allowing customers to embed a custom onboarding and everboarding experience directly in their product (actually inline using WebComponents/ShadowDOM instead of iframes) and modify it at any time without needing to rely on engineering.

When I joined I was the most experienced IC on the team so when the CTO left shortly thereafter I stepped into an engineering leadership role. I was still an IC but was then also the source of guidance for all things engineering short of people management.

One of the most impactful projects I built at Bento was the WYSIWYG capabilities which serve as the foundation of all the no-code aspects of the product. From that I was able to build the functionality to allow customers to inject their onboarding guides inline anywhere on their site, select elements which should have tooltips, and even allow non-visual features like choosing elements which should automatically complete steps in guides when clicked.

Apart from the many other features I worked on, I was deeply involved in systematically and iteratively modernizing and optimizing the code to bring it from "spit and bandaids" typical of a young startup's codebase to something much more scalable and maintainable in the long term.

I joined as part of the acquisition of Chartio and the work started to convert the general BI platform that was Chartio into what would eventually become Atlassian Analytics to bring together data from across the entire Atlassian platform as well as external sources. Following on from the last project at Chartio I was chosen to lead the Visualizations team tasked with modernizing and componentizing the dashboards and charts so they can be easily "embedded" in any Atlassian product.

Chartio (acquired by Atlassian in Feb 2021) was a modern BI platform which prioritizes ease of setup and use for both technical and non-technical users.

About a year into my tenure I was chosen to spearhead the technical design and development of an entirely new chart builder. The intent was to make the experience much faster and easier while keeping functional parity with the "legacy" chart builder while setting up a foundation upon which to expand the functionality more easily in the future. Once that project was released and winding down I then moved to lead the technical design and development of a new chart rendering library to improve the capabilities and performance of charting on the platform until the company was acquired by Atlassian.