Matthew OldachAI & automationLet's talk
About chapter pop-up book

About chapter preview.

Open About chapter page ↗Open Services page ↗

Choose a chapter to turn through the book in order. Viewing About. Keyboard and reduced-motion navigation switch directly.

Matthew, in person

I'm a bioinformatician who drifted into engineering because the analysis kept depending on the plumbing. About 10 years later I work across software, data and practical AI automation. I still like figuring out how something works, and then making it useful to the person who has to live with it.

Where I've been

I trained in marine biology at Dalhousie, then did an M.Sc. in bioinformatics at the University of Calgary. Research jobs followed in Montreal and Calgary, analysing genotyping, methylation and sequencing data. I co-authored a paper in Nature Genetics (2019), and my genomics papers have about 176 citations between them.

Since 2021 I've been a consultant with Amaris, placed inside Roche and Genentech. I've curated scientific data, tested software for sequencing instruments, and now run the infrastructure under Genentech's internal AI projects. The longer version, with results, is onthe Experience page.

How I work

I write things down where people will look for them. A recovery procedure belongs in the repository, next to the code it rescues, and a new team should be able to set up from a template without booking time with me.

I start new AI tools with the smallest safe permission. The coding agents I put into a regulated pipeline began read-only, then got permission to comment. They still can't change code on their own.

And I like a before-and-after number. A genomics lookup going from 15 minutes to 15 seconds is easier to defend than "it feels faster".

What I do for small businesses

The same habits work for a team of five. I help small businesses find one workflow where AI can save real hours, then build that piece properly:

  1. We map the workflow as it actually happens, workarounds included.
  2. We pick one bounded change and agree how we'll measure it before I build anything.
  3. I build it so you can see what it's doing, with logs and plain-language docs, and a person in the loop wherever judgment matters.
  4. I hand it over with written ownership, so it keeps working after I've gone.

Sometimes the honest answer is a better spreadsheet, and I'll tell you that. See the ways we can work together.

Outside the work

Disc golf, backcountry ski touring, board games and video games. Ski touring is the one that sounds most like my job: you read the snow carefully before you commit to a slope. All four give this paper workshop some of its personality.

Get in touch

Hiring, or have a workflow that eats your week? Emailmoldach686@gmail.com or find me on LinkedIn. I'm near Edmonton, Alberta, on Mountain time, and I work remotely with teams in other time zones. My code is onGitHub and my papers are onGoogle Scholar.