Internal platforms, tailored business software, order-entry systems, and operational tools built for real daily use.
About
Senior product engineering for operational software and internal platforms.
I’m a Senior Product Engineer with a design-led background and hands-on delivery experience across product strategy, interface systems, and implementation. I work on workflow-heavy software where operational reliability, clarity, and speed directly affect business outcomes.
Product thinking
Interface systems
AI-aware execution
Product definition, UX/UI, architecture choices, and core implementation carried end-to-end across the same engagement.
Work spanning focused company operations, cross-department coordination, and nationwide sales workflows.
CodeIgniter 4, PHP, MySQL, HTMX, JavaScript, analytics instrumentation, and delivery choices shaped by product fit rather than framework fashion.
I work in both Italian and English, and I’m comfortable collaborating across local and distributed product contexts.
Background
I started in design and communication, then moved steadily into digital product work and software development. That combination still shapes how I work today: I care about how systems are structured, how interfaces guide people, and how products behave once they are used repeatedly by real teams.
How I work
I’m particularly drawn to products that cannot be reduced to generic patterns: internal tools, workflow-heavy applications, tailored business systems, and software that supports operational decisions. In those contexts, I usually work across boundaries rather than inside a single silo.
A few concrete examples are available in my operational software case studies.
Product and engineering
I think about product structure, define interaction logic, shape interfaces, build core parts of the system, and keep the whole product moving in a coherent direction. I tend to be most useful where teams need both strategic clarity and hands-on execution, not one without the other.
Design perspective
I don’t see design as decoration layered on top of software. I see it as a way of making systems legible. The same applies to engineering: good implementation is not just about correctness, but about building products that stay understandable, maintainable, and evolvable over time.
Evidence from delivery contexts
- Internal operational suite for a 20-person company with shared planning and service coordination.
- Tablet-based order system supporting a nationwide distributed sales force.
- Progressive modernization of mature operational software without interrupting daily work.
How responsibility was carried
- Product definition and interaction structure.
- UX/UI execution for workflow-heavy interfaces.
- Main implementation ownership and delivery decisions.
These responsibilities are documented across the published case studies.
AI and emerging technology
I’m especially interested in how AI can improve the usefulness of traditional software. What matters to me is not novelty for its own sake, but applying new capabilities in ways that remain precise, useful, and grounded in product logic.
In practice, that can mean adding assisted classification, guided retrieval, conversational support, or faster access to structured knowledge inside the workflow itself rather than bolting on a generic chatbot.
What I’m looking for
I want to work where ambitious product work, strong engineering, and thoughtful interface design reinforce each other — in high-maturity teams building serious technology with long-term intent and clear standards.
If this is close to your context, you can get in touch here.
Role-focused conversation: LinkedIn. Project-focused conversation: email brief.