Turned ambition into a technical launchpad.
Year Up was the pivotal bridge into technology: six months of technical and professional development followed by a six-month internship at Palo Alto Networks.
My journey started with rooms, devices, identity, and employee support. Today I build production-minded AI agents shaped by the constraints of real IT operations.
My path started with the infrastructure people rely on every day—rooms, devices, identity, and support—and evolved into building AI systems that make those operations faster, clearer, and more repeatable.
Year Up was the pivotal bridge into technology: six months of technical and professional development followed by a six-month internship at Palo Alto Networks.
During my six-month Year Up internship at Palo Alto Networks as an Audio Visual/IT Specialist, I supported enterprise collaboration at scale, strengthened incident and asset workflows, and translated break-fix experience into documentation global teams could reuse.
In Desk Side Support, I managed the moments where hardware, software, mobile devices, networking, and meeting technology meet the employee experience—across in-person and omnichannel support.
As an IT Administrator, I combine frontline service delivery, onboarding, access, device compliance, and AV support with production-minded agent design—building tools such as AirGuidance and ConFlu around real operational evidence.
Manual research and drafting avoided across roughly 290 escalated CoPilot cases.
Estimated weekly documentation time saved through scheduled, governed runbook drafting.
Mac inventory records processed for fleet analysis.
Mac and Windows devices surfaced in a verified site dry run.
Four systems, each shaped around a real operational constraint. Open a profile for the design story—or run the workflow demo to see the sequence.
The common thread isn’t a model. It’s a way of building systems that can explain what they know, respect the boundary of what they can do, and get better from real work.
Solved tickets, internal runbooks, vendor knowledge, and system-of-record data—not generic intuition.
Separate high-confidence automation from low-confidence guidance, and keep a human at consequential gates.
Failures become sharper rules, stronger skills, better retrieval, and safer operating boundaries.