Photo: Josh Olalde / Unsplash
Where things stand
We’re not actively hiring right now. PointCPD is built by a small, practical team, and we’d rather grow deliberately than post roles before we genuinely need them. When that changes, roles will be listed here first — not on a generic job board before this page reflects it.
What kind of team we’re building
PointCPD sits at the intersection of construction-industry knowledge and software product work — the module content needs a subject-matter expert’s judgement about what actually matters on a residential site, while the platform itself needs proper software engineering discipline (an immutable points ledger, verified payment-gated entitlements, real accessibility standards). When we do grow the team, it’ll be roles that genuinely span that intersection, or that support one side of it well: content authoring and review from people with real building industry experience, and platform engineering from people who take the non-negotiables (server-side verification, audit-exportable records, accessible interactive design) as seriously as we do.
The authoring pathway — open now, informally
Even without a formal hiring process open, we’re genuinely interested in hearing from subject-matter experts — practising builders, site supervisors, or trainers — who might want to help author or review future modules. Content review and authoring is often how people end up working with us before any formal role exists on this page, since it’s low-commitment for both sides and lets us see how a working relationship actually functions before either of us commits to more. If that’s you, get in touch and tell us your background and what area of building practice you know best.
Why we’re deliberate about this
CPD content that feeds a licensed builder’s actual licence renewal is not a place to cut corners on quality or move fast for its own sake — every generated or human-authored question and every module goes through real review before it publishes, and we want the people doing that review (and everyone else on the team) to be genuinely good at what they do, not just available. That’s a slower way to grow a team than posting a batch of roles and hiring quickly, but it’s the right trade-off for what we’re building.
What to expect if you reach out
A real reply from a real person on the team, not an automated acknowledgement. We’re small enough that every message that comes in through our contact page gets read personally, and if there’s a genuine fit — whether that’s a future formal role or an informal authoring relationship right now — that’s the conversation we’ll have directly.
What “small and deliberate” actually means day to day
Right now, module content, platform engineering, and day-to-day operations are handled by a genuinely small group working directly with each other — there’s no layer of management between the people building the product and the decisions about what gets built next. That’s part of why real feedback from builders using the platform, and real subject-matter input from authoring conversations, has such a direct line to what actually ships. Growing the team deliberately is partly about protecting that directness for as long as it makes sense to.
What working with us looks like day to day, if it comes to that
Direct communication, real ownership of a specific area rather than a narrow ticket queue, and a genuine expectation that quality and accuracy matter more than shipping speed for its own sake — particularly for anything touching module content or the points ledger. That’s not a startup platitude; it reflects the actual non-negotiables we hold ourselves to on the engineering and content side, and we’d want anyone joining the team to hold themselves to the same bar.
Stay in the loop
There’s no formal careers mailing list yet, in keeping with how deliberately we’re approaching this — but if you reach out and mention you’d like to be told when we’re hiring formally, we can reasonably keep track of that as a small team. In the meantime, this page will always reflect our actual current hiring status, not a placeholder that goes stale.