Diagnosis of mechanical, electrical, and thermal issues across SLS and SLA 3D printer product lines. Designed and implemented fixes for issues discovered. Gained much experience in 3D printing, design for 3D printing, and electro-mechanical problem solving. Exposed to the challenges of remote/overseas manufacturing.

Design and drafting of an electromechanical test rig to be used under vacuum. The test rig involved mounting and coordinating six independent motion systems to direct a collimated light beam in 3D space with two mirrors.

• Development and oversight of machining and inspection process improvements within the constraints of strict GD&T requirements for several jet engine part families including the F119 and the F135• Development of data collection and analysis software systems with the goal of first pass yield improvement, aggregate rework cost reduction, and facilitation of a better process-change>result feedback loop for manufacturing engineers making production decisionsTakeaways - Jet engine production is a monumentally difficult task that demands excellence. Every last part and subsystem that leaves every Pratt & Whitney facility including the hundreds of external component and subsystem suppliers must meet or exceed that bar of excellence. The difficulty of executing on and coordinating this task cannot be understated. Every single missed opportunity to vertically integrate production and design systems will result in lost efficiency somewhere in the chain. Currently, given a production system portfolio spanning several decades of electronic and software technology, the task of vertically integrating all of these systems to meet a larger vision of complete system unification borders on impossible without creating and maintaining complex production software internally.But...In return for the monumental difficulty and cost incurred, the result is pure real-world magic

Undertaken my senior year in parallel with the ASME Robotic Design Competition• Led a team to design and build a UAV tasked with delivering a cubic payload to a designated drop zone upon UAV deployment on ground return of the launch vehicle• Led a team to design and build an electromechanical system to retain and then deploy the UAV payload on ground return, as well as a grid-fin based altitude control systemTakeaways - This is the project that made me believe nearly no design decision in engineering is trivial, and that every one of those decisions is a compromise somewhere. As a team of college students with minimal faculty oversight, we were tasked with designing and constructing a rocket that must reach an altitude of one mile in a controlled manner, return safely to the ground in the correct number of pieces, and do this while carrying a payload that is expected to survive the up to 17 Gs encountered during flight, be deployed, fly around, and deliver a subsequent payload. And to boot we were entirely donation funded and had to campaign for that in parallel. There's too much detail to go into, but I am proud that we were even somewhat successful at doing all of this. We made it to Alabama, our final rocket launched, and it returned successfully to the ground in the correct number of pieces.This project also taught me what it meant to put everything I have into something. From subscale failures, to a full blown full-scale recovery failure meaning complete destruction of our rocket necessitating the construction and successful flight testing of a second rocket in under two weeks to remain in the competition, I had never before gotten so little sleep over the course of two months and been happy to do it.

Undertaken my senior year in parallel with the NASA SLI competition• Led a team to design and build an electromechanical system to navigate a field, collect balls from the tops of poles in that field, and deposit them within a designated zone on the field• Aided the control systems team in design, construction, and programmingTakeaways - This year was a dramatic improvement over the last, but that simply meant I was exposed to a new range of deficiencies in my leadership and technical knowledge as certain core competencies were met by the team. Like the NASA SLI competition, there is too much detail to go into, but this year we made it to the competition and scored points. In hindsight I very evidently set my expectations for the capabilities of the robot too high, so at the time the whole ordeal still felt like somewhat of a failure on my part as team lead. But again in hindsight, I am very proud of what the team was able to accomplish given that just like rocket team, we had minimal faculty oversight and were entirely donation funded. This was another truly essential part of my college experience.

Undertaken my junior yearOne Big Takeaway - I tasked myself with reviving an ASME design competition team that hadn't been active at UMass in many years. This project was holistically a mess and it was my fault as team lead. I failed to set deadlines internally. I failed to effectively use the team's collective time and capability. I failed to grasp the difficulty of designing and following through on a competent control system at the lower electrical component level we intended to use, all before it was too late. And above all, I failed to be a team player.This was an essential and necessary part of my college experience. It broke me. But these failures and learnings are the foundation for how I approach problems and team work now.

Summer after my sophomore year• Wrote, customized, and tested CoDeSys control applications for custom drilling rig systems• Learned about and implemented mission critical industrial control systems• Autonomously created collection and visual analysis tools for drilling rig data in shell, c++, and Java• Functionality of the above tools rivaled and expanded upon the functionality of Schramm's competitors

Summer after my freshman year• Worked with a team of interns to rebuild a web service in Typescript instead of Javascript• Learned how to use Git• Wrote countless integration tests

Undertaken my junior and senior year of high school• Wrote six apps in total, 3 for iOS in Objective-C and 3 for Android in Java• Learned and used AWS for the backend of the last app I developed, FSE the Free Stuff Exchange• Create an S Corp LLC to release these apps under and generated ~$750 in revenue