I care about the product and the code behind it.

Product judgment, not just implementation. I want to understand who we’re building for, what they are trying to achieve, and whether the proposed feature is the simplest way to help them.

Deep Laravel experience. PHP and Laravel are where I’m most productive. I’m comfortable moving from database design and queues to Inertia interfaces, integrations, testing, and deployment.

Curiosity below the application layer. I actively work with Linux, networking, containers, reverse proxies, CI, and provisioning. I don’t need infrastructure to be a black box to ship application code.

Ownership and pragmatism. I like taking a problem from an unclear first conversation to a maintainable result. I value boring technology where it works and new technology where it earns its place.

My side projects reflect how I work. Visuper explores nuanced coaching workflows in a Laravel product. ease.wedding turns fragmented inquiries and tasks into a focused workflow for wedding professionals. Purrver is my hands-on route into server provisioning, systemd, Caddy, databases, and deployment lifecycles.

I also build and test remote development setups on Linux infrastructure because I’m interested in the environment behind the editor—particularly now that coding agents need secure, reproducible computers of their own.

A remote-friendly product team working on a real, useful product. Laravel or a similar backend-heavy stack would be a natural match, as would work involving SaaS, internal workflows, developer tools, or infrastructure.

I’m happiest when the role leaves room to investigate, shape the solution, and improve the way the team builds—not only pick tickets from a queue.