I design load-bearing hardware, model vehicle physics, and turn ambiguous requirements into engineered systems that can be tested, understood, and improved.
Four projects, four different operating environments, one consistent approach: make the system visible, then make it better.
A payload-retrieval UAV developed through roughly 10 design iterations. Résumé-reported design history includes an approximately 30 lb payload target, a 15-to-9 lb vehicle-mass reduction, and about 100 calculations; the case study separates those figures from the uploaded preliminary eCalc scenario.
View case study →A deterministic planning and simulation system for a future U.S. electric-freight network—connecting human drayage, autonomous line haul, charging, energy, cost, routing, and shipment execution without pretending simulation is live infrastructure.
View case study → Open the live system ↗Our four-person ME 250 team designed a scale-model sled that had to carry at least 100 g, use no wheels, run only on torsion-spring energy, stop without human intervention, and signal completion. A morphological study narrowed 2,419,200 combinations before CAD, workshop fabrication, and subsystem integration.
View case study →
I translate a client’s goals into clear, responsive web experiences—combining positioning, visual systems, implementation, and launch support instead of treating the website as decoration.
View case study →I’m David Sura, a mechanical engineering student at UIC focused on autonomous systems, structural design, and the software that makes complex machines legible.
I chose engineering because I have always been drawn to problems that resist the first answer—puzzles, Rubik’s cubes, math, and physics—and to design as the point where an idea becomes something real. Golf keeps me patient and analytical; swimming and water polo taught endurance and teamwork; Polish cultural dance kept me connected to my heritage; and founding a boxing club in high school gave me an early lesson in organizing people, earning trust, and leading from inside the work.
The through-line is systems thinking: interfaces matter as much as parts, and the reasoning should remain inspectable.
Translate mission constraints into geometry, materials, interfaces, and manufacturable assemblies.
Design around sensors, compute, communications, power, and the realities of the physical platform.
Make assumptions explicit, preserve provenance, and test the highest-consequence decisions.
Turn complex technical work into an experience that users, clients, and collaborators can act on.
I’m interested in ambitious engineering teams working across mechanical design, testing, and manufacturing. My résumé has the fast overview; the projects show how I think.