About

The short version behind the work.

I am a University of Michigan student studying Industrial and Operations Engineering with Computer Science. The work I want to highlight most sits between physical systems, practical software, team projects, and the process of making rough ideas usable.

Origin

How I got here

My path into engineering started long before college through building things, robotics, and the steady pull of wanting to understand how complicated systems fit together. That eventually led me toward Industrial and Operations Engineering, where technical decisions are tied to constraints like time, cost, safety, people, and reliability.

I am also studying Computer Science because many of the systems I care about need better tools around them. I like work where a spreadsheet, script, interface, fixture, or physical build can make a complicated process easier to repeat and explain.

Path

Engineering started early through building, tinkering, and competitive robotics, where ideas had to survive real constraints.
Industrial and Operations Engineering fits the way I like to think: systems, tradeoffs, data, people, and execution all connected.
Computer Science gives me a practical way to build tools around those systems instead of only describing what should improve.

Now

Continuing research and engineering work with Los Alamos National Laboratory after a summer internship focused on modular panel design for hot cell workflows.
Building out University of Michigan coursework across IOE and CS into project write-ups that explain goals, constraints, and outcomes clearly.
Staying involved in technical and community organizations, including TEK, Michigan Czech Student Association, and Human Powered Submarine.

Working style

How I tend to work

I like problems where the best answer has to account for both the model and the messy real-world setup around it.
I tend to learn by building a first version, testing where it falls apart, and then tightening the system from there.
I care about documentation because good work becomes more valuable when someone else can understand and reuse it.

Portfolio role

What I want the portfolio to do

Make project pages useful to read quickly, with enough context to understand why the work mattered.
Show a balance of software, systems, manufacturing, research, and student organization work.
Keep a little personality in the writing so the site feels like a person built it, not just a template.