In PersonOn-site in Montreal; relocation is available for the right candidate.
ProductProduct Management
About the job
Requirements
Experience shipping real software, artificial intelligence, machine learning, backend, identity, or platform systems.
Ability to understand firmware constraints and model evaluations.
Ability to define product requirements, arbitrate tradeoffs, and ship products.
Ability to measure product performance with data.
Ability to translate between business, engineering, design, and science disciplines.
Ability to reason from first principles and make product decisions.
Ability to edit complex inputs into a clear, defensible product point of view.
Strong technical writing and product specification skills.
Experience with product management and roadmap tools including Jira, Trello, and Git.
Experience with technical collaboration tools and documentation.
Experience with product specification and workflow management.
Experience with data visualization and reporting tools.
Experience with artificial intelligence-assisted workflow and productivity tools.
Experience with Figma or user experience collaboration platforms.
Responsibilities
Own product specifications end to end by defining requirements, arbitrating tradeoffs, and shipping.
Build the measurement layer and use data to determine whether the product works.
Reduce proposed solutions to their irreducible core and protect it.
Translate between disciplines and produce a single defensible point of view.
Own the product layer where hardware meets software, including how the device, digital experience, and cloud behave as one system.
Architect solutions for software and data problems that present as hardware problems.
Product Manager — NO SAINT
Location: Montréal · On-site Relocation available for the right candidate
Base + meaningful equity
Read this part first
Most PM job descriptions are written by committee, so they read like one: a wall of "collaborate cross-functionally" and "drive alignment." We're not going to insult you with that. Here's what's true.
We build nicotine delivery systems that solve societal problems, but first drive consumer preference. Why? You can't make a difference without being relevant first. We're fast-growing- The Grocer's Top Product Launch of 2025- and we're scaling into new markets— which means solving product problems most consumer companies never have to. The product you'll own sits at the intersection of AI/ML, firmware, mobile, cloud, behavior and pattern assessment, UX and design, and it has to clear a bar higher than anyone has ever cleared before.
This is not just a roadmap-grooming job. This is a build-the-hard-thing job.
What you'll actually do
You are the connective tissue between business, several disciplines of engineering, design, and science. Not a messenger between them — the person who holds the whole system in their head and makes the calls nobody else is positioned to make.
You'll own the product layer where our hardware meets our software — how the device, the digital experience, and the cloud behave as one system. The hardest problems we have live here: they're software and data problems dressed as hardware problems, and solving them well is a genuine technical and architectural challenge, not a UX polish exercise. There are no off-the-shelf answers for what we need to build; you'll have to architect past the obvious.
You will:
Own specs end to end — define the requirements, arbitrate the tradeoffs, and ship.
Build the measurement layer: if we can't show it works with data, it doesn't work.
Make the hard reductions. Most of what gets proposed should be cut. Your job is to find the irreducible core and protect it.
Translate between disciplines that don't naturally speak the same language and produce a single defensible point of view from the mess.
Who you are
You come from software / AI. You've shipped real systems — backend, ML, identity, or platform. You can read a firmware constraint and a model eval with equal fluency and tell the engineer when they're wrong. This is non-negotiable; a PM from a non-technical background cannot do this job.
You run on first principles. You don't ask "what do competitors do." You ask "what is actually true, and what does that force us to build." You reason from the physics of the problem up, not from convention down.
You are ruthless about results. You measure. You cut. You'd rather ship one thing that decisively works than five that mostly do. Process is something you tolerate, not something you generate.
You're a product-minded editor. You take a sprawling, half-formed mess of inputs from multiple disciplines and produce a sharp, defensible point of view. You have taste, and you have the spine to act on it.
You write well. Clear writing is clear thinking. If your specs are muddy, your product will be too.
Technical Skills
Product management and roadmap tools (JIRA, TRELLO, GIT)
Technical collaboration tools and documentation
Product specification and workflow management
Data visualization and reporting tools
AI-assisted workflow and productivity tools
Figma or UX collaboration platforms
Along with your application, please share the following with us:
One system you shipped that you're proud of — and the one decision in it you'd defend against anyone. One to two paragraphs only.
One feature, product, or process you killed — and why killing it was the right call. We care more about this than #1.
A teardown of a popular product (soft or hard) you think is badly designed — what's broken, and what you'd do instead. Shorter = better.