I have been working in the FOLIO community since 2020 as part of the Prokopovych team. I am now the lead developer of the Aggies team who is responsible for managing both front-end and back-end modules with possible edge module development in the future. We do a lot of sprints and I would love to see some engineering come in to play more. This is what the technical council is, in my opinion. I hope to see FOLIO environment more agnostic to the language or software stack outside of official Flower releases by design. I personally prefer specification driven development where standards are developed and specifications are written. I actively participate in the Workflow SIG and the Security group/team.

I have been contributing to the FOLIO project since 2018, advancing from a developer to a team leader. During this time, I have been involved in design and implementation of architectural solutions for critical features, actively participating in their development. In addition, I have a comprehensive understanding of the project as a whole and have ideas for its future improvement. I am confident that my participation in the Technical Council will be valuable not only because of my technical expertise but also thanks to my commitment to contributing to FOLIO’s strategic decisions and long-term growth.

I have over 18 years of experience as an Analyst and Software Engineer, starting at a consortial data center and later with Stanford University Libraries. I have developed a strong understanding of Library Management systems, workflows, and technical stacks. Trained in Agile methodologies and project management, I’ve built integrations across platforms like ILLiad, Caiasoft, credit card gateways, and university business systems. Recently, I contributed to Stanford’s migration to FOLIO, gaining hands-on experience with SysOps using Kubernetes and Helm, and becoming familiar with FOLIO's codebase. I’m eager to use my skills to help Stanford and the broader community evolve FOLIO.