During my summer at Puberry, I accomplished two notable outcomes: developing and implementing a new scenario-based learning flow and building a comprehensive teacher-admin portal, including database tables, API calls, endpoints, and triggers to support its functionality.

The Department of Education requested our scenario-based learning flow to provide students with a new style of learning—one that introduces friction and critical thinking, rather than simply tapping through options to move forward. We were given a deadline and met it. Two other engineers and I executed the minimum viable product for the department. I designed the graphical user interface, incorporating new, crisp components and styling.

The need for a teacher-admin portal arose from our school-wide subscription plans. We required an administrator at each school to monitor their plan, seats, and classes. The new portal allows administrators to manage students and teachers, along with essential information such as joining codes and classroom assignments.

My computer science degree is about more than coding—it involves solving complex problems. As Puberry continued to develop, I personally resolved issues and found efficient solutions. We went through a significant graphical update, which required thoughtful solutions to transition from the old to the new application. Ticket management and a new development workflow were crucial to track progress. The teacher-admin portal presented one of my first major back-end challenges. I implemented a full-stack workflow, creating new content fields in our content-management system, adding database tables, developing API endpoints, running migrations, and integrating the front end. I also synced a local development environment to test the code using a Grok Tunnel to host CMS updates locally.

Challenges this summer were not solely technical. Ethical concerns arose as we ensured our work complied with guidance, protection, and security procedures. In developing the scenario-based flow, we knew we needed to create something with more friction than our quizzes because friction fosters growth. Quizzes might allow students to engage without transformation. Some content includes vulnerable topics, such as body image. We had to address these sensitively while prompting thoughtful reflection. Quizzes can feel prescriptive and mechanical—life is not. Puberry AI helped us diversify options and pathways for students. When we encourage growth through scenarios, our app becomes its most authentic version.

This summer was eye-opening. I learned more useful skills for my career than ever in the classroom. Our new chief technology officer, Eric, taught me invaluable skills in work management and technical execution. I am more confident in my role and more passionate about development. At Puberry, my view on education and creativity evolved. The scenario-based flow showed me that too much structural smoothness can obscure emotional depth. Clear outcomes can mask complexity. Balancing structure with authenticity, along with tackling numerous technical challenges, made this my most successful project yet. I believe this experience will shape my entire professional future.