Full-stack engineer with a security-first posture. React on the front, PHP and .NET on the back, Python where the data lives, WordPress where the clients want it. Every system designed assuming someone will try to break it.
Code is read more than it's written. Systems are operated more than they're designed. The best engineers I've worked with don't write clever code — they write clear code, and clarity scales.
My approach: assume hostile inputs, design for failure modes, optimize for the next engineer to read this, ship under real constraints instead of waiting for perfect ones. Security isn't a feature bolted on at the end — it's the posture you start from.
I'd rather have a boring system that runs at 3am than a beautiful one that doesn't.
Honest tiering. No progress bars. Languages and frameworks I actually ship with — daily drivers, active tools, things in rotation.
What I open VS Code to first.
Production React, vanilla JS, Node-side scripting. The default for anything interactive.
Built KARE Rx Card with thousands of dynamic rows. Component-driven, hooks-first.
ML pipelines, data preprocessing, KARE internal tooling. pandas, scikit-learn, NumPy.
Computer Coach certified. Modern CSS, responsive systems, animation, grid mastery.
Five+ production client sites. Theme Builder, custom CSS, ACF, performance tuning.
Branch-per-feature, conventional commits, code review hygiene, rollback discipline.
Used in production. Reach for them often.
Built KARE PharmTech end-to-end. AWS-deployed, dynamic content, MySQL-backed.
Schema design, query optimization, transaction handling. Oracle SQL via MSCS.
Rapid responsive scaffolding. Production grid systems for KARE corporate site.
PHP deployments, static hosting, basic infrastructure ops. Production exposure.
Wireframes, prototypes, design systems. Used for KARE UX work + portfolio design.
JAMstack deploys, CI/CD, KARE Pillbox launch. Preview branches, redirects, env vars.
Competent. Pulled in when needed.
OOP foundation from TCC + FAU coursework. Backend reasoning, algorithms.
KARE internal apps — security-hardened SharePoint alternative for sensitive data.
Hosting operations, MySQL via phpMyAdmin, .htaccess, file management. AC4S ops.
The corporate face of an 11-brand generative AI healthcare ecosystem. Owned end-to-end.
KARE PharmTech is the parent brand of an ecosystem spanning Clinicals, Digital Health, GPO, HUB, Lifestyle, Pillbox, PMS, Provider Strategies, Rx Card, Rx Portal, and Specialty. The corporate site needed to communicate that ecosystem clearly without flattening any individual brand, feel premium and AI-forward, and serve as the public anchor of investor and client conversations.
Each is real, public, and used in production. Click through to see them live.
Discount card platform rendering thousands of pharmaceutical pricing rows as a dynamically styled web application. Led the React.js build end-to-end.
Adherence-focused pharmaceutical product launch site. Co-developed with one other engineer for fast-turnaround marketing launch. Netlify-deployed.
.NET-based internal applications built as a security-hardened alternative to SharePoint for sensitive pharma data. Compliance-aware architecture from day one.
Executive search platform with three-track service architecture (clients / candidates / students), Calendly integration, Sherpa LMS setup, Activity Journal blog.
Multi-event healthcare-tech conference site. Speaker management, Eventbrite integration, sponsorship tier system, Tampa Tank pitch competition section.
501(c)(3) pediatric cancer research nonprofit site. Stripe donation flow, gala marketing, board management, embedded press coverage.
Every form, every URL parameter, every API response is a potential attack surface. I validate at the edge, sanitize before storage, and never trust client-side enforcement alone. The security mindset isn't paranoia — it's just respect for what users (and attackers) actually do.
What happens when the database is down? When the third-party API rate-limits us? When the file upload is 10x bigger than expected? Production code has to gracefully degrade, surface errors clearly, and never silently lose user data. Happy paths are the easy half.
The next engineer reading this code might be me in six months, or someone else with no context. Clear naming, explicit logic over clever tricks, comments where the "why" isn't obvious. Clever code feels great to write. Clear code is the only kind that scales.
Hosting limitations, client deadlines, stakeholder revisions — real engineering happens inside boxes you didn't draw. The skill isn't waiting for the perfect environment; it's making the constraints work. AC4S taught me this. KARE proved it.
Graduate work at Florida Atlantic University. The depth behind the breadth.
Relational algebra, transaction systems, concurrency control, deadlock analysis, execution plans, indexing strategy. Hands-on labs running Oracle SQL via SSH into bastion hosts, simulating concurrency, analyzing execution paths with DBMS_XPLAN.
Graph theory, centrality analysis, social network analysis, large-scale graph processing. Built a Twitch social network analysis project using PySpark + NetworkX + Louvain community detection to map influence structures.
Implemented linear regression, logistic regression, and Gibbs sampling from scratch — not from abstraction libraries. The point: understand the underlying math, then earn the right to use the shortcuts.
