Rooms that work when the meeting starts
I install, configure and troubleshoot AV and IT systems — Crestron and Extron control, Zoom and Teams rooms, networks, imaging and Active Directory.
At SUNY Schenectady that meant 80 large events a year and a thousand tickets, on a campus of five thousand people. At Domino's it meant AV, sensors and thin clients across restaurants, where downtime is measured in orders lost.
Also: a 10% cut in A/V spend at SUNY, by specifying equipment that did the job instead of equipment that looked like it would.
A production environment I run myself
118 containers across two machines, at home, in daily use by my family. Single sign-on, reverse proxy and TLS, centralised logging, intrusion detection, offsite backup, and a private model gateway.
It is not a lab that sits idle. Things break in it and I fix them, which is the part a certificate cannot show: a database that filled a disk and took a photo service down with it, a nightly backup that had been copying a NAS onto the wrong drive for a week, a service that restarted a thousand times because it mistook its own slowness for somebody else's.
Single sign-on
One account across every application in the house, with per-person access and sessions that end when access is removed.
Observability
Metrics, logs and uptime checks on a second machine, so the box that is down is not the box being asked whether it is down.
Applications
A phone assistant, a photo library with automatic tagging, a garden catalogue, and a telephone line that answers and plays a recording.
74 rooms and a report to show for it
Top 7% on TryHackMe — 74 completed rooms across offensive and defensive tracks, from the Cyber Kill Chain and the Pyramid of Pain through to digital forensics and SOC operations.
It is the deliberate half of the same habit as the homelab: break something in a place where breaking it is the point, then write down how.
Offensive: SQL injection,
command injection, file inclusion, SSRF, XSS, IDOR,
authentication bypass, subdomain enumeration, Metasploit, Burp
Suite, Linux and Windows privilege escalation.
Defensive: SOC operations, digital forensics, threat
intelligence, the Cyber Kill Chain, the Unified Kill Chain, the
Pyramid of Pain, the Diamond Model.
Foundations: networking to the packet, the OSI model, DNS, HTTP,
Linux and Windows internals, PowerShell and Python for testers.
Coursework at Saint Rose included a full ethical-hacking report on the OverTheWire Bandit wargame — scope, intelligence gathering, threat model, vulnerability analysis, exploitation, post-exploitation and findings, written the way an engagement is actually documented.
DJ and live sound
I DJ. Which is the same job as the rest of this page, with an audience watching.
Signal flow, gain staging, a room's acoustics, and knowing what to do in the four seconds after something cuts out — that is AV work, and doing it live is the version with no second take. It is why I am comfortable in a control booth during an event rather than only before one.
Equipment I work with: Crestron and Extron control and switching, Zoom and Teams room systems, DSP and mixing, projection and displays, cable infrastructure and the patching that keeps it serviceable.
I also stream my own sets from a server I run — Traktor into OBS, RTMP into Owncast on the LAN, HLS back out through the same reverse proxy as everything else here.
Nobody taught me any of this
Every system on this page I built by reading, trying it, breaking it and fixing it. No bootcamp, no team to fall back on, no one to hand it to when it got hard.
That is the part worth hiring. Certificates say I passed an exam. What I actually do is take a scope I have not seen before and keep going until it works — then write down what went wrong so the next person does not lose the same afternoon.
I have ADHD. It changed how I learn, not how much: I go all the way into a problem and I do not come out until it is solved. Seventy-four rooms, a hundred and eighteen containers and a fault chased through three layers are all the same trait doing the same thing. Most employers treat it as a risk. It is the reason any of this exists.
None of this was knowledge I started with. I had not written PHP, I had not designed a schema, and I had never terminated TLS or read a reverse proxy config. I learned it the slow way, on a live system, with my own family using it.
And I use AI heavily — I would rather say so than have you wonder. It became available to me academically in my last semester, and it is how these pages get written as fast as they do. By hand I would have run out of gas long before this much existed. That is the honest trade: one person, a day job, and a system the family actually depends on.
What it does not do is the deciding or the finding. It is confidently wrong often enough that taking its word is how you ship a fault, and the failure I watch for hardest is code that only works because the tool made it work — a thing that passes because whatever wrote it also wrote what it was checked against. So I do not verify the tool with the tool. I research it out, read the forums, ask colleagues and friends what they make of an idea, and bring my own education and experience to it before I keep anything.
Prompting and pasting does not get you here. Somebody who had only done that would have no faults to write up, because they would never have found them. Every part of this site I have troubleshot myself, as deeply as I could. Five faults are written up in the engineering notes — the symptom, what it first looked like, and the cause two or three layers down — including the ones where I was wrong first.
Why any of this transfers
A company does not need someone who has run containers. It needs someone who has had to decide who gets in, what happens when a certificate expires at 2am, and where the second copy lives. I have had to decide all of it, because there was nobody else to ask.
The numbers below were counted on the running systems, not estimated. They change; the shape does not.
Identity — one account, not thirty
Every private service sits behind a single OIDC issuer I run: Immich, Jellyfin, Kavita, Audiobookshelf, two wikis, the recipe library and two phone apps I wrote. One account per person, one place to revoke it, and no service holding its own password list.
Access — two ports for the whole estate
Nothing is published on a port of its own. A reverse proxy terminates TLS for every hostname, renews all 34 certificates without being asked, and forwards to services that are not reachable from outside at all. Remote shell rides on 443 alongside the web traffic, so port 22 is closed to the internet.
Language models, run in-house
The assistants across these sites answer from models running on my own hardware, reached through a single gateway that holds the credentials and routes by task, so an application never holds a key and the model behind it can be swapped without touching the application. Speech synthesis runs on the low-power machine; the GPU is reserved for what needs it.
Change control and recovery
Source lives in a Git service I host, and the machines are described in compose files rather than assembled by hand — so a rebuild is a file, not a memory. When something is patched into a running container it is written back into the build context in the same sitting, because code that exists only in a running container is not deployed, it is borrowed, and the bill arrives at the next rebuild.
Where I have done it
Lead AV & IT Technician — Domino's Inc
- Installed and configured AV systems, temperature sensors and thin clients across restaurant sites.
- Troubleshot AV and network faults on franchise-specific equipment, keeping stores trading.
- Preventative maintenance and cable management standards, so the next fault was quicker to find.
Senior IT / Lead AV Technician — SUNY Schenectady
- Led the team through 1,000+ support requests a year in Remedyforce, beating SLA by 15%.
- Ran Crestron and Extron systems for 80+ large virtual events a year on Zoom and Teams.
- Built user onboarding with Active Directory and imaging, and improved network efficiency for 5,000+ users.
- Cut A/V spend 10% while improving production quality.
Crew & Drive-Thru — Burger King
- Reached the location's highest guest-satisfaction scores within a year, measured by GuestTrack — the company's own survey programme, answered by customers rather than by me.
- Knew the regulars well enough to have the order started by the sound of the car. Suggestive selling worked because it was a correct guess rather than a script, and it is why the upsell was usually accepted.
- Twenty cents on a cup against a customer who comes back: I gave away the cup. Arguing wins the transaction and loses the account, and at a single location the account is worth more. It is the same call support turns on — the cheap reversible fix now, rather than being right about the small item.
- No complaint that outlived the window: anything wrong was put right at the point it was raised, and those customers returned. Accuracy checked before handover, because the expensive failure is the one found in the car park.
Qualifications
Digital Forensics and Cybersecurity — Cyber
Operations, MS · University at Albany
(in progress)
BS Cyber Security · The College of Saint Rose
AS Computer Information Technology · Northwest
Florida State College
CompTIA Security+ and A+, both current to 2027. Cloud+ expected 2026. Six further college certificates and two TryHackMe paths.
Let's talk
Open to AV, IT and security work — on site in the Capital Region, or remote. The resume is a page; this site is the evidence behind it, and everything on it I built myself.
One thing has not changed across any of it: I make it right with the customer, whatever it takes. A room that fails four minutes before a meeting and an order that is wrong at the window are the same problem — somebody is waiting, and being right about the policy is worth less than fixing it.