Mechanical engineer who builds, tests, and iterates real hardware. From FEA at Hyster-Yale to custom smartwatches to solar tracking platforms.
I've been taking things apart since I was 14 (PCs, then MacBooks, then forklifts at Hyster-Yale). I'm a mechanical engineer finishing my B.S. at Santa Clara University, transferring from Portland State. What I care about is the full loop: physics, model, simulation, prototype, break it, iterate. I like problems where the answer isn't obvious and you have to go from a vague need to a piece of hardware that actually works. Looking for mechanical design, CAE, or product design roles in consumer hardware or industrial equipment.
Four projects that best show how I think, design, and ship.

Advanced my mechanical engineering work through higher-level design, controls, testing, and simulation courses while building projects that tied coursework directly to hardware and analysis.

MECOP intern on the Global Modeling & Simulation (GM&S) team at Hyster-Yale Materials Handling, Counter Balance Development Center in Fairview, Oregon. Three major projects: EAGLE (protective enclosure, 98% cost reduction), AWESOME (weld automation, 70-87% time savings), and FEA for C23/P12 adapters (nonlinear structural simulation). Mentored by Max Stein, Engineer IV.


Worked on a student rocket team supporting mechanical design work, learning how to translate concepts into hardware that could be built, tested, and improved for flight-related systems.

Built the foundation of my mechanical engineering track through transfer coursework, lab-based problem solving, and early design projects that shaped my hands-on engineering approach.
Certifications, board roles, and leadership positions that show range beyond the bench.
The operating principles I bring to every team and every problem.
I don't hand off problems. I follow them from whiteboard to finished hardware. If something breaks at 11pm before a review, I'm the one fixing it.
I start from physics, not assumptions. Whether it's a weld joint or a mounting bracket, I understand why the solution works, not just that it does.
Good enough to test beats perfect on paper. I build, break, learn, and refine quickly. More iterations mean better outcomes, always.
I've worked with manufacturing, software, and ops teams. I speak engineer and I speak business, and I know when to use which.
Deadline doesn't mean sloppy. I know which tolerances matter and which don't, and I make that call early so I'm not chasing problems at the end.
New tool? New domain? I ramp quickly. From LabVIEW to Simscape to Python scripting in Abaqus, I pick up what the job needs.
Software and hardware I use to design, simulate, build, and test.