Twelve years turning messy, technical problems into working systems — parsing escalation reports into resolutions at IBM, translating damage assessments into approved claims on rooftops. Same skill, two trades: read the situation, build the structure that resolves it.
I've spent most of the last decade building enterprise software in PHP, with real depth in TypeScript/React and six years at IBM Cloud (SoftLayer) working on production infrastructure and internal tooling.
The project I'm proudest of: I led development of an internal AI tool at IBM — built with Python, Hugging Face, and watsonx — that read client escalation text and surfaced likely resolutions, cutting the time support teams spent digging for answers. It's the same instinct I bring to every system: find the structure hiding in a mess of information, and build something that acts on it reliably.
Currently sharpening TypeScript, React, and cloud fluency to return to full-time engineering, while running a residential roofing/insurance-restoration book on the side — a trade that, as it turns out, runs on the exact same instinct: read the situation, document it precisely, get it approved.
| Item | Rating | Notes |
|---|---|---|
| PHP / Laravel | Load-bearing | 12 years — heaviest lane, MVC, Eloquent, legacy modernization |
| TypeScript / React | Load-bearing | Design systems, hooks, component architecture |
| Cloud Infrastructure | Load-bearing | Docker, Kubernetes, Linux, Nginx — 6 yrs at IBM Cloud |
| Node.js | Structural | REST API design, auth, middleware |
| SQL — MySQL, Oracle | Structural | Indexing, query optimization, schema design |
| Python + AI/LLM Integration | Structural | Hugging Face, watsonx, RAG — production AI tooling at IBM |
| Go | Supporting | Backend services at IBM and Hyrox |
A claims-tracking system built on the actual roofing/insurance-restoration workflow — lead intake through claim approval. The system-of-record half of a two-part project.
An AI layer that reads claim and adjuster notes and surfaces likely next actions — deliberately mirroring the escalation-parsing tool I built at IBM, applied to a domain I know from the ground up.
Small, focused reference builds — a Laravel API, a React/TS component set, an infra playground with Docker/Kubernetes/Nginx configs, and a working systems-design prompt built end-to-end rather than just whiteboarded.
| Rev. | Role | Org | Period |
|---|---|---|---|
| R7 | Insurance Restoration Sales Specialist | Priority Roofing | 2025 – Present |
| R6 | Software Architect | Hyrox | Jan – Apr 2025 |
| R5 | Software Engineer II | IBM SoftLayer | 2018 – 2024 |
| R4 | Full-Stack Engineer | Securus Technologies | 2017 – 2018 |
| R3 | Ecommerce Software Developer | PFSWeb | 2017 |
| R2 | Full-Stack Engineer | RealPage | 2016 – 2017 |
| R1 | Full-Stack Developer | Oakwood Software | 2014 – 2016 |