Intake and Troubleshooting
Ticket framing, impact assessment, endpoint checks, DNS/DHCP review, escalation context, closure notes, and evidence capture.
Enterprise Service Desk / IT Support / Systems Growth
Experienced Service Desk Professional — Microsoft 365, endpoints, identity workflows, and documented infrastructure validation.
Enterprise IT Support Professional with proven service desk experience and an evidence-backed growth path toward Systems Administration and Infrastructure Operations.
Support disciplineIntake, triage, remediation, validation, and handoff notes.
Microsoft operationsMicrosoft 365, identity, endpoint, and policy documentation.
Proof-first structureEvery highlighted project points to preserved repository artifacts.
My Portfolio Standard
I present proven support experience alongside preserved lab records, sanitized documentation, diagrams, scripts, runbooks, and validation notes. Each major project identifies the objective, technical area, implementation workflow, validation method, and associated proof artifact.
Technical Focus
I pair each capability with project evidence, documentation, or a validation artifact so the portfolio remains useful for both hiring managers and technical screeners.
Ticket framing, impact assessment, endpoint checks, DNS/DHCP review, escalation context, closure notes, and evidence capture.
Microsoft 365 support exposure, identity and access workflows, Conditional Access intent, Active Directory fundamentals, endpoint policy documentation, and tenant-safe change records.
DNS, DHCP, VLAN segmentation, pfSense firewall boundaries, VPN access paths, validation checklists, and infrastructure operations documentation.
Reusable provisioning logic, dry-run review, structured logging expectations, change records, validation notes, and operational handoff checklists.
Incident summaries, remediation plans, post-incident reviews, network runbooks, and validation records written for repeatable operations.
Performance-aware static pages, source-controlled evidence, link validation, accessibility checks, metadata review, and deployment readiness.
Certification Authority
I present certification assets as reviewer-friendly context for the technical areas I document across service desk operations, infrastructure labs, Microsoft administration, Linux fundamentals, and network troubleshooting.
I use this foundation to frame hardware, operating system, mobile device, troubleshooting, documentation, and customer-support workflows.
Open badge asset
I connect this credential area to server hardware, storage, virtualization, availability, backup, and infrastructure maintenance concepts.
Open badge asset
I use this baseline for terminology, system components, databases, software concepts, security basics, and practical IT communication.
Open badge asset
I map this credential to cloud service models, identity-aware administration, governance basics, Azure service categories, and cost-awareness concepts.
Open badge asset
I use this networking signal to support routing, switching, subnetting, device access, layered troubleshooting, and operational network diagrams.
Open badge asset
I apply this foundation to shell navigation, package awareness, file permissions, services, logs, and cross-platform troubleshooting practice.
Open badge asset
I connect this training to troubleshooting structure, operating systems, networking basics, security fundamentals, and customer-facing support habits.
Open badge asset
I use this credential area for TCP/IP basics, DNS, DHCP, subnetting, wireless concepts, and support-ready connectivity checks.
Open badge asset
I align this area with least privilege, authentication concepts, policy awareness, network boundaries, and secure support workflows.
Open badge asset
I tie this credential to Windows Server roles, Active Directory context, storage concepts, administration basics, and service validation notes.
Open badge assetInteractive Home Lab
I use this preserved lab model to explain how Proxmox, pfSense, Active Directory, DNS, DHCP, VPN access, VLANs, Windows Server, Linux workloads, and IDS/IPS concepts relate in a realistic support and systems administration environment.
I use Proxmox as the virtualization layer for lab workloads, service isolation, snapshot-aware practice, and infrastructure documentation.
pfSense represents the routing, firewall, NAT, VLAN gateway, WireGuard, OpenVPN, and segmentation-control boundary.
Active Directory supports domain-service planning, OU structure, Group Policy scope, authentication context, and Windows administration practice.
DNS and DHCP provide name resolution, lease assignment, reservation review, gateway checks, and common service desk troubleshooting paths.
WireGuard and OpenVPN model controlled remote access, tunnel validation, firewall rules, and client connectivity troubleshooting.
VLANs separate management, server, client, lab, and monitoring traffic so routing and firewall policy remain reviewable.
Windows Server anchors identity, management, service validation, and endpoint support workflows.
Linux workloads support service hosting, package administration, network checks, logging practice, and cross-platform troubleshooting.
IDS/IPS concepts provide traffic visibility, alert-review context, and segmentation validation without claiming live production monitoring.
The WAN edge shows where outside connectivity reaches the firewall before controlled routing into lab segments.
Repository Governance Platform
I operate this repository as a governed DevSecOps-style engineering platform with automated CI/CD validation, evidence integrity enforcement, Lighthouse auditing, screenshot verification, SEO governance, and operational telemetry reporting.
CI validationGitHub Actions quality gate active.
Lighthouse performanceLatest proof page desktop score.
Integrity fingerprintsSHA-256 evidence hashes tracked.
Evidence entriesIndexed proof artifacts mapped to claims.
GitHub Actions automatically validates accessibility, Lighthouse thresholds, SEO metadata, screenshots, evidence integrity, links, HTML, PowerShell, and deployment readiness.
Repository artifacts are indexed, mapped, validated, and fingerprinted using SHA-256 integrity hashes to support operational traceability and documentation integrity.
Repository telemetry tracks validation coverage, Lighthouse reporting, governance metrics, evidence inventory health, and CI/CD operational status.
Featured Work
These are the highest‑value review paths — each one opens into real, source‑backed artifacts, not simulated case studies.
Preserved records for conditional access intent, identity boundaries, endpoint administration notes, and architecture review.
Sanitized incident documentation showing symptom capture, triage, remediation planning, validation, and post-incident review.
Operating Rhythm
Capture affected users, devices, service boundaries, urgency, and known-good behavior before changing anything.
Use logs, baselines, configuration state, screenshots, diagrams, and repeatable checks to isolate likely causes.
Document the planned fix, risk, expected result, validation method, and follow-up owner.
Confirm restoration, update notes, preserve artifacts, and keep the record usable for the next incident.