Cracked Product Manager New York City

YakLabs is building a desktop AI application that turns knowledge workers into AI power users, without docs, API keys, or knowing what to ask for. One surface for agentic AI work: proactive, personalized, progressively powerful. The gap between AI power users and everyone else isn’t talent, it’s setup. We close it. The team: Alex Goddijn spent four years at Palantir, then founded an agent harness company that was acquired by Poolside AI. Seb Goddijn led internal AI at Ramp. We’re building Kay so that kind of leverage isn’t limited to companies with their own internal AI team. We have funding. Product and design work in person in New York City, and some engineering roles are remote. Small team, high intensity, no passengers. The job You talk to customers, decide what matters, and then build it yourself, end to end. Kay has a plugin SDK that lets you build complete applications on top of the product: the integrations, the workflows, the interface, and the skills that make it useful for one kind of work. Your job is to turn what you hear from customers into those applications, built so they sell to the next customer and the one after, not just the one who asked. You also ship horizontal features in the core product. Either way, you ship full features on your own, without handing a spec to engineering or waiting on design. Problems you’ll work on These are examples, not lanes. You will move between them, while taking real ownership of the ones that match your interests. From conversation to product: A customer describes a painful workflow in a meeting. How do you get from that to a working application they are using the next week, and how do you tell whether the pain is theirs alone or something every customer like them has? Repeatable, not bespoke: A one-off build wins one customer. A product wins a segment. How do you shape an application so it works across many companies with different tools, data, and habits, and so it helps us close the next deal faster? Knowing what to build next: Customers, investors, and our own team will ask for more than anyone can ship. How do you decide with evidence, and say no well? Time to first value: Someone installs an application and connects their accounts. Within their first session they should get something done they couldn’t do before. What does that first hour look like, and how do you know it worked? What you’ll do Work deeply with customers and design partners, often on site. Watch how they work, not only what they say. Build end-to-end applications on the plugin SDK, from the first prototype to something customers pay for. Ship horizontal features in the core product when what you learn from customers points there. Own your areas from problem to shipped to measured. Define success, instrument it, and report on it honestly. Package what you build so it sells: a clear story, a demo that lands, and a setup the next customer can get through without you. Who you are You ship. You’ve built and launched real software on your own, and you don’t need an engineer or a designer to get a feature out the door. You build with coding agents every day, and you use AI tools more heavily than anyone you work with. You’re great with customers. You can run a discovery conversation, hear the problem under the request, and disagree with an executive without losing them. You have taste. You can tell good product from almost-good product and explain the difference. You think commercially. You care whether what you build helps us sell, and you can explain why it will. You write clearly and briefly. Bonus You’ve been a founder, a founding engineer, or a forward deployed engineer. You’ve built and sold software to enterprises, especially in financial services. You’ve built on a plugin or app platform (Slack, Salesforce, Shopify, Figma, or similar). Who we look for These apply to every role at YakLabs. First principles thinking. We’re building in a category that’s being defined in real time. Best practices don’t exist yet. You reason from the problem, not from what everyone else is doing. High agency and ownership. You don’t wait to be told what to do. You see what needs to happen, you go make it happen, and you own the outcome. At a team this size, there’s nobody to delegate to. Deep curiosity about AI tooling. Not just using ChatGPT or Copilot: you’re experimenting, writing your own tools, trying new agent frameworks the week they drop, forming opinions about what works and what doesn’t. The people building this product should be the most demanding users of the category. You build compounding leverage. In the era of building with agents, one person doesn’t just ship one person’s work, they build the systems that build the product. Every person is amplified, and with that amplification comes the responsibility to build things that compound: skills, automations, agent workflows that make the next thing faster. This is a new way of working, and you’re excited to develop the skillset it demands. The deal Early team, meaningful equity. In person in New York City for product and design roles. Some engineering roles are remote, and each posting lists its location. You’ll shape the product, the culture, and the company. This is a founding-team role. How we hire YakLabs is an equal opportunity employer. We consider every application withoutregard to race, color, religion, sex, gender identity, sexual orientation,national origin, age, disability, veteran status, or any other protectedcharacteristic. If you need an accommodation at any point in the process, email View email address on click.appcast.io and we will work it out with you. A person, not a machine,reads every application. #J-18808-Ljbffr Meetkay