Define
Clarify the user, problem, requirements, constraints, success criteria, and what must be proven.
I am an ASU mechanical engineering student focused on computational mechanics, CAD, digital prototyping, and product development.
Each project is presented as a case study—showing the problem, design decisions, engineering process, and final result rather than only the finished render.
A clear process keeps the work grounded in user needs, engineering constraints, and measurable improvements.
Clarify the user, problem, requirements, constraints, success criteria, and what must be proven.
Sketch alternatives, compare mechanisms, study references, and narrow concepts using trade-offs.
Build parametric CAD, assemblies, drawings, simulations, and prototypes with manufacturability in mind.
Test, document failure points, iterate, and communicate the result through diagrams, metrics, and renders.
The portfolio includes a lightweight Three.js model viewer to demonstrate assemblies directly in the browser.
Filter by discipline, then open a project to see its challenge, approach, role, outcomes, and gallery.
I am a Mechanical Engineering student at Arizona State University with a focus in Computational Mechanics. I enjoy combining CAD, digital prototyping, product design, additive manufacturing, and visual storytelling to turn ideas into clear engineering concepts.
I am currently seeking engineering internships where I can contribute to mechanical design, product development, prototyping, automotive design, manufacturing, or interdisciplinary hardware teams.
A polished render is useful, but it is not the whole story. Strong engineering work explains why a concept was chosen, how constraints shaped it, what failed during development, and what changed after testing.
This portfolio is structured around that process. Every case study can include sketches, requirements, CAD iterations, simulations, prototypes, test evidence, manufacturing considerations, and measurable outcomes.
Keep only the tools and capabilities you can confidently discuss in an interview. Depth and evidence matter more than a long software list.
Open to engineering internships, collaborative projects, design challenges, and conversations about product development.