Tufts University
University IT, school support, identity, portal, and campus knowledge-base workflows.
Resume note
Top school entry for IT Support and Education Support experience.
Resume / Work Log
School IT, logistics, engineering software, equipment operations, websites, and automation.
School support list
Tufts University and Cornell University lead the list, followed by the broader school support set. Each entry includes the institution symbol, support context, and resume-ready work language.
University IT, school support, identity, portal, and campus knowledge-base workflows.
Resume note
Top school entry for IT Support and Education Support experience.
Ivy League support context for account access, service-desk routing, and campus application help.
Resume note
Top school entry for IT Support and Education Support experience.

Service desk, account access, Duo, and campus knowledge base support.
Resume note
Identity support, portal routing, ticket documentation.

Student and staff service-desk queue with login and portal troubleshooting.
Resume note
Account recovery, device guidance, remote triage.
Campus support workflows for sign-in, ticket intake, and escalation notes.
Resume note
User verification, access issues, service routing.

PacificNet, locksmith, verification, and login-support references.
Resume note
Campus account checks, access verification, KB handoff.
Technical college support queue for portal, device, and classroom access issues.
Resume note
Login troubleshooting, ticket hygiene, escalation detail.

School support queue with account, campus-service, and remote help context.
Resume note
Support intake, identity context, knowledge-base lookup.
School help-desk support for login, application, and campus-service issues.
Resume note
Ticket detail, access triage, escalation readiness.

Campus network and login troubleshooting with on-campus connection references.
Resume note
Network access, account recovery, knowledge-base guidance.

College support queue for student, faculty, and staff access requests.
Resume note
Authentication support, service routing, ticket notes.

University service desk flows for account, Duo, and campus-application support.
Resume note
Identity checks, application access, concise documentation.

College help-desk support for login, app, and device troubleshooting.
Resume note
Remote triage, user guidance, escalation detail.

Multi-campus support context for accounts, portals, and student service access.
Resume note
Account routing, queue context, portal troubleshooting.
University support references for access, school services, and ticket handling.
Resume note
Login triage, support documentation, escalation paths.

Island-campus support queue for accounts, applications, and user requests.
Resume note
Identity routing, app access, clean ticket handoff.

Health-science university support context for identity and campus services.
Resume note
Secure access, user verification, service routing.

Technical college support queue for portal, classroom, and account issues.
Resume note
Login support, device context, clear ticket summaries.
Operations capabilities
Traveled the country and performed logistics operations across 40+ states, parts of Canada, and Mexico.
Operations capability
Routing, dispatch context, service queues, field handoff, and practical work tracking.
Operations capability
Technical tools, dashboards, documentation systems, support workflows, and software-backed operations.
Operations capability
Device setup, equipment tracking, service readiness, maintenance context, and operator notes.
Operations capability
Operations support for heavy equipment environments, field safety context, telemetry, and job-site handoff.
Selected work
Completed and reusable SpaceStatic work, summarized by problem, work performed, tools, result, and the related service.
A simple public site needed to explain the offer, collect payment, and route the buyer to the right follow-up without extra scheduling steps.
Built the service page, Stripe checkout path, thank-you handoff, metadata, and supporting shop entry so the purchase had one clear flow.
The offer became a public, buyable service page with receipt-backed follow-up instead of a loose email thread.
A PC was unstable after updates and needed a repair path before deciding whether a reinstall or replacement was necessary.
Checked update state, system corruption indicators, startup behavior, device context, and ticket notes before narrowing the repair path.
The issue moved from vague instability to a documented repair path with clear next steps if the same symptoms returned.
A personal agent environment needed a lightweight purchase option, a domain request path, and a practical delivery expectation.
Created the agent-home product, checkout intake, visual previews, and refresh option for small post-delivery changes.
The agent home became a repeatable build offer with a simple refresh lane instead of a one-off custom quote every time.
A public X account needed relationship context without letting API reads grow past the paid scope.
Added estimate-first checkout, saved report reopening, CSV export, usage reservation, and custom-feed handoff for large accounts.
The scan path shows what will be read, blocks undersized checkouts, and keeps large accounts in a scoped manual lane.
The catalog needed more than one-off downloads; each pack needed files, metadata, preview art, ZIP delivery, and checkout verification.
Built the generation scripts, catalog metadata, downloadable ZIPs, product pages, social cards, and Stripe session checks.
The catalog can publish practical form packs with consistent pages, files, and delivery rules instead of hand-built listings.
A field setup needed reliable internet context, referral routing, and a way to track whether satellite connectivity was healthy.
Connected the Starlink surface to the IT support page, added dashboard routing, and kept setup notes tied to support intake.
Connectivity work has a clearer support route and a dashboard path for checking signal and project health.
Next work log entry
New entries should stay specific: what broke, what changed, what tools were used, what improved, and which service someone should use for a similar request.
Open support ticket