CTO&Co-Founder — Ship AI-Powered Product (Remote)

<p>90% of vibe coding projects never become real software.</p><p>People build fast. They generate features, fix bugs, add pages.</p><p>But they can't ship. Because they have no idea what they actually built.</p><p>No structure. No tracking. No path to production.</p><p>That's not a tool problem. That's a category gap — and nobody's closing it.</p><p>We are.</p><p>Codelogs.ai turns AI-coded projects into real, shippable software. The operating system above Lovable, Bolt, and V0.</p><p>Built. Live. First users in. First positive market and pmf signals received. Target: €1M MRR. 12 months. Max 10 people.</p><p>---</p><p>We're hiring a CTO. Co-Founder Level.</p><p>Not a senior engineer. Not a tech lead.</p><p>You are the engineering team. You ship. You talk to users. You track what's working. You iterate. Daily. No manager sets your priorities. No PM writes your tickets. You open Claude Code at 7am because you already know what to build next.</p><p>The product is built: Chrome Extension, full-stack, clean codebase, documented. Clean handover on day one. You're not starting from scratch. You're taking it to exit.</p><p>What that means day-to-day:</p><p>→ Ship working product every single day: features, fixes, experiments</p><p>→ Own the product end-to-end: architecture, performance, new features</p><p>→ Run customer interviews yourself. Find patterns, feed them into the roadmap</p><p>→ Build and own the data layer: usage tracking, retention signals, drop-off points</p><p>→ Use Claude Code / Cursor as your primary build method</p><p>→ Make product decisions - you won't be handed a spec sheet</p><p>→ Lay the foundation so that when we hire, onboarding takes days, not months</p><p>Remote. Fully available. Full product ownership.</p><p><strong>You're not working for a first-time founder.</strong></p><p>Volker Hein. Former SAP CTO, responsible for sales in 16 countries. Spent the last 5 years building a 7-figure consulting business helping software CEOs scale and exit. He founded Codelogs out of his own frustration with AI-driven development. This is hands-on with someone who's actually done it.</p><p>---</p><p>You're a fit if:</p><p>You've done this before. You've taken a product from early traction to exit or close enough that you know what that year actually costs.</p><p>You ship the day the idea lands, not the day the spec is approved.</p><p>You read your own metrics. You fix things before anyone asks.</p><p>Speed isn't your goal, it's your default.</p><p>→ You've shipped full-stack products solo or in a very tiny team</p><p>→ You write clean code fast and know when "clean enough to ship" is the right call</p><p>→ You treat customer conversations as engineering input, not a distraction</p><p>→ You use AI coding tools at an agentic level, not Copilot autocomplete, actual workflows</p><p>→ You instrument your own features and actually look at the data</p><p>Not for you if:</p><p>→ You want "frontend" or "backend", not both and everything else</p><p>→ You need someone to write the tickets</p><p>→ You're not comfortable talking directly to customers</p><p>---</p><p>This is a 996 role. Founder-level responsibility, founder-level upside.</p><p>If that sounds exhausting, this isn't for you.</p><p>If that sounds like finally the right room, read on.</p><p>Compensation: Equity-based compensation. Discussed openly.</p><p>---</p><p>To apply, pick one:</p><p>1. Send a 60-second Loom: a product you shipped and what broke along the way</p><p>2. One paragraph: the hardest technical decision you made under pressure and would you make it again?</p><p>3. DM me with what you'd build in the first 30 days at Codelogs and why</p>#J-18808-Ljbffr