Technical Product Manager / Product Ops | AI Product, AI Workflows

We're an early-stage startup looking for an intelligent, fast, AI-NATIVE TECHNICAL PRODUCT MANAGER who can turn a fast-moving product into something legible, organized, and easy to build against. Neurow is a productivity platform and life OS that integrates personal development and mental health to help goal-getters achieve more, in less time, with less burnout. At its core it's an AI agent that knows your goals, remembers your history, and works with you across multiple surfaces. We have 25 beta users onboarded to our MVP. Once the product is stable, we scale fast. We've been building faster than we've been documenting (some is organized and some is messy) and we need help with organization systems and team systems. WHAT YOU'D WORK ON - PRODUCT DOCUMENTATION. We have a product catalog with feature homes already structured and governed. You'd use AI to search our company second brain for the messy, scattered documentation and turn it into real feature documentation, checked against the codebase. Our docs live in Obsidian, our product lives in the code, and they drift. Keeping those two honest with each other is part of the job. - TEAM OKRS - Goals, Objectives, Key Results - DEVELOPER AND FEATURE COORDINATION. A few developers and AI agents will work in this codebase at the same time. Someone has to own who is working on what, which features touch the same parts of the system, and what has to land before what. The goal is catching the overlap on the board, before it becomes a merge conflict or someone blocked for a day waiting on work they didn't know was in flight. We have a starting point, and we know where the holes are. We haven't finished it. We'd want you to pick it up and make it a real working system, and we're genuinely open to how you'd do it. - TEAM COMMUNICATION, RUN ON SLACK. Slack is our coordination layer, so much of this role lives there. Keep engineering, product, and design in sync. Make sure nobody has to ask around to find out what someone else is building. Keep it useful instead of noisy. You'd shape how we use it. - USER FLOWS AND USER STORIES. For features that exist and features we're about to build. Written clearly enough that an engineer can build from them and a new person can understand the product from them. - THE WORK SYSTEM. Set up and maintain our sprint board and our broader pipeline in Asana and Linear. Run the sprint cadence. Keep the roadmap honest about what's next. - FINDING THE BOTTLENECK. Then building the workflow, automation, or SOP that removes it. WHO WE ARE LOOKING FOR YOU'RE AI-NATIVE. You use AI tools every day and you're comfortable in a terminal. Claude Code, Codex, Cursor, CLI workflows, agentic and autonomous workflows. We want someone who automates the business workflows around the work itself: intake, triage, status, coordination, reporting. If you've built autonomous or semi-autonomous workflows for yourself or a team, tell us about it. YOU'RE AN EXCELLENT COMMUNICATOR. This is a coordination role, so communication is important. You write clearly and briefly. You tell people things before they have to ask. And you're comfortable being assertive: chasing an answer, telling someone their work overlaps with someone else's, saying out loud that a date won't hold. Assertive and kind at the same time, not one at the cost of the other. YOU'VE BUILT COORDINATION SYSTEMS. You can look at a week of in-flight work and see where one task is quietly waiting on another, and what has to ship first. Or you've built the thing that surfaces it, so it keeps working when nobody is watching. YOU'RE TECHNICAL. You don't need to write code all day, but you can read a codebase, follow what's happening in a pull request, and tell whether a doc matches reality. YOU WRITE USER FLOWS AND USER STORIES THAT ENGINEERS AND DESIGNERS CAN ACTUALLY BUILD FROM. Clear, specific, with acceptance criteria or other needed documentation. YOU KNOW LINEAR, ASANA, AND SLACK well enough to set them up and maintain them properly (we are also open to other tools). NICE TO HAVE, but not necessary: - Writing SOPs and process documentation - Talking directly to users and turning what you hear into product decisions - Information architecture or knowledge management experience YOU'RE A GREAT FIT IF: - You think in systems. When you see a mess you see the structure hiding underneath it. - You're extremely proactive. You don't wait for a task list, you go find the bottleneck and fix it, and you bring us your own opinion on the product, not just your organization of it. - You're fast, and you'd rather ship a good version today than a perfect one next month. - YOU CARE ABOUT PRODUCTIVITY SYSTEMS. You have opinions about Motion, Sunsama, Akiflow, Lindy, Fantastical, Notion, Linear, Asana, or ClickUp, because you've used some of them. - YOU'RE INTO PERSONAL DEVELOPMENT AND MINDSET WORK. Tony Robbins, Andrew Huberman, Deepak Chopra, Atomic Habits. If names like these are part of how you think about your own life, you'll understand why we build what we build. - CONSCIOUS PRODUCTIVITY, GOAL ATTAINMENT, MENTAL HEALTH, AND HOW PEOPLE ACTUALLY CHANGE mean something real to you. WHO THIS IS NOT FOR Please don't apply if: - You wait for instructions or a task list before you start - You need day-to-day management - Your product experience is mostly slide decks and meetings - You think coordinating a team means running a weekly status meeting - Your first instinct in a new company is to replace what's there with your own version of it, before you understand why it's built the way it is To be clear about what's settled and what's yours: our documentation architecture is built and working, and we need it filled in, not rebuilt. Our coordination systems are a different story. There's a starting point and there are real gaps we already know about. That part we want you to take over and build out properly, and we want your thinking on it. We need someone self-managed and self-sufficient, who brings their own IDEAS to the table and wants to get their hands in everything to improve it. THE LOGISTICS - START DATE: You must be available to start the week of AUGUST 5. We're interviewing now. - HOURS: 15-25 hours/week for the first 1 month sprint, then 5-10 hours/week for ongoing team and product coordination. - LONG-TERM: We're hiring for a long-term relationship. The sprint is how we both find out if it's right. - TIME ZONE: Work from anywhere. Most of the work is async, however we need you available for live-sync communication for at least a 4-HOUR block per day (between 9:00 AM and 11:30 PM US Central Time). - SYNC: A video connect 1-2x per week. Everything else runs on Slack. - YOU'LL USE THE PRODUCT. You'd be organizing something you use every day. You need to use it to know where it's broken, and to have a real opinion about where it should go. ABOUT THE FOUNDER The founder spent 20 years in the human potential industry and 10+ years as an executive and productivity coach, with a background in behavioral neuroscience, NLP, and AI system design.