THANK YOU FOR SUBSCRIBING
A featured contribution from Leadership Perspectives: a curated forum reserved for leaders nominated by our subscribers and vetted by the Construction Tech Review Advisory Board.

Woolworths Group
Matt Hosking, Chief Technology Officer
Building Retail Technology Around Scale


Matt Hosking
Keeping Growth From Outrunning Technology
Retail technology leaders often face a familiar problem.Customer needs can be increasing at a rate that exceeds the system capability to support those needs. The emergence of new channels and greater transaction volume along with new customer expectations create pressure on the IT department to increase capacity without causing instability.
These pressures are precisely where Hosking’s efforts have centered. In his career he has worked on the integration and scale of marketplace technologies among various brands of customers in Woolworths retail business.
But the scope of the problem is often far more than just infrastructure. Marketplaces add further layers of complexity such as product catalogs, seller communities, customer experience, and logistics. Decisions about platform technology can affect thousands of daily interactions with customers.
There have been indications in public hiring information and conversations about technology leadership that Hosking’s department continues to focus on scalability of the platform and the use of current engineering methods in the cloud. This isn’t just about supporting growth, but building an architecture for future growth.
Executive technology roles can sometimes become disconnected from implementation. Strategic decisions are made at leadership level while technical realities remain confined to development teams.
Hosking’s style of leadership seems to be a little different. His professional background describes Hosking as being a hands-on CTO, and colleagues also mention that he is actively involved in problem-solving and discussions related to software development and architecture. That proximity matters in retail environments where technology priorities can shift quickly. Teams must respond to changing customer behavior, marketplace requirements and commercial objectives while maintaining platform reliability.
Remaining engaged with development practices gives technology leaders a clearer understanding of delivery constraints. It also creates stronger alignment between technical direction and execution. Hosking's public commentary around modernization efforts and engineering practices reflects an interest in improving how technology teams work rather than focusing solely on the systems they produce.
The result is a leadership model built around technical credibility. Decisions about architecture, security and platform evolution are informed by direct familiarity with the engineering environment rather than abstract governance processes.
Balancing Marketplace Agility With Enterprise Expectations
Technology organizations inside major retailers often operate between two competing forces. One demands speed. The other demands consistency.
Hosking's role requires navigating both. Market-based enterprises can thrive due to their ability to engage in fast iteration cycles and product launches. This being said, technology choices made by Woolworths are bound to be influenced by enterprise-wide norms.
A recent hiring drive related to technology for his company brings out technologies based on cloud, machine learning, and new software frameworks. Those priorities suggest an effort to maintain the adaptability associated with digital commerce businesses while operating within the requirements of a large public company.
That balance is increasingly relevant across retail. Customers rarely distinguish between technology systems operating behind a brand. They simply expect reliability and convenience regardless of channel or transaction type.
Matt Hosking's leadership reflects the practical realities of that expectation. His focus on scalable platforms, engineering engagement and marketplace technology demonstrates how retail technology leadership increasingly depends on connecting strategic growth objectives with the everyday work of building and maintaining software that customers rely upon.


