Technical Product Manager

ABOUT THE ROLE We need a Technical Product Manager who can be our in-house lead, someone who partners with our existing AI engineer contractors to keep building, rather than just handing off specs and waiting. This isn't a traditional PM role. You'll be embedded across our portfolio of vertical businesses, working directly with contractors and teams, moving between projects as priorities shift. You'll own both the technical product thinking and the hands-on execution of prototypes, MVPs, internal tools, and integrations, especially in the early, resource-light stages before a project has its own dedicated engineering team. As the team grows, this role is expected to evolve into hiring and managing other builders — so we're looking for someone who can operate as a strong senior individual contributor now and step into people leadership as the portfolio scales. Reporting directly to the CEOå and Head of Product, you'll evaluate priorities, identify tradeoffs, and provide recommendations on product direction, technical decisions, and resource allocation across multiple initiatives. While the CEO retains final decision-making authority, you'll provide the analysis, recommendations, and operational leadership needed to keep projects moving efficiently and effectively. As our portfolio grows, this role will evolve from a senior individual contributor into a people leadership position. You'll help define and build the product function, with the opportunity to hire, mentor, and lead additional builders as the organization scales. WHAT YOU'LL OWN Product Strategy Across Multiple Projects Partner with business unit leads to define product direction, technical scope, and priorities — often for ventures still finding product-market fit. Translate ambiguous, early-stage ideas into clear requirements, PRDs, and success metrics. Prioritize building now vs. later, given that resources are shared across the portfolio and every project is competing for the same attention. Support in building technical narratives for decks and funding rounds Hands-On Building Personally build MVPs, prototypes, and early product versions — this may mean writing code, configuring no-code/low-code tools, or standing up integrations, depending on the project. Ship fast, validate with real users or data, and iterate — favoring working software over polished documentation. Build the internal tools and lightweight automation that let small or nonexistent teams punch above their weight. Working Across a Portfolio Move between 2–4 active projects at a time, context-switching without losing momentum on any of them. Standardize just enough process (documentation, handoff notes, basic architecture decisions) that a project can survive you rotating off it. Identify patterns and reusable components across business units — no reason to rebuild the same login flow or admin panel five times. Communicate clearly and frequently with non-technical stakeholders who may not have visibility into the technical details. Judgment & Prioritization Triage constantly: with limited time and sometimes no dedicated team per project, you decide what gets your attention this week. Push back on scope creep and unrealistic timelines when a project's ambitions outpace its resourcing. Recognize when projects require additional resources and proactively recommend solutions. Validate the work and technical quality of our offshore teams Growing the Function As the portfolio scales, help define and build out the builder/product function — potentially hiring and managing additional Technical PMs or product engineers. QUALIFICATIONS Required 6+ years in product management or a hybrid product/engineering role, with direct, hands-on building experience (not purely spec-writing) — scripting, front-end/back-end development, no-code platforms, or technical prototyping all count. Comfortable working on multiple unrelated projects simultaneously, often with incomplete information and no dedicated team. Strong technical fluency: able to read code, understand system architecture, and make informed build/buy/integrate decisions. Experience taking a product from zero to a working first version, ideally in an early-stage or startup environment. Excellent written and verbal communication — you'll be the connective tissue between technical execution and business stakeholders who don't share your context by default. Preferred Prior experience at a startup studio, venture builder, holding company, or multi-brand/multi-subsidiary organization. Familiarity with traditional engineering and AI no-code/low-code tools (Experience standing up projects that were later handed off to dedicated engineering teams. Background in a technical discipline (CS, engineering) or equivalent self-taught technical depth. Exposure to robotics; IoT is a nice-to-have, not a requirement. WHAT SUCCESS LOOKS LIKE Multiple projects have working, validated product versions that started as your prototypes or the support you've given other builders. Business unit leads trust you to make the right call on scope and priority without hand-holding. Projects you've rotated off of continue running smoothly because you left them in a maintainable state. Leadership has a clear, current picture of which projects are gaining traction and which need investment or should be sunset, informed by your product judgment. You've laid the groundwork to bring on and manage additional builders as the portfolio grows. A NOTE TO FIT This role suits someone who gets energy from variety and ambiguity, not someone who wants deep, singular focus on one product for years. We value curiosity, ownership, humility, speed, and thoughtful debate. Strong opinions are welcome, and they should be backed by data and a willingness to adapt. #J-18808-Ljbffr