Munir Hassan

About

Reliable systems are designed at the boundaries, not just in the code.

Lead Engineer in Sydney, focused on distributed systems, engineering judgement in high-stakes environments, and building teams that make better technical decisions.

I’m Munir, a Lead Engineer in Sydney. I set technical direction across several teams and lead engineers directly, on customer-facing platforms where mistakes are expensive and every change has to be explainable: how it behaves under load, what it touches, and how to undo it.

My focus is distributed systems and the decisions around them: modernising business-critical platforms without big-bang rewrites, keeping customer state consistent across old and new systems, and releasing in a way that limits the damage when something goes wrong.

The decisions I write about here are ones I’ve had to make: replacing a fragile cache-expiry trigger with a queue and scheduler while deliberately avoiding a full event-driven rebuild; arguing for a data-model fix rather than patching a multi-tab bug; and preparing for a high-risk migration where the biggest risk wasn’t in the code.

AI is making code cheaper to produce. It hasn’t made reliable systems cheaper. I’ve set shared standards for AI-assisted development so a team’s output is consistent and reviewable, and I migrated this site with an agent and documented where it had to stop. My working view: safe automation starts with tightly scoped permissions; approval gates are the second line of defence, not the first.

Much of my career has been spent where reliability matters: pharmaceutical production software, insurance, energy and health. I’ve built product capabilities in a platform vendor’s R&D team and run high-traffic platforms for global brands, working across Australia, Italy, Malaysia and Bangladesh.

Selected impact

  1. About 80% faster page loads on a migrated customer journeyDesigned APIs on the legacy platform so the new front end could move independently, which sped up the migration and avoided a big-bang cutover. The first migrated journey loads about 80% faster than its legacy version.
  2. Customers keep their progress across two platformsDesigned session management shared between the old and new platforms, with sensitive cached data encrypted, so a customer can cross between them mid-journey without starting again.
  3. Progressive delivery adopted as a programme standardIntroduced canary releases with success metrics and rollback criteria agreed before release day. The approach is now the standard for major releases across the programme.
  4. Standards other teams build onMade automated end-to-end testing part of the definition of done, a model other teams now follow. Owned the content model for the headless platform, a reference point for multiple teams, and presented the target architecture to the wider engineering community.

How I think about engineering

  1. Systems fail at the boundariesOrdering, timing, retries and who owns the data. Make those assumptions explicit before production finds them. See where →
  2. Permissions before approvalsAn agent should only be able to do what is safe. Approval improves a decision; it doesn’t limit what can happen. See where →
  3. Don’t ship what you can’t define and explainIf you can’t say what a change does, what it touches and how to undo it, you aren’t approving it. You’re passing it along. See where →
  4. Fix the model, not just the bugA recurring defect is often a design assumption the product has outgrown. See where →
  5. Complexity has to earn its placeThe simplest design that holds up in production usually wins, including the rebuild you choose not to do. See where →

Path

  1. 2026 – now
    Lead Engineer · Bupa Australia

    Technical direction and engineering leadership for the modernisation of customer-facing platforms.

  2. 2022 – 2026
    Senior Developer · Bupa Australia

    Backend architecture for customer-facing platforms in a regulated environment, through the move from a traditional CMS to a headless, API-first architecture on Azure.

  3. 2020 – 2022
    Senior Software Developer · VMLY&R

    Technical ownership of high-traffic platforms for major brands: solution design, performance and third-party integrations.

  4. 2018 – 2020
    Senior Software Developer · AKQA

    Multi-site, multi-lingual enterprise platforms on .NET; set implementation standards and quality gates, and mentored developers.

  5. 2015 – 2018
    Senior Developer, R&D · Sitecore · Kuala Lumpur

    Built core product capabilities used by enterprises worldwide, including usage analytics at scale and Azure Marketplace provisioning.

  6. 2013 – 2015
    Senior Software Engineer · Aprosoft · Dhaka

    Led development of a loyalty platform with real-time transaction processing for a global petroleum company.

  7. Earlier
    .NET Software Engineer · Milan · Dhaka

    Enterprise software in regulated and large-scale domains, including pharmaceutical production, insurance and energy, in teams across Italy and Bangladesh.

Certifications: Microsoft Certified Solutions Developer · Sitecore Certified Professional Developer · SAFe Practitioner · Certified ScrumMaster.

Talks, conversations, collaboration

Happy to speak or compare notes on: Platform migrations without big-bang rewrites · Release risk and progressive delivery · Safe AI-assisted delivery in regulated environments · Leading engineers through the shift to AI.

Connect on LinkedIn →