I did not start my career as a software engineer.
My first professional experiences taught me something that has stayed with me: most business problems do not exist inside one tool. They exist between people, processes, information and systems.
I spent years working close to customers and day-to-day operations. That meant dealing with requests, resolving issues, keeping information accurate, following processes, coordinating work and making sure something that entered the system actually reached the other side. Those experiences gave me an appreciation for the operational details that are often invisible from the outside.
As my work moved into digital operations and real estate, the problems became more connected. A property enquiry could involve a website, a form, a CRM, a calendar, an agent, a customer, a follow-up sequence and eventually a transaction or service process. Managing those pieces individually was possible. Making them work together was much more valuable.
That is where my interest in systems grew.
I began working with CRM platforms, workflow automation, websites, forms, calendars, communication tools and integrations. Instead of simply completing the task in front of me, I started asking what happened before it, what should happen next, where information should go and what could be made automatic.
Today, that thinking influences how I approach web development and software. I am not interested in building an interface in isolation. I want to understand what the interface is connected to, what the user is trying to accomplish and what the business needs to happen behind it.
The result is a way of working that combines operational understanding with systems thinking and increasingly deeper software engineering.
