Chief Technology Officer

/!\ NOT A JOB DESCRIPTION. A WARNING. Looking for a CTO.

Most CTOs shouldn’t even read this. No team. You build it.

No playbook. You write it. This is construction.Dust.

Noise. Bad cameras. No internet half the time.

People doing things their way for 20 years. You make systems that work anyway. AI.

Computer vision. Edge compute. Not in a lab — on site, where nothing behaves.

We’re talking: On-device inference on cheap Android phones Models that survive bad lighting, motion blur, partial occlusion Flutter frontends that work offline-first TensorFlow Lite quantized to INT8 running on devices with 3GB RAM Real-time defect detection where the ground truth doesn’t exist yet Clean datasets and managed pipelines? This will break you. Don’t care about your resume.

Care if you’ve shipped something that works when everything around it is broken. Have you: Shipped production CV outside a demo? Handled noisy inputs where labelled data barely exists?

Built edge inference without cloud fallback? Designed systems that degrade gracefully when connectivity drops to zero? Gone zero to one with no playbook?

This is that. $12T industry. Zero intelligence layer. Hasn’t changed in decades —not because it’s small, because it’s hard.

First to crack it owns the category. Real salary.Real equity — co-founder level, not token. Full-time or part-time or hybrid.

But equity isn’t the pitch, the pitch is a problem that won’t leave you alone at 2 AM. Need structure before you start — skip this. Need to be managed — skip this.

Read this and thought “messy… but I want in” — DM me. No resume.Just tell me what you’ve built or send this to that one person who doesn’t post much… but is always building something.