Sebastian Ben Mastrangelo

Senior Full Stack Developer — PHP/Laravel & C#/.NET

I'm a full stack developer with 10+ years of experience building and scaling web applications, primarily in PHP (Laravel, Symfony) with recent hands-on work in C#/.NET using the ABP Framework. I care about clean architecture, reliable test coverage, and shipping features that hold up in production — not just in a demo.

View my resume →

What I Do

Most of my career has centered on enterprise PHP applications: architecting RESTful APIs, leading framework upgrades (PHP 7.4 → 8.3, Laravel 8 → 11), and building automated end-to-end test suites with Playwright and Cypress. More recently I've been contributing to a migration from Laravel to C# using the ABP Framework, and building a database-driven dynamic questionnaire system using domain-driven design.

Core Stack

PHP — Laravel, Symfony
C# / .NET — ABP Framework, Entity Framework Core
Vue.js, JavaScript / TypeScript
PostgreSQL, MySQL
Docker, AWS
Playwright, Cypress (test automation)

Experience Highlights

Senior Full Stack Developer - PHP & Laravel — ComplianceHR (2023–2026)
Sr Full Stack Developer - PHP & Laravel/Pod Lead — Red Oak Technologies, vendor for Apple (2021–2023)
PHP Full Stack Developer — Apogee Design Inc. (2017–2021)
PHP Full Stack Developer — LV.NET (2015–2017)

How This Site Was Built

This site is a small, living example of how I build: a custom Laravel application, not a template or a hosted site builder. It's the same stack I use professionally, and everything below is real code you can ask me about.

Laravel + Vue, rendered on the server. The backend is Laravel 13 with Inertia v3 and Vue 3, bundled with Vite and styled with Tailwind CSS. Public pages are server-side rendered, so they load fast and search engines see full HTML, while the admin area stays a snappy client-side app.
A custom content management system. I can create, edit, and publish pages from a private admin panel using a rich-text editor (TipTap) with a raw HTML mode. Pages can be drafts or published, and any new page is served automatically under its own URL.
Drag-and-drop navigation. The menu is database-driven. I can reorder it, nest it into dropdowns, and point items at internal pages or external links without touching code. It has a responsive mobile menu.
Built-in SEO tooling. Each page has its own title, description, and keywords, with a live search-result preview and character counters in the editor. Open Graph tags and canonical URLs are generated automatically.
A contact form that doesn't rely on SMTP. Messages are sent through the Gmail API using OAuth with send-only permission. The form validates input, includes a honeypot field to catch bots, and is rate limited.
Locked-down admin access. Only admin accounts can sign in, with rate-limited login attempts and two-factor authentication and passkey support through Laravel Fortify. Admin routes are protected by middleware.
A read-only database browser. I built an admin tool for inspecting tables safely. It only accepts GET requests, runs inside read-only transactions, hides sensitive tables, and masks columns that look like secrets.
Production error alerts. Unhandled exceptions are emailed to me with the URL, stack trace, and context, de-duplicated so one bug doesn't flood my inbox. Logs are split by severity and rotated automatically.
Code quality checks. The project uses PHPUnit feature tests, static analysis with Larastan/PHPStan, and Laravel Pint for consistent code style.
Accessibility and WCAG 2.2 AA. Accessibility is integrated into the development workflow, with a focus on meeting WCAG 2.2 Level AA requirements. I use semantic HTML, accessible form labels and error messages, keyboard navigation, visible focus indicators, and appropriate ARIA attributes where needed. I also account for high-contrast mode and ensure interactive elements communicate their purpose clearly, including when links open in a new tab. Automated accessibility audits run through GitHub Actions on pull requests, and failing checks block merges until the identified issues are addressed. This makes accessibility a continuous quality gate rather than a one-time audit.
Automated deployment. Every push to main triggers a GitHub Actions workflow that deploys to the production server over SSH. Locally I develop in Docker Compose with PHP, Node, and PostgreSQL containers so my environment matches production closely.

Curious how any of it works? Send me a message and I'm happy to walk you through it.

Let's Connect