Skip to content

About

Who I am

Ovina Peiris is a technology leader based in Perth, Western Australia, who leads the engineering and architecture function at an Australian omnichannel retailer with 50+ locations and a high-growth e-commerce operation.

My team of 20+ engineers, spanning ERP development, full-stack engineering, integration architecture, and technical analysis, builds and operates the technology platform that connects our stores, our website, and our data.

What the platform looks like

We run a composable commerce architecture. Every component is API-connected, independently deployable, and designed to be replaced without rebuilding the whole system.

  1. 01Experiencestorefront · apps · in-store
  2. 02Commercecatalogue · cart · pricing
  3. 03Orchestrationintegration · events · contracts
  4. 04Systems of recordERP · inventory · finance
  5. 05Datawarehouse · models · reporting
  6. 06Intelligenceagents · context · retrieval
Fig. 01 · Platform section, by layer
Platform layers and responsibilities, as led by Ovina Peiris
LayerResponsibility
ExperienceStorefront, internal applications, and in-store tooling. Server-rendered, incrementally revalidated, delivered from the edge.
CommerceHeadless commerce services. Catalogue, cart, pricing, and promotions, consumed through APIs rather than bundled with the frontend.
OrchestrationThe integration layer. Event routing, contract enforcement, retries, and error handling between every other layer.
Systems of recordERP as the single owner of inventory, purchasing, finance, and fulfilment. One system owns each data domain.
DataCloud warehouse, transformation pipelines, and reporting marts. The layer that turns operations into decisions.
IntelligenceLanguage models reading production business data through structured tool interfaces, with human judgment kept in the loop.

How I got here

The journey started in Colombo, Sri Lanka. Capital markets technology first, then e-commerce consulting across APAC and EMEA. That work brought the move to Perth, Western Australia. New country, new timezone, new scale of ambition.

Perth was where things shifted. The search for a harder problem led to an Australian omnichannel retailer in the middle of a technology transformation. What started as a Senior Technical Business Analyst role turned into something bigger. Within two years the scope had grown into leading engineering and architecture across the entire platform. The title caught up to the work, not the other way around.

The background is a mix of technical and commercial: a BSc in Information Technology from the University of Moratuwa, an MBA from the Postgraduate Institute of Management at the University of Sri Jayewardenepura, and a CIMA qualification. The combination of engineering thinking and business fluency is deliberate. The best technology decisions happen at that intersection.

What I believe

Five principles that guide how I build:

  1. Systems should be composed, not monolithic.

    The best architectures are assembled from purpose-built components, not locked into a single vendor's vision.

  2. AI should augment judgment, not replace it.

    The value of AI in enterprise isn't automation for its own sake: it's giving smart people better information, faster.

  3. Scale is designed, never accidental.

    Systems that scale reliably are the ones that were architected for scale from the beginning, not patched into it later.

  4. The best architecture is the one your team can operate.

    Elegance means nothing if your team can't deploy, monitor, and troubleshoot it at 2am.

  5. The title follows the work.

    Don't wait for permission. Do the work of the role you want, and the title will follow.

What I'm working toward

I'm building toward a CTO role, not as a destination but as the natural next step in how I think, build, and lead.

That means deepening my understanding of AI strategy at the enterprise level, growing my ability to communicate technology decisions to boards and executives, and building the systems that let engineering organisations scale beyond what one person can manage.

I write about that journey here: mostly on composable architecture, ai-augmented operations, and engineering leadership.

Read the writing →

Frequently asked questions

Ovina Peiris is based in Perth, Western Australia, Australia.

Ovina Peiris is Head of Engineering & Architecture for an Australian omnichannel retailer. He leads a team of 20+ engineers spanning ERP development, full-stack engineering, integration architecture and technical analysis.

Ovina Peiris holds a BSc in Information Technology from the University of Moratuwa (Sri Lanka), an MBA from the University of Sri Jayewardenepura, and a CIMA qualification from the Chartered Institute of Management Accountants (UK).

Ovina Peiris works across headless commerce platforms, ERP systems, integration and iPaaS tooling, cloud data warehouses, and AI agent frameworks. His focus is the architecture that connects them rather than any single product.