Design-led background
I started in design and communication, then moved steadily into digital product work and software development.
About · Senior Product Engineer
I connect product thinking, interface design and software delivery.
I work on operational software where understanding the business, shaping the product and building it well cannot be treated as separate responsibilities.
Product definition
UX / UI design
Software development
AI integration
The short version
A design-led engineer for software that has to work in the real world.
My background crosses disciplines, but the objective is consistent: turn complex operations into products that are clear to use, reliable to run and realistic to evolve.
End-to-end responsibility
I carry product definition, UX/UI, architecture choices and core implementation across the same engagement.
Operational contexts
Internal platforms, order-entry systems and tailored business tools built around real daily work.
Pragmatic technology
PHP, CodeIgniter, MySQL, HTMX and JavaScript — chosen for product fit, maintainability and delivery value.
How I work
One product system, not a chain of separate handoffs.
I’m most useful where strategic clarity and hands-on execution need to reinforce each other.
Product definition
I map workflows, exceptions, business rules and priorities before deciding what should be built.
Interface systems
I make dense information and repeated operational tasks understandable without hiding necessary complexity.
Software delivery
I build core parts of the product and keep architecture, interaction logic and rollout moving coherently.
AI integration
I add assisted classification, retrieval and decision support where they improve the actual workflow.
What guides the work
Design is how a system becomes legible. Engineering is how it stays useful over time.
I care about what a product asks people to understand today, and about whether the system can still evolve tomorrow.
Workflow first. Screens only make sense once the work behind them is understood.
Clarity without distortion. Reduce friction without simplifying away business reality.
One coherent system. Product, UX and code should strengthen the same decisions.
Evidence from delivery
Responsibility grounded in real operational contexts.
These are private systems, so the case studies focus on the problem, product decisions and operational outcome.
20-person company
Shared planning and service coordination across departments.
Read case studyNationwide sales network
Tablet-based order entry shaped around field sales activity.
Read case studyMature operational software
Progressive modernisation without interrupting daily work.
Read case studyAI and emerging technology
Useful capability, not novelty bolted onto a product.
I’m interested in how AI can improve traditional software through assisted classification, guided retrieval, conversational support and faster access to structured knowledge inside the workflow itself.
The test is practical: the capability should remain precise, understandable and grounded in the product’s logic.
Project conversation
Need this level of ownership on an operational product?
Tell me how your team works today, what the software needs to improve and where the current process is getting in the way.