Chief Technology Officer

SQiBLE | Remote (Australia) | Full-time

Most engineering functions are being quietly retrofitted for AI. Ours is underway and small enough to build properly, not bolt on. Busy enough, too, that it has to work on live client platforms this quarter, not in a strategy document. One CTO, reporting to the CEO, on the leadership team, owning the strategy, the platform and the team across ERP, CRM, integration and custom software. Take what's running and push it much harder.

Be clear on one thing before you read on: this is a hands-on job. You'll be in the architecture every week, designing it and arguing about it, and building it yourself when that's what the situation calls for. There's no principal architect underneath you to hand it to. Still reading? Keep going.

What you'll own

- Technology strategy. Where the platform goes over the next three years. What we build, what we retire. You bring the plan; you don't wait for one.

- The platform, hands on. Architecture, standards, reusable shared components over bespoke one-offs. You design the hard parts, review what the team ships and unblock what's stuck. You decide what good looks like and you show them.

- The function. Structure, hiring, capability, performance, retention, cost. You're building a function, not supervising a team. Some of that capability lift happens by you sitting alongside people and showing them.

- AI and automation. Into how we build and into what we ship, as reusable platform services, not bolt-ons. This is the centre of the job, not a workstream inside it. Early on you'll be close enough to it to shape it directly.

- Delivery and its economics. Estimation accuracy, margin, rework, utilisation. A CTO who can't read a delivery P&L; is a technical lead with a better title.

- Clients and revenue. Solution design, the hard scoping conversations,



and the executive relationships that keep valuable accounts. You explain technical calls to non-technical people without losing the detail.

- Risk, security and compliance. Client data, IP, contractual obligations, and the reporting line up into Jonas. You surface problems early and own the path out.

The kit

PHP, .NET Core, Vue.js, JavaScript, MySQL. ERP and CRM (Infor CSI and Zoho ideal; Dynamics, NetSuite, Odoo all fine). APIs, ETL, middleware. AWS and Azure.

You need to be current enough in this to design in it and be useful in a code review, not just talk about it.

The bar

10 years in engineering, at least three leading, including a stint owning a whole technical function end to end. Still technically current, not two or three years removed from it. Real client-facing delivery. Consulting, implementation, managed services or product background. Comfortable with numbers, because you'll be held to some. AI in your daily workflow and in what you've shipped, and you can show us both. "I tried ChatGPT once" ends the conversation.

The honest version

This is a small business inside a very large one. You won't inherit 200 engineers and a platform team. You get a tight, capable group, a live platform, real clients and nothing between you and a decision. The flip side is that there's nobody to hand the hard technical work to. If scale is what you're chasing, this isn't it. If control is, it is.

Don't bother if:

✘ You need a big team and a big budget before you can do anything.





✘ Leadership means a strategy deck and a quarterly steering committee.

✘ You haven't been near the architecture in five years and you're fine with that.

✘ You want the title without the delivery accountability.

✘ You need certainty before you'll move.

✘ Your AI game stops at ChatGPT.

We need to talk if you can say yes to at least 4 of these 6:

✔ You've built or rebuilt an engineering function and it outlasted you.

✔ You've changed how a team builds, not just what it builds.

✔ You're still close enough to the work to design it and be useful in a review.

✔ You've owned the numbers, estimates, margin, cost of delivery, and been measured on them.

✔ You decide on incomplete information and wear what follows.

✔ You've sat across from a client's executive team and held the room.

A word from the person you'd report to

"Progress over perfection, always. I'm not going to tell you how to build it, but I do expect to find you in the detail with the team, not above it. Bring me a platform that scales and a team that's firing, and the technology calls are yours."

About Us

SQiBLE builds software that connects the entire journey from quote to delivery, specialising in automotive and manufacturing. Small, and proud of it. No layers, no politics, no waiting three weeks for a decision. You ship, you watch it land, you do it again.

Behind that small team sits Jonas Software and Constellation Software, Inc. (TSX: CSU.TO): 20,000 people and $3.5 billion USD, going nowhere. Startup pace, enterprise backing. That combination is rare, and it’s exactly why people stay.

What’s in it for you

- Flexible remote working (Australia-based)

- Employee Share Purchase Plan (Constellation Software Inc.)

- Flexible leave options

- EAP wellbeing support
- A role that will be unrecognisable in 24 months because you redesigned it

📌 Chief Technology Officer (Melbourne)
🏢 SQiBLE
📍 Melbourne