I care more about useful capability than a perfect title.

I tend to look for the operating reality behind a problem. What is actually happening? Where is information getting lost? What is creating repeat work? What depends too heavily on one person remembering everything?

That mindset applies to staffing, customer service, inventory, training, reporting, documentation, technology, and almost anything else. I am interested in solutions that make the work clearer and more reliable—not complexity for its own sake.

I also value accuracy. Counts, records, schedules, financial controls, reports, and handoffs are easy to dismiss as routine details until one of them is wrong. Good operations are built on getting those details right consistently.

I began college studying Computer Science at East Carolina University before transferring to Penn State, where I shifted into Early Childhood Education. That academic path changed direction, but both sides still show up in how I think: I am interested in how systems work and in how people learn, communicate, and perform within them.

Outside school, my earlier background included student teaching, youth-development work, customer-facing retail, and home care. Those experiences are not the center of my career today, but they help explain why training, communication, patience, documentation, and developing people have remained recurring parts of the work I do well.

I have an established operating background, hands-on experience with business systems, and a genuine interest in technology. The most realistic path is not to pretend one replaces the other. It is to combine them.

Over time, I want to become useful in work where business operations, people, process, information, systems, and technology all matter. The exact title can change. The capability is what I am building.