Blog
26 July 2026 · Australia

How I would pivot
to non-clinical now.

All you need is a problem that annoys the hell out of you.

The short version

If I was starting the pivot out of clinical today I wouldn't start with my CV. I'd learn to vibe code: describe a problem that annoys you to an AI tool in plain English and build the thing you wish existed. I'm not a developer and that's how the career quiz on this site got built.

You end up with something to point at that isn't a clinical caseload, and a reason to be in rooms full of people building things.

Below is how to pick the problem, where to build it, and what to do with it once it exists.

That career quiz on this site, the one that matches your clinical skills to non-clinical roles? I built it.

I'm not a developer and I don't know how to write code. I built it by describing what I wanted in plain English and working with AI until it became what I imagined - a quiz for allied health folks to match their skills to non-clinical roles in a meaningful way.

All I had to do was explain it to AI the same way I'd explain it to you over coffee - ICYMI this = vibe coding.

Which is why, when people ask what I'd do if I was starting the pivot out of clinical today, I don't say update your CV.

I say learn to vibe code. Everyone has something they can build - just think of something that annoys the hell out of you (and probs a few of your friends). Then open Lovable or v0 or Claude Code (my favourite) and describe the solution you wish existed.

It can help to have some reference products you enjoy using that will help it come up with the designs. And then you get to iterate on it.

What you come up with might only fix part of the problem. That's fine. Then you put on your big boy/girl pants: hand it to the people who have the same problems and ask for brutally honest feedback - take the feedback and iterate again.

Next you wanna go find your new people. This could be a local vibe-coding meet-up, or online if that's more your speed. Show up, share what you've made, and be helpful to the other folks there, you can:

You can also branch out into startup events or whatever industry your thing belongs to, and go meet the people already working on problems in that space.

No guarantees but by going through this process you'll end up with something to point at that isn't a clinical caseload, and it gives you a reason to be in rooms full of people building things - as well as something cool to talk about.

Have a crack and tell me what you make. Or just tell me the thing you whinge about at work, cos I'd like to know if it's buildable 🤞

This first went out to Post-MDT subscribers on 26 July 2026. You can read the original edition in the archive, or get the next one in your inbox.

Read enough? Go find the role.

The blog is the why. The guide and the quiz are the which: the non-clinical roles your clinical training actually maps to, and what it costs (in time and money) to get there.