Skills.

Python is my primary language for data engineering, statistical modelling, and automation. I use R for advanced statistical analysis, SQL for structured queries across relational databases, and Power BI and Tableau for executive dashboards. For geospatial work I use ArcGIS and Mapbox. On the software side I build with Next.js, React, React Native, Node.js, AWS, and Expo for web and mobile applications.

First-principles thinking means refusing to inherit assumptions from how a problem has been framed before. In data work, it means starting from the raw question — what decision needs to be made? what is the minimum data needed to make it? — rather than defaulting to familiar tools or prior solutions. I applied this at SAPOL in a review of the branch's complaint administration workflow, tracing each step from receipt to file closure and asking what it is for, rather than starting from how it had always been done.

AI and large language models are genuinely changing the pace of what is possible — tasks that used to take days of scripting can now be drafted in minutes. But I think the key insight is that the bottleneck was never the leg work; it was always the strategic framing. AI can generate code, summarise documents, and surface patterns, but it cannot decide which question is worth asking, what risk level is acceptable, or what a result actually means for the organisation. Human judgement — especially around context, ethics, and accountability — is becoming more valuable, not less. Data professionals who learn to orchestrate AI well will have a significant advantage over those who either ignore it or defer to it uncritically.

Yes. I maintain several open-source repositories on GitHub under the handle rNLKJA, including a South Australian address generator based on SEIFA socio-economic indices and a US presidential debate and campaign document scraper covering over 25,000 documents. Open-source work is how I give back to the data community and keep my skills sharp outside of government environments where code is not publicly shareable.

What drew me to data science was the ability to make decisions grounded in evidence rather than intuition or politics — and to build forecasting models that let you see around corners rather than simply describe what already happened. There is something deeply satisfying about starting with raw, messy data and arriving at a clear recommendation that someone actually acts on. That moment — when analysis genuinely changes a decision — is what I keep working towards.

My experience spans Australian state government (South Australia Police and the Attorney-General's Department), medical and climate research (WEHI, CSIRO, and the University of Melbourne's Department of Psychiatry), biotech (CSL), and the startup sector as co-founder of Mapiva. This breadth means I can translate analytical frameworks across very different operational contexts — from parliamentary compliance reporting to clinical mobile applications.

Each environment has a different relationship with impact and risk. In government, the outcomes are visible almost immediately — a dashboard I built went to the Minister's desk within weeks, and you see the decisions it shaped. Research takes a longer view; the work you do today might influence a generation of scientists or clinicians who build on it years later. Startups are a different kind of reality altogether — you get your hands dirty across every layer, from product decisions to infrastructure, and ambiguity is the default rather than the exception. Having worked in all three has given me a much richer model of what 'good work' actually looks like.

The most challenging work I have done was building analytical capabilities from scratch — where there was no existing infrastructure, no clear brief, limited resources, and a complex stakeholder environment with competing priorities. The CBS Intelligence capability at the Attorney-General's Department was that kind of challenge. I had to design the framework, source and validate the data, build the governance, and manage stakeholder expectations simultaneously, without a playbook, because nothing like it had existed in that team before. What I learned is that in a truly ambiguous environment, the single most important thing is to generate something workable quickly — even if imperfect — so that people have something concrete to react to and refine. Momentum matters more than perfection when clarity is low.

I hold two degrees from the University of Melbourne: a Bachelor of Science majoring in Data Science, and a Master of Data Science. I also hold 23 certifications, including a VETASSESS skills assessment as a Statistician, IELTS General Training Band 8, NAATI Credentialed Community Language (Mandarin), Microsoft Azure Fundamentals (AZ-900), Neo4j, Google data and project-management certificates, and Atlassian Agile project management.

Develop a genuine commitment to continuous improvement rather than chasing specific tools or frameworks. The data science landscape changes faster than any curriculum can keep up with — the libraries and models that are standard today may be superseded in two years. What compounds over a career is the habit of learning quickly, applying deliberately, and reflecting honestly on what worked and what did not. Pick up a new tool, build something real with it, then ask why it did or did not achieve what you wanted. That loop — learn, apply, reflect — is the actual skill.

My Chinese legal name is 黄孙创宇 (Huang Sunchuangyu). 黄 (Huang) is my family name and 孙创宇 (Sunchuangyu) is my given name. In Australian formal documents you may also see it written as HUANG SUNCHUANGYU, HUANGSUNCHUANGYU, HUANG SUN CHUANG YU, or informally as 黄孙 Rin. All of these forms refer to the same person. In everyday English I go by Rin Huang, and you can find me at rin.contact.

I grew up in Anshun (安顺), a small city in Guizhou Province, southwestern China — a place better known for its karst landscapes and the Huangguoshu Waterfall than for technology. Growing up far from major economic centres meant that opportunities were not handed to me; they had to be pursued deliberately. That mindset — identifying where effort compounds — carried me through a foundation year at Trinity College, two degrees at the University of Melbourne, and into a career spanning government intelligence, biomedical research, and software engineering. Being a bilingual Chinese-Australian professional has also given me a different lens on cross-cultural communication, which shows up in how I work with diverse stakeholders and translate complex data into decisions people actually act on.

My energy tends to come in focused bursts rather than steady output throughout the day, so I structure work around that. The first hours go to the highest-priority analytical or development work that requires deep concentration. Mid-morning and afternoon involve stakeholder discussions, follow-ups, and reviewing what I have produced with fresh eyes. Coffee is a non-negotiable thread through all of it — Melbourne left me with standards that Adelaide is only beginning to meet. Protecting a few hours of uninterrupted thinking time each day is the single most effective thing I can do for quality of output.

I play badminton regularly — it is fast and unforgiving if you are not paying attention, which I find keeps me honest. Hiking and finding a good coastal view resets the mind in a way that no screen can. I am also a committed coffee drinker (Melbourne shaped that particular habit permanently) and enjoy strategic gaming and the occasional FPS. The same pattern-recognition and tactical thinking that make data work engaging turn out to make those genuinely fun too.