Technology Delivery Lead

WeFlex helps people with a disability, people in aged care, and Australian war veterans live longer, healthier lives through access to physical fitness, allied health and therapy supports. We're a registered NDIS provider. We've delivered over 50,000 sessions, grown 30x in 2.5 years, and we plan to keep doubling every year.

The seat
Our COO sets the business priorities. Your job is to make them ship.

You sit between the business and the build. A priority comes in ("clients aren't reporting back", "kill our legacy CRM"). You work out the real problem, scope it, sequence it, build part of it yourself, and run the delivery cadence so the team ships the rest, tested and documented.

How the tech function is structured:

The COO owns vision and business priorities. She d ---------- what matters and approves what gets built.
You, the Technology Delivery Lead, own the delivery engine: intake, scoping, sequencing, sprint cadence, BAU stability, documentation, and the development of our two junior devs. You also build.
Our Technology Solutions & Data Lead is your senior peer. He owns deep architecture, data and AI capability, and takes the hardest technical problems.
Two junior developers report to you.
Day-to-day you work directly with the COO. She sets priorities, you align the delivery plan with her, and development runs through scoping and review gates to catch mistakes early.

What you'll do day-to-day
Turn business problems into specs. You take an ambiguous brief from an exec and produce a scoped doc: the actual problem, what's in and out of scope, requirements with acceptance criteria, and how we'll test it.
Run delivery. Sprint cadence, ClickUp board, intake triage, dependencies, blockers raised early, weekly delivery reporting. You always know the status of everything in flight.
Build. You personally ship mid-complexity automations and systems: n8n workflows, Airtable systems, integrations across Supabase, GoHighLevel, Zendesk, Xero and our internal portals.
Keep the lights on. Bugs triaged, broken automations fixed or routed, systems stable, documentation current.
Coach. You review the juniors' work, pair with them on problems, and keep the quality bar high.
On AI
This part is a hard requirement. Claude, GPT, Cursor or equivalents need to already be core to how you diagnose, scope, build and document. The most effective tech lead we've had wasn't our strongest raw developer. He was the best we've seen at using AI to close that gap, and he out-shipped people with twice his experience. We hire for that pattern. The build task is where you show us yours.

Who fits
Your career path looks something like business analyst, then product owner, then delivery or tech lead, ideally on a live software product. Ten years of solo senior-engineer titles is the wrong path for this seat.
You've run delivery inside someone else's structure (a PM system, a product org, an exec's priorities) and got good at it.
You've shipped real automations and systems yourself and can show them: workflows, integrations, internal tools.
You've developed juniors who got measurably better under you, and you can name them when we ask for references.
You write plain business English. A COO can read your specs and Looms without a translator.
We weight what you can actually do over degrees, years of experience or industry background.

What this role isn't
A strategy seat. The COO owns business priorities and the roadmap; this role turns them into delivered systems.
A heavy DevOps, Kubernetes or infrastructure role. We run managed low-code at scale.
Open to agencies or dev shops. Individual, exclusive, full-time applicants only. No concurrent client work.
Pay and logistics
PHP 90,000 to 220,000 per month, depending on demonstrated capability.
Full-time, fully remote, AEST-aligned hours, Philippines-based.
To apply
Submit here: ----------

Two parts:

Part 1: application form. CV, portfolio link, 7 short written answers, notice period and salary expectation.

Part 2: build task. A real WeFlex scenario with sample data. You build a working artifact and record a short Loom walking through your thinking, your tool choice and your AI workflow. There's no time limit. We score the quality of the build.

We don't review applications without a completed build task. It's the highest-weight signal in our process.

Reviewed weekly. Open until filled.