Job Opportunities API

ShiftCare builds care management software that helps NDIS, aged care, home care and disability support providers roster staff, coordinate clients, and run their businesses. We are growing fast across Australia, the US, Canada and the UK, and we are looking for a technically minded, design-opinionated Product Owner to join our Product team. This role is native to the way product is actually built now: agents do the heavy lifting, humans make the calls. ShiftCare runs an AI operating system for product work — agents scan competitors, synthesise support tickets and sales signals, draft specs, score the backlog against revenue, and assemble the weekly operating picture. This role runs that system. You will design the agent workflows, write the prompts and skills that power them, review what the machines produce with a sceptical eye, and make the judgement calls that should never be automated. You will also be the person who refuses to ship ugly software. You have strong, articulable opinions about user interface design — hierarchy, spacing, interaction, copy — and you can defend them in a design critique and in front of customers. And when something ships, you can explain it in plain English in a way that makes a time-poor care provider actually adopt it. This is a hands-on, high-autonomy role. We are not interested in how many years you have carried the Product Owner title. We are very interested in whether you can think in systems, build with agents, hold a bar on interface quality, write with precision, and move work forward without being managed. If you are a career backlog administrator, this is not the role. If you build agent workflows because you can't help yourself, have a genuine point of view on where AI is taking the product craft, and wince at bad interfaces — read on. What you will do Run the AI operating system. Own the agent workflows that drive our product pipeline — from raw customer request through prioritisation, spec, engineering handoff and release. You will write the prompts, skills and scheduled jobs (cron) that do the heavy lifting, review their output with a sceptical eye (does this account for what we've already shipped?), decide what gets automated and what stays a human call, and improve the system every week. Set the quality bar on UI design. Partner closely with design, critique flows with a genuine eye for interaction and visual detail, and refuse to ship experiences that are merely functional. You will sketch, wireframe or prototype to make ideas concrete, and you will be one of the people who says "this is not good enough yet" — and can say exactly why. Get into the technical detail. Read the API, query the data, understand the data model, and reason about trade-offs with engineers rather than relaying messages between them and the business. Write specs that engineers do not have to reverse engineer. Prioritise with revenue in mind. Shape the roadmap by weighing net-new revenue, churned and at-risk deals, support ticket volume, and logo and staff volume — split by region (AU, US, CA, UK, global) — alongside strategic fit and competitive position. You bring ranked options to the decision with sources, not vibes. Market what you ship, in plain language. Write the blurb, the announcement and the help-article draft that turn a technical capability into a benefit a busy care provider immediately understands. You own adoption, not just delivery — shipped-but-not-adopted is your failure, not marketing's. Own and groom the backlog. Keep a healthy, well-prioritised backlog in Linear with clear user stories, acceptance criteria and requirements, so the team always knows what is next and why. Drive delivery. Run refinement, planning and reviews, keep work unblocked, and make scoping calls in the moment rather than escalating them. Stay close to customers. Gather and synthesise feedback through support conversations, user testing and direct customer contac