Osmo Software Technical Product Manager at Osmo to independently scope, negotiate, and deliver internal tooling projects that improve workflows. Collaborate closely with engineering to drive product delivery under ambiguity.
Responsibilities
We're hiring a Technical Product Manager to be our product’s right hand as Osmo scales its Software and AI organization. This is a hands-on product role, not a program management role — you'll own scoping, requirements, and delivery negotiation directly, working independently from day one.
Your first mandate: Osmo's internal workflows are largely manual today, and information doesn't always flow through our systems the way it should. You'll identify the 3-5 tools that would drive 80% of the impact, embed with the relevant teams to master the problem, and come out with clear requirements that get built. From there, expect to move across workstreams as priorities shift, applying the same structural skills to a new domain. You'll work closely with engineering throughout, and you'll need to hold your own there: when an estimate doesn't add up, you push back with specifics, ask for the breakdown, and know how to simplify a requirement to get something shipped faster. This role takes real tenacity to drive scope and delivery under ambiguity, and real kindness in how you ask a stretched engineering team for more.
Scope With Rigor — Independently scope projects end to end: understand the business value and customer need, then write clear, complete requirements that inform what engineering builds.
Negotiate Scope and Estimates — When an engineering estimate doesn't match reality, push back with tenacity: ask for the breakdown, identify what's actually driving the cost, and simplify or revise the requirement to get to a faster, leaner build.
Find the 80% — Scope Osmo's highest-value internal tooling opportunities: identify the 3-5 tools that would drive the majority of workflow impact, then sequence and prioritize the build.
Embed and Master — Rapidly insert yourself into a workstream, understand it deeply, and come out with the requirements and plan to fix what's broken.
Partner Directly With Engineering — Work hand-in-hand with the CTO’s team to get scoped work built and delivered against committed dates.
Operate Without a Script — Take high-level direction into an ambiguous space and bring back clarity, milestones, and a plan — with the curiosity to figure out what's actually needed rather than waiting to be told.
Bring Structure Without Bureaucracy — Sequence and manage ambiguous initiatives without adding process for its own sake.
Pivot With the Business — Move fluidly across workstreams as Osmo's priorities shift, applying the same core PM skill set to new problems.
Use AI as a Working Tool — Build and use AI-powered tools and workflows in your own work — for requirements drafting, dependency tracking, and stakeholder communication.
Qualification
Direct Engineering CollaborationA ClearBachelor's degree or higherWays to Stand OutYou've Operated at a Small
Required
A Mid-Senior Generalist — You work independently and bring PM best practices without needing to be trained on the fundamentals. You're a generalist, not a specialist: your skills are fungible, and you're comfortable being reassigned to a completely different problem space.
Direct Engineering Collaboration, Non-Negotiable — You have worked hands-on with engineering teams in a prior role. You know how to sit across from an engineering lead, question an estimate, and land on a scope that actually reflects the work.
A Real Requirements Writer — Writing requirements documents has been a core, sustained part of at least one prior role — not a one-off exercise.
Comfortable in Ambiguity — You can take a loosely defined problem and a high-level directive and figure out the rest. You don't need a detailed plan handed to you.
A Clear, Confident Communicator — You can bridge business needs and engineering constraints, and you're comfortable pushing back on senior stakeholders, including leadership, when timelines, scope, or resources don't add up.
An AI-Native Operator — Fluency with modern AI tools (LLMs, automation platforms, workflow builders), with a track record of using them in your own work.
Bachelor's degree or higher, or equivalent experience.
Ways to Stand Out:
You thrive in ambiguity and build your way out of it — We move fast and our pioneering in our space. We build what no one has ever imagined before.
You've Worked Alongside Deep Technical or Scientific Teams — Comfortable partnering with ML, hardware, or R&D-heavy functions even though this is not a technical specialist role.
You've Pivoted Across Domains — You've moved across genuinely different product areas within the same company and ramped quickly each time.
You've Operated at a Small, Fast-Moving Company — Where you had to build the process yourself rather than inherit one.
