Product Manager

PRODUCT MANAGER Location: Boston / Remote (flag: spec says Pacific / Central / East Coast acceptable — narrower than the other JDs' "Boston / Remote." Confirm which you want.) Employment Type: Full time Location Type: Remote Department: Product WHO THIS IS FOR Most PM roles hand you a roadmap and ask you to turn it into tickets. This one doesn't have a head of product doing that — it has a founder who's still defining the hard questions, and a team that executes well but has no dedicated owner for what comes next. You've owned a product line end-to-end, not just the process around one. You know the difference between running discovery calls and actually changing your plan because of what you heard on them. You've shipped something where the whole fight was making it feel effortless, not making it feature-complete. You're not looking for a defined roadmap to execute. You're looking for the open questions — provenance, version propagation, what belongs public versus private — and the room to drive them from fuzzy to decided yourself. You live in AI tools day to day — comfortable building in Claude Code or similar — and you track the rough edges of what's possible right now. Not so you can build the flashiest thing, but because the actual job is taking what's dense and technical underneath and making it disappear for someone who isn't AI-native themselves. If a customer's daily tool of choice is a basic chat window, effortless is the whole bar. ABOUT EDISYL edisyl builds AI solutions that turn messy institutional data into decisions, workflows, and outcomes. We came out of blockchain data infrastructure — 8 years, 20+ chains, 700M+ resolved wallets — and now deploy that capability to enterprises navigating the same challenge: how to make their data work for them at scale, without armies of analysts. We have active deployments with a financial institution and Interlochen, a proven architecture, and inbound from firms that need what we've built. The technology works. What we're building now is the enterprise motion around it. THE ROLE edisyl's team executes at a high level. What grows in importance as we scale is dedicated ownership of the long-term roadmap, so velocity is pointed at a compounding plan where each build deliberately sets up the next. That ownership currently lives part-time across several people; this role makes it someone's full focus. We're building a genuinely new product surface — public knowledge packs with private company overlays on top of Forge, Lattice, and Stratum. It lives or dies on getting the hard product questions right, and those need a dedicated owner now, while they're still being defined, not after we've shipped the wrong answer. This isn't a project manager role — the team self-manages well. And it isn't a head of product role — vision and prototyping stay with our CTO/founder. It's the person who turns vision and market signal into a compounding plan the team executes. You're closer to a founding product partner than a traditional PM: someone who sets direction rather than receives it, and is expected to pressure-test the vision against the market rather than transcribe it into tickets. WHAT YOU'LL ACTUALLY DO - Own the long-term product roadmap, translating vision into a sequenced plan where each build deliberately compounds the next, and driving alignment on it across leadership and the team - Run continuous customer and market discovery, maintaining ongoing contact with users and the market, synthesizing what comes back, and feeding it into roadmap decisions as a standing input, not a one-off - Drive open product-architecture decisions to resolution — provenance, the public/private seam, version propagation across packs, consumer-facing vocabulary — from fuzzy to decided - Think through the in-the-weeds product architecture — the specific edge cases, like how access or permissions behave under a given condition — before engineering picks it up, so the details are already decided rather than…