Service Desk and IT Support
Incident triage, user support, access troubleshooting, escalation communication, and resolution documentation.
Service Desk experience · infrastructure direction
I fix what’s broken, then figure out why it broke.
I support people and systems professionally, then keep learning by building my own Windows, Microsoft 365, Linux, networking, and automation environments. The work here separates what I did, how I checked it, and what remains unproven.
IntakeInvestigateRemediateValidateDocument
What I bring
The calm of support work. The curiosity of an operator.
Service desk work shaped the habits that matter when systems fail: listen carefully, narrow the scope, communicate clearly, preserve context, and leave the next technician a useful record.
Systems Administration Practice
Active Directory, Group Policy, DNS, DHCP, Windows Server, Linux integration, virtualization, and backup operations in a personal lab.
Microsoft 365 and Entra
Personal-tenant work with users, groups, licensing, roles, sign-ins, applications, exports, and limitation-aware evidence.
PowerShell and Validation
Repeatable checks for inventory, evidence generation, links, document integrity, repository structure, and content drift.
Selected systems
Start with the work, then inspect the source.
Each route answers a different reviewer question without repeating the same portfolio pitch.
On-Premises Home Lab
A long-form systems case study covering Proxmox, pfSense, Active Directory, Windows, Linux, network segmentation, backups, four isolated restore exercises, automation, explicit limitations, and direct evidence paths.
case studyOpen the labMicrosoft 365 and Entra
Personal-tenant administration represented through exports, screenshots, manifests, and claim boundaries.
proof routeInspect evidenceRCA and automation
Troubleshooting records and validation tooling show how I move from symptom to documented result.
project routeReview methodsEvidence method
A claim is only as strong as what the artifact demonstrates.
Commands, captured output, observed behavior, reproducibility, scope, and limitations determine evidence strength. The proof index exposes those relationships directly.