Product Operations Lead

koodos
koodos

Product, Operations

Posted on Aug 17, 2026

New York City · Full-time · In-person

Why join koodos labs?

koodos labs is building personal intelligence that works for the person it represents.

Our mission is to put personal intelligence within your control: to help people bring together the context they choose, understand and refine what Shelf learns on their behalf, and decide how that context can be used.

We built Shelf to power this vision. Millions of people choose to connect Shelf to services across their digital lives, and Shelf aggregates that activity on their behalf. Users and creators have already built hundreds of personal apps powered by that context.

You should join koodos labs for the people and our mission. We aspire to build the best team of the 2020s, a place where it’s good to be from.

Your mission

Be the operational backbone of the product, design, and engineering team.

Shelf is becoming a more complex system: connectors bring in user-authorized context, user representation makes it legible and editable, and an app platform lets people put that understanding to work. The team needs someone who can keep that shipping machine clear, coordinated, and moving quickly.

Your job is to create enough structure that Design can focus on craft, Engineering can focus on shipping, and Leadership can focus on the highest-leverage decisions.

This is a highly collaborative, facilitation-oriented role with substantial ownership. We expect it to grow into broader operations leadership as the company scales.

What you'll do

1. Run the product operating system

  • Run sprint planning across Product, Engineering, and Design so priorities, ownership, and capacity are clear.
  • Own the backlog as a living artifact: keep work scoped, sequenced, and understandable enough to be picked up cold.
  • Facilitate rituals and working sessions with clear agendas, named decisions, owners, and follow-through.
  • Own release coordination, QA readiness, launch checklists, release notes, and cross-team communication.
  • Be the person people can ask when they need to understand what is shipping, what is blocked, or what needs a decision.
  • 2. Stay one step ahead

  • Identify coordination failures, unclear ownership, missing decisions, and operational bottlenecks before they become expensive.
  • Know when a problem is genuinely unresolved and when the team is simply avoiding making a decision.
  • Simplify processes aggressively. We want less process with higher reliability, not more ceremony.
  • Build lightweight systems and automations that let a small team operate at much greater scale.
  • 3. Own support operations

  • Oversee our support operation and contractors, setting priorities, quality standards, and coverage.
  • Keep intake, routing, and resolution standards clean and consistent.
  • Translate recurring support signals into useful product and engineering inputs.
  • Identify automation opportunities that reduce manual work while improving the user experience.
  • 4. Help an AI-native team operate like one

  • Use AI aggressively to compress administrative work, synthesize context, maintain artifacts, and improve throughput.
  • Help the team develop better operating patterns as software development itself changes.
  • Make sure AI increases speed without producing low-quality artifacts, unclear thinking, or work that nobody truly owns.
  • Ideal Candidate

    Every job description is a wish list. If this role really excites you, please reach out even if your background looks a little different.

    You’re likely a good fit if you:

  • Are a heat-seeking missile for pain. You notice messy operating problems and feel compelled to fix them.
  • Thrive in the hairy middle. You can hold ambiguity without letting resolvable decisions linger.
  • Are warm, collaborative, low ego, and trusted by very different kinds of people.
  • Are genuinely energized by operational craft, but have no interest in process for process’s sake.
  • Are obsessive about execution and detail. Missing owners, broken links, unclear tickets, and dropped threads bother you.
  • Have several years of experience in a role requiring operational rigor across product, design, and engineering teams, such as product operations, program management, product management, technical project management, or adjacent work.
  • Understand how software gets built. You know what a useful ticket, QA pass, launch checklist, and release process look like.
  • Are extremely comfortable with AI tools and use them to multiply your output without outsourcing your judgment.
  • Can analyze recurring problems and build systems that remove them rather than repeatedly routing around them.
  • How we interview

    We aim to move fast and focus on simulating what it would actually be like to work together.

    Introduction: Context about Koodos, Shelf, and the role.

    First Call: A conversation with our CEO about your background, judgment, and the operating environments where you do your best work.

    Case Interview: A simulation based on a real cross-functional operating problem.

    Onsite: Meet the team and work through several realistic situations together.

    References: We’ll ask for 2–3 references. You’re welcome to reference check us too.

    How to apply

    Email team@koodos.com with your resume and a short description of an operational improvement you made that materially changed how a team worked.

    FAQs

    Where will I work?

    What is compensation?

    What tech stack do you use?

    Do you sponsor visas?