Responsibilities

• Develop deep knowledge and empathy for users needs in the areas they tackle. This involves reviewing existing issues, tickets, docs, engaging in lots of interviews and evaluating quantitative data.
• Understand the underlying mechanics of the product at a technical level. You don’t need to read/write code, but need to have the curiosity and ability to over time understand how things work and develop instincts for what’s easy/hard.
• Develop strategies for solving clusters of users needs in thoughtful ways, ultimately delivering product docs which frame needs in actionable ways for designers and engineers. This is really important.
• Steward projects forward, helping keep focus, momentum, and continuously re-evaluating scope, with flexibility and appreciation for technical constraints and UX considerations.
• Follow-up on the outcomes of projects you ship, quantitatively and qualitatively.
• Collaborate with the rest of the team, consistently seeking and providing feedback, as well as pitching ideas for how to advance the product.
• Responsibilities don’t include: managing people, herding cats, writing code, making mocks.

About you

• A thorough thinker, able to be both diligent with details but systematic to see the big picture.
• Appreciative of clean but powerful user experiences (and the hard work they require).
• Able to keep a vision in mind, but break the path to it into small, doable, valuable steps.
• Bearer of strong product sense and good taste. Yes, I said it: good taste. To make a product users can love, it has to be lovable in the first place, and that requires knowing what not only solves a problem but is pleasant to use.
• Excited to work asynchronously in a global team, and with the written communication chops to do it effectively.
• More interested in the Product than the Management part of Product Management.
• While our team is globally distributed, this role involves enough synchronous interactions with team members in the US West Coast. So don’t accept applicants farther East than UTC+3. This restriction doesn’t necessarily apply to other roles at Metabase, but is non-negotiable for PMs.

Skills and experience

• Must have enough of a technical background. Preference is from data analysis, data engineering, or software engineering with experience with databases. PMing these things for a long while can also work. We’re not set up to have people learn the basics of data stacks on the job and screen for it early in the process.
• At least 4 years of experience in a product management role, making software in-house, having been through a few cycles of discovery, execution and iteration. We’re not yet set up to simultaneously train a junior PM and onboard them to the complexities of Metabase. In terms of responsibilities and the level of autonomy we expect from our PMs, this is a mid-to-senior PM role, and IC PMs on our team previously held GPM, Director and VP titles.
• Depending on the role you’re for which you’re a good match, experience working on a platform team and thinking through APIs may be needed, but we’ll get there later.
• Driven and able to help others continuously deliver work through influence, not authority.
• Skills you don’t need: up-to-date coding skills, customer management, horse whispering.