Product Manager

Description

About the company

Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.

The company makes products self-driving (the company's site). It's the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously.

We've since shipped <u>more than a dozen products</u> (the company's site), including:

The company Desktop (the company's site), the only AI devtool that understands your product, not just your codebase.

<u>A built-in data warehouse</u> (the company's site), so users can query product and customer data together using custom SQL insights.

<u>the company AI</u> (the company's site), an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.

We are:

Product-led. More than 450,000 organizations have installed the company, mostly driven by word-of-mouth. We have intensely strong product-market fit.

<u>Default alive</u> (https://paulgraham.com/aord.html). Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.

We're set up for a long, ambitious journey.

We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and <u>being as weird as possible</u> (the company's site).

&nbsp;

Things we care about

Transparency: Everyone can read about our roadmap, how we pay (or even let go of) people, our strategy, and how we work, in our <u>public company handbook</u> (the company's site). Internally, we share revenue, notes and slides from board meetings, and fundraising plans, so everyone has the context they need to make good decisions.

Autonomy: We don’t tell anyone what to do. Everyone chooses what to work on next based on what's going to have the biggest impact on our customers, and what they find interesting and motivating to work on. <u>Engineers lead product teams</u> (the company's site) and <u>make product decisions</u> (the company's site). Teams are flexible and easy to change when needed.

Shipping fast: <u>Why not now?</u> (the company's site) We want to build a lot of products; we can't do that shipping at a normal pace. We've built the company around small teams – autonomous, highly-efficient groups of <u>cracked engineers</u> (the company's site) who can outship much larger companies because they own their products end-to-end.

Time for building: Nothing gets shipped in a meeting. We're a natively remote company. We default to async communication – PRs \> Issues \> Slack. Tuesdays and Thursdays are <u>meeting-free days</u> (the company's site), and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.

Ambition: We want to solve big problems. We strongly believe that aiming for the best possible upside, and sometimes missing, is better than never trying. We're optimistic about what's possible and our ability to get there.

Being weird: Weird means redesigning an already world-class website for the 5th time. It means shipping literally every product that relates to customer data. It means building an <u>objectively unnecessary developer toy</u> (the company's site) with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.

Product at the company

<u>Product management plays a slightly different role at the company</u> (the company's site) than at most other companies and is incredibly important. Instead of micro-managing engineers, PMs are responsible for research , data , and setting high-level context across the organization.<u>They work across multiple products</u> (the company's site) to determine how products are being used, what the competitive landscape is like, and how users are feeling about the company. Using the usual PM jargon we could say PMs at the company are very<u>discovery-focused and don’t engage in delivery</u> (https://www.svpg.com/discovery-vs-delivery/) almost at all.

Among other things, they:

Run <u>growth reviews</u> (the company's site) for products that have product-market-fit

Dive into data research projects to answer challenging questions without obvious answers

Organize <u>user interviews</u> (the company's site)

Provide just-in-time product feedback for new and existing features, following our principles of shipping and iterating quickly

Coach product engineers on <u>"how to do product</u> (the company's site)"

If you want to know more about our philosophy of building products, read our article<u>“Product Management is broken. Engineers can fix it.”</u> (the company's site)

What you will be doing:

You will be joining the company as a Product Manager, working with one of our <u>small engineering teams</u> (the company's site) (with the potential to cover more than one team/product after your onboarding period), with a heavy emphasis on analyzing data , talking to users and owning the commercial aspects of your product(s):

We have a<u>growth review</u> (the company's site) with every product every month. As the PM, you ensure we have the right metrics, dig into things that have changed, understand what users are doing, why they're churning, etc. You use the findings to figure out if we need to dig deeper into a trend or reprioritize what we're building.

Across our<u>10+</u> (the company's site) products (and counting!), we have thousands of paying customers and many more on the free tier. That’s a lot of users and a lot of data. Example questions you might be answering:

You keep an eye on the commercial side of things. Each of our products is competing with incumbents multiple times bigger both in revenue and employee size. You will lead the research into our competitors and the tooling landscape, and provide recommendations where we have the biggest untapped potential, whether it’s pricing, feature parity or even spinning out an adjacent product

Things you choose to pick up. This could be a data deep dive outside the scope of the repeating growth reviews. Or figuring out how to package and price a new product that we want to perform better in terms of usage or revenue. Or it could be rubber-ducking the engineers to help them figure out the UX for a new product concept. This is a highly autonomous role, and you’re expected to figure out where it makes the most sense to spend your time.

What you won’t be doing:

Backlog grooming (it always sounded gross anyway)

Deciding or approving what we build (though you’ll help surface the context needed to make good decisions)

Shielding developers from users (instead, you should aim to invite an engineer for every user interview you do)

Project management / writing gazillions of tickets, RFCs, or PRDs

Coding and shipping new features yourself (small PRs and hackathon contributions are of course encouraged!)

You’ll fit right in if:

You’ve been a technical founder or product engineer in a startup: We are explicitly looking for someone who has written code before and now wants to focus on the product and commercial side

You have strong product sense - meaning you can identify a product’s biggest selling points and weaknesses (both user experience and commercial) and turn them into actionable insights that inform your team’s product decisions

You’re familiar with business and product metrics (e.g. activation, retention, churn) and defining and tracking key product metrics. You don’t hesitate to write SQL (or another query language) to answer data questions

You’re very proactive/organized, so you don’t wait to be told what to do. Instead, you figure out what needs to happen, make it happen and keep multiple threads moving forward without letting things slip

You collaborate well as you default to transparency, share early, and seek feedback from the team and customers in an async-first world. Strong communication skills are the key to strong collaboration.

You have hands-on experience using observability products and understand how engineers use them to investigate, debug, and diagnose issues in production.

Nice-to-haves (We don’t expect you to tick all of these boxes, but at least 2-3 are a big plus):

You’ve worked on or PM’d an observability product before.

You have additional data modelling experience on top of writing queries.

You’ve worked on a developer tool or AI product before.

You’ve done a decent portion of interviewing users already. And looking at additional product management experience, you might have even worked with designers or engineers on new user experiences?

If you have a disability, please let us know if there's any way we can make the interview process better for you - we're happy to accommodate!

LI-DNI

Experience: 5+ years

Visa: US citizen/visa only