Kieron O’Donoghue

Work

How I work

I'm a Corporate Services Analyst working in the construction industry in Australia. My work sits where analytics, accounting, and operations meet — using data and systems to help a business run more smoothly. This page is about how I work rather than where.

Areas of responsibility

Business systems

Working with the systems behind day-to-day operations and keeping them reliable.

Reporting

Producing reporting that supports clear, confident decisions.

Process improvement

Finding the repetitive or error-prone steps and making them simpler.

Automation

Removing manual handling where a small automation does the job better.

Business systems & process improvement

A lot of my work is understanding how a process really works, then improving it — making the systems behind operations more reliable and less manual. Often the most useful change is a small one that removes a repeated step or a recurring source of error.

The construction industry is practical and deadline-driven, and corporate services has to keep pace with it. That context keeps the work grounded in real operational needs rather than theory.

The goal with reporting is clarity: the right numbers, in a form that's easy to read and trust. Good analytics should make a decision easier, not add more noise.

Analytics & reporting

I help turn operational and financial data into reporting that people can actually use. My background in business analytics is the lens for this — reading data well, and presenting it so the story is obvious.

Current learning

I'm developing my Python, SQL, JavaScript, and CSS through practical work and personal projects. I'm learning as I build, and I'd rather be honest about that than pretend to be more senior than I am.

Industries & topics of interest

How I approach problems

  1. Understand it first

    I map how a process actually works before changing anything. Most of the value is in understanding it properly.

  2. Simplify, then automate

    A messy process automated is just a faster mess. I simplify first, then automate what remains.

  3. Build in checks

    I add simple validation so a workflow flags obvious problems instead of passing them through silently.

  4. Keep it maintainable

    I favour solutions that someone else (or future me) can still understand and trust later.

I keep this page general and don't share confidential or internal detail about any employer's systems or data.