- Domain
- Regulated or safety-critical: healthcare and hospital operations, emergency management, public safety, govtech, utilities, ports and logistics, critical infrastructure, industrial. About ten of my eighteen years are here.
- Company stage
- Established and durable — Series A and beyond, profitable SMBs, established private companies, mature product companies.
- Team size
- 25–50 engineers is the sweet spot; 10–25 works where the problems are interesting. Company headcount is not a constraint — span of control is.
- The mandate
- Professionalizing an engineering function: first real CTO, inherited mess, unpredictable delivery, broken process. Equally comfortable inheriting a team or building one.
- Product shape
- B2B SaaS, mobile-central, used in the field or offline. App Store and Play Store submission and appeals are a core competence.
- Scope
- I set technical direction and make technology choices. Not a principal or solutions architect — the hands-on infrastructure, networking and IAM remit is not the job I want.
- Product
- I want product direction in scope. What I need alongside it is a product and design function to execute the craft beneath it, rather than being the one writing every spec and drawing every screen.
- Location
- Based in the Laurentians, north of Montreal. Remote or hybrid in Montreal; remote or hybrid in Toronto, where I would relocate for the right role. Fully remote anywhere else in Canada. Ottawa is within driving distance for occasional in-person.
- US roles
- Available fully remote to US employers as a contractor or through an employer of record. Not available for roles requiring physical presence in the United States, US work authorization, or a US security clearance.
- Engagement
- Permanent, fractional, interim and consulting CTO engagements.