Serving as project lead during this capstone was a defining experience in my growth as an engineer. Beyond the technical complexity of designing a high-throughput apple-sorting system, I learned how much leadership relies on clarity, coordination, and keeping a team aligned when things don’t go according to plan.

One of the most important lessons I took away was the value of iteration, not only in the design process but also in how we functioned as a team. Setting the direction meant more than proposing solutions. It involved listening carefully, balancing competing ideas, and knowing when to pivot. Our design encountered real obstacles, from component failures to shifting timelines, and I came to understand that steady leadership often means maintaining focus and calm when uncertainty sets in.

This experience also reshaped how I view the role of the engineer. Technical ability is essential, but it must be paired with a strong sense of responsibility to the people and systems we serve. I felt this most clearly in discussions around usability and safety, where design trade-offs had real consequences for the end users of our system.

Throughout the project, I saw how I naturally gravitate toward organizing complexity and making decisive calls under pressure. At the same time, I recognized the need to develop more patience, especially during the early stages of problem-solving when ideas are still taking shape. Going forward, I plan to give more space for ambiguity and resist the urge to jump to quick conclusions. This experience challenged my thinking, strengthened my confidence, and gave me a clearer sense of how I want to approach my work as both an engineer and a leader.