0%
New Britain, CT — Available now
Software engineer, BS in Computer Science, MS in progress. Everything below runs — most of it opens in this tab, and all of it ships its source.
Selected work
Designed, built and deployed on my own. Two open and run right here in your browser; the third ships its source and comes up locally with a single Docker command.
Joining a new codebase usually means days of reading before you can change anything. RepoInsight fixes that: point it at a GitHub repo and ask questions about it in plain English, generate docs, or check it for security issues. Answers cite the actual files they came from, so you can verify every one.
Fifteen help desk tickets, each opening with what the user said rather than
what's wrong — “it says connected but nothing loads.” You investigate with a
simulated Windows console (ipconfig, ping,
nslookup, tracert), then commit to a diagnosis. The
engine scores your route as well as your answer, so it can tell you when a step
was right but taken too early.
Paste a job description, add your resume, and see how well they line up. I wrote the matching engine from scratch — TF-IDF, cosine similarity and a 190-skill taxonomy — because I wanted the score to be something you could inspect rather than trust. Open the scoring panel and you can drag the weights and watch the total recompute. No language model, no backend, no upload.
Smaller builds
Projects where I wanted to get a single thing right — a schema, an interface, an algorithm. Each one runs, and the source is on GitHub.
Course projects and smaller experiments — game implementations, algorithm practice, and coursework in Java, Python and C++. Not portfolio pieces, but they're public if you want to see how I write day to day.
Background
The short version: I like problems where the hard part is the design, not the typing.
The three builds above share a habit I care about: they don't ask you to take their word for it.
RepoInsight cites the file every answer came from. CareerMatch opens up its own scoring so you can move the weights yourself. The troubleshooting lab explains the consequence of every wrong turn instead of just marking it wrong. I'd rather ship something inspectable than something that only looks confident.
I have a Bachelor's in Computer Science and I'm finishing a Master's focused on software engineering. Most of what I've built starts the same way — I run into something that should be easier than it is, and I'd rather design the thing that fixes it than work around it.
I'm comfortable across the stack — schema design and stored procedures through to the interface — and I care about the parts that don't demo well: readable code, real tests, and something the next person can pick up without me.
Contact
If you're hiring for a software engineering role, I'd like to hear about it. Email is fastest — the form goes to the same inbox.