↓Skip to main content

About Me - Mugunth Kumar

Who I Am #

I’m an engineering leader with over 20 years of experience building technology that creates real impact. My journey has taken me from India to Singapore to Melbourne, giving me a global perspective on technology leadership.

I’m a polyglot engineer — I believe a software architect should see the big picture and use the right language and stack for the right product, user, and scale. I’ve shipped production systems in Python, Rust, Go, TypeScript, Kotlin, and Swift.

Five core values run through everything I do — personally and professionally. They aren’t aspirational abstractions. They’re decision-making heuristics that show up in how I build teams, architect systems, and choose what to work on.

1. Fairness #

Decisions should be objective. Opportunities should be earned. Evaluation should be consistent.

In practice, this means building teams where the hiring process is structured, the growth path is transparent, and diverse perspectives aren’t a metric — they’re how better solutions emerge.

  • Improved gender diversity from 5% to 30% through rubric-based, bias-free hiring at Steinlogic
  • Expanded international hiring (New Zealand, Colombia) during COVID at Openpay, improving global delivery capabilities
  • Created capability frameworks and technical guilds to democratize knowledge and growth opportunities at every company I’ve led
  • Built structured hiring rubrics aligned with capability frameworks — consistent evaluation, not gut feel

2. Sustainability #

Leave it better than you found it — whether it’s a codebase, a team, or an infrastructure bill.

I apply this to everything I touch: don’t waste resources, optimize for the long term, and leave things in better shape than you found them.

  • PaperCut (certified B Corp) — built their mobile engineering capability by upskilling existing engineers rather than hiring externally. Sustainable team growth, not disposable contractors
  • Reduced operational costs to ~$30/month for a meeting data platform serving sub-100ms queries (Pink Cloud)
  • Built self-hosted infrastructure for Nool on homelab — Forgejo CI, Caddy, Cloudflare Tunnel, Watchtower — no unnecessary cloud spend
  • Chose pgvector over Qdrant for Nool’s semantic search — no new infrastructure when PostgreSQL already handles it with transactional integrity
  • Consistently optimized infrastructure costs without sacrificing reliability (e.g., 90% cost reduction through right-sizing)

3. Authenticity #

My work must reflect who I am and what I believe. Professional life is an expression of identity, not just a means to an income.

I choose projects that align with my lived experience and values. This isn’t idealism — it’s how I sustain the energy and conviction needed to build things that matter over years, not months.

  • Pink Cloud — 8 years (2017–2026), from Distinguished Technical Fellow to CTO. Built subscription platforms, ETL pipelines, and led Australian expansion with university partnerships. You don’t stay somewhere for 8 years unless the work genuinely matters to you
  • Nool — saw a gap in the reading space that Goodreads and StoryGraph aren’t filling. Built semantic book discovery from the ground up rather than shipping another recommendation feed
  • Exhibit AI — evidence analysis for family law proceedings. Built privacy-first architecture (local LLM screening, raw data never leaves the network) because the domain demands it
  • Openpay — a BNPL that deliberately partnered only with car repairs and healthcare, not impulse-buy markets. The company didn’t survive, but the principle was sound
  • My programming books (h-index: 35, translated into 3 languages) — written to teach properly, adopted by universities because the content held up

4. Growth and Self-Awareness #

Continuous personal development and honest self-reflection. Staying curious about my own thoughts and behaviours, learning from experiences, challenging assumptions, and evolving.

This is the value that connects my books to my leadership. The same methodology that achieved an h-index of 35 is what I apply in every team — assess where each person is, build from their existing skills, and accelerate them to productivity.

  • PaperCut: Turned 4 Go engineers into mobile specialists, eliminating external hiring needs — by meeting them where their skills already were
  • Education Horizons: Coached tech leads into people leaders within 90 days; trained associates to run production releases within 3 months
  • Steinlogic/RedMart: Scaled from 1 engineer to 10, serving as the primary engineering team through to Alibaba acquisition
  • Reduced attrition from 30% to under 5% — people don’t leave when they’re growing
  • My own embeddings journey — highlight-vectors → Resonance → Nool — reflects this: I don’t adopt technology by plugging in APIs. I learn it ground-up before shipping it in production

5. Ubuntu and Self-Transcendence #

“I am because we are” — my existence is fundamentally interconnected with others.

In a team context, this means building systems and knowledge that outlast any individual — including me. It means investing in people and processes that continue to deliver value long after I’ve moved on.

  • Built incident management processes and trained teams to run them independently (Education Horizons)
  • Created architectural decision records (ADRs) ensuring technical choices were documented and challengeable (Steinlogic)
  • Designed CI/CD pipelines that enable junior engineers to deploy safely without senior oversight (PaperCut, Pink Cloud)
  • Built cultures where engineers felt safe raising concerns, leading to earlier issue detection and faster resolution
  • Open-source contributions (MKNetworkKit, MKStoreKit — 5,000+ GitHub stars) — knowledge shared freely, used by thousands of developers worldwide

The Five Questions I Ask Before Every Decision #

When complexity threatens to overwhelm — as it inevitably does — these values provide orienting questions:

  1. Is this decision fair to the team, users, and stakeholders — or does it favour the loudest voice?
  2. Is this sustainable — will it scale without accumulating waste, debt, or burnout?
  3. Are we building the right solution, or the expected one?
  4. Are we learning from this, or repeating patterns that feel safe?
  5. Does this create value beyond the immediate deliverable?

When these questions compete, context determines priority. The willingness to sit with that tension and accept that consistency may require different choices in different circumstances is itself a form of leadership maturity.

What I’m Looking For #

I’m most effective in environments where the technology matters and the problems are real:

  • Growth-stage companies needing to scale teams and systems sustainably
  • Organizations adopting AI/ML where I can apply strategic + hands-on expertise
  • Cross-functional leadership requiring alignment between product, engineering, and business
  • Teams that care about craft — where quality, coaching, and long-term thinking are valued

I’m based in Melbourne, Australia and open to new opportunities.

“Leave it better than you found it” — whether it’s the Earth we inhabit for less than a century, our relationships, our workplaces, or our communities and shared spaces.

Download PDF Version