• You'll join a small and friendly distributed team of engineers, designers and researchers who are designing, building, and testing new ways of doing collaborative science. We do most of our work in writing, across many time zones, and there are no managers: engineers pull their own work from a queue, and we judge progress by what researchers do with the tools rather than by targets. We are moving from asynchronous toward pair programming, short iterations and regular retrospectives.
• This role will place you in a central node of a product that is evolving with its researcher user base. We have extensive feedback from internal use as well as two years of user pilots with research labs across North America, more ideas than we can act on, a growing community of labs, and funding to do something with both. You'll shape the product strategy, working out with the founders where Discourse Graphs should go, what to prioritize, and how to get there.
• Some of the questions we are considering include whether the product stays a set of plugins in Obsidian or needs a standalone app now, how it will live in researchers’ existing tools such as agentic coding interfaces, and when we will extend our use cases to adjacent areas like publication overlays and institutional research roadmapping. We’ll follow where users’ interest is strongest, while making sure the work they depend on comes first.
• Much of the work is hands-on, since there is no product team under you. Week to week you'll talk with the researchers who use the tools, turn what you hear into one ordered queue of work together with the designer and developers, and show your ideas as working prototypes as often as you write them up. You’ll be able to rate priority based on user need and our product vision. Engineers choose their own work from that queue, so we won't ask you to assign tasks, run sprints or act as a Scrum Master.