I fix computers at CCSU during the day and build software the rest of the time. Finishing my MS in Computer Science this September. Most of the projects below you can just open and try, nothing to install.
All three of these are mine start to finish. Two run right here in the browser with nothing to install. RepoInsight needs Docker, but it comes up with one command.
Every time I picked up a new repo I lost two or three days just reading before I could safely change anything. So I built this. Point it at a GitHub repo, ask questions in plain English, generate docs, run a security pass. Every answer comes back with the file it pulled from, so you are not just taking its word for it.
I work a help desk, so I wrote the fifteen tickets the way they actually come in:
what the user said, not what is wrong. "It says connected but nothing loads." You
dig around with a fake Windows console (ipconfig, ping,
nslookup) and then commit to a diagnosis. It grades how you got there,
not just the answer. The DNS one catches almost everybody.
Paste in a job description, drop in your resume, see where you actually line up. I wrote the matching engine myself (TF-IDF, cosine similarity, a 190-skill taxonomy) because every other tool I tried hands you a number and expects you to believe it. Open the scoring panel and drag the weights around. Nothing gets uploaded, it all runs in the tab.
Older projects where I was mostly trying to get one thing right.
This started life as a SQL Server database I designed for a class. Tables, relationships, stored procedures, the whole thing. I liked the schema enough that I built a real front end on top of it, then swapped the data layer for IndexedDB so it runs in a browser instead of needing a server.
Class projects and small experiments. Games, algorithm practice, coursework in Java, Python and C++. None of it is polished, but it is all public if you want to see how I write when nobody is looking.
Most of my debugging instincts came from the help desk job, not from a classroom.
Professional
Jan 2025 — Present
Hardware, software, networking, account lockouts. Faculty, staff and students, in person and over remote sessions. I take tickets in Ivanti from the first report through to closing them out. I also image and maintain the Mac and Windows lab machines with Jamf and Azure. When something keeps coming back I write up what actually caused it, so we stop reopening the same ticket every semester.
Jan 2024 — Jan 2025
Met tight unload deadlines and trained new hires on the process.
Oct 2020 — Apr 2023
Processed high volumes of mail against dispatch deadlines.
Education
Expected Sep 2026
GPA 3.83
2022
GPA 3.82
2020
There is one thing all three of those have in common. None of them ask you to just trust the output.
RepoInsight gives you the file it pulled the answer out of. CareerMatch lets you open the scoring and move the weights yourself. The troubleshooting lab tells you what a wrong step would have cost you rather than just marking it red. I have used enough tools that were confidently wrong to want the opposite.
BS in Computer Science from SNHU, and I am about a semester out from finishing my MS there. Day job is the help desk at CCSU. That is where the troubleshooting lab came from, honestly. I had explained the same three diagnostic routes to people something like forty times and figured I would rather build the thing that teaches it.
I am comfortable most of the way across the stack, from schema design and stored procedures up to the interface. The parts I actually care about are the ones that do not demo well: code someone else can read, tests that catch real things, and leaving a project where I am not the only one who can touch it.
If you are hiring for a software engineering role I would like to hear about it. Email is quickest. The form goes to the same inbox either way.
