Building the future of the Confidential Computing platform at 1Password, along with other unannounced projects.

Expanding 1Password's current offering into uncharted territories. Building confidential computing infrastructure with Rust. Read about it here 🚀 https://blog.1password.com/confidential-computing/

Led the organizational effort to outline the processes our team would follow to select and prioritize our product road map. Leveraging my previous experience in product discovery and my interest in cross team collaboration, I outline a process that allowed us to pull in data from many of our customer facing teams to prioritize the features that would make the most impact to the day-to-day workflows of the administrators of our business accounts. This process took into consideration a healthy amount of tech debt prioritization, flushing out the feature's we'd already released, and expanding our feature offering. The process of selecting this roadmap struck the balance of being data driven and diplomatic. Since our team was large enough to take on multiple projects at once, a ranked choice voting system was implemented that allowed each engineer to select the projects they'd like to contribute to the most. This voting system encouraged individuals to step outside of their comfort zone if they felt like learning something new, and ensured those individuals were paired with an experienced engineer to facilitate an environment of growth. Frontend engineers became backend engineers, backend engineers became frontend engineers; great software was built.

Built prototypes that explored how we could expand 1Password's current offering. While many internal prototypes went through a process that followed the product discovery framework, one big feature eventually hit all of our users: Item Sharing. Implementing E2EE sharing with an unauthenticated party required a tightly integrated cross functional effort between security, engineering, and UX teams to ensure the security didn't compromise the user experience and vice versa. What was eventually released was a final product we were all proud of. We went on to extend the feature over the coming months. We built administrator dashboards that allow our business users to control the behavior of the feature for their teams, document sharing support, among other details; like support for dark mode. This was 1Password's first service that hosted its own frontend, which introduced many new challenges. In addition to those challenges, I led the effort to introduce the first significant use of WebAssembly within our web clients: the item you receive in a share link is entirely powered by WebAssembly. This was the first big step forward in the 1Password's eventual goal of sharing business logic with our client apps by leveraging our client's Rust library, compiled to WebAssembly, for use in our web client. Achieving this was no easy task to do so securely. Once the feature shipped, I gave internal tech talks as well as authoring internal blog posts and documentation, all in an effort to increase the adoption of WebAssembly across our web organization. These resources have become the go-to place for internal teams to turn to when they begin integrating the use WebAssembly in their roadmaps.