Jobs · Marketing

Director, Product Management (Remote)

ExecutivePlacements.com · Burlingame, CA · 3 wk ago
RemoteRemoteMarketing$230k–$295k/yrFull-time
We need to output HTML fragment with sections: h3 for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the role? There's a paragraph about mission, etc. That could be "About the role" or maybe "About the role" is not explicitly heading but we can create. The content includes mission, description of Lumi, etc. That's substantive. Responsibilities: list of bullet points. Requirements: list of bullet points. Qualifications? The posting includes "Bonus Points" which could be considered qualifications or skills. Could treat as "Qualifications" or "Skills". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have Benefits: list of benefits. Pay: compensation range given. Schedule: not mentioned. So we should not include Schedule. Qualifications vs Skills: The posting has "Requirements" (experience etc.) and then "Bonus Points" (extra desirable experience). Could map Bonus Points to "Qualifications" or "Skills". Since they are extra qualifications, we could put under "Qualifications". Or we could have both Requirements and Qualifications sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Bonus Points into Requirements? But they are distinct: Requirements are mandatory, Bonus Points are nice-to-have. Could still be under Requirements with sub-bullets? But we need to follow instruction: Use
  • for any list of duties/requirements/benefits. So we can have one Requirements section that includes both mandatory and bonus points? Might be okay but we risk losing nuance. Better to have Requirements (mandatory) and Qualifications (bonus). That's two sections, still okay. Skills: Not explicitly listed; maybe we could treat technical fluency etc as skills but they are in Requirements. So we may not need separate Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check each for real specific content. About the role: we have mission paragraph, description of Lumi, role description. That's substantive. Responsibilities: bullet list. Requirements: bullet list of mandatory items. Qualifications: bullet list of bonus points. Benefits: bullet list. Pay: compensation range. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO, scam warning, privacy policy, etc. Also remove duplicated lines, navigation, cookie etc. The posting includes some duplicated lines like "Job Description Job Description". We'll ignore. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe slight rephrase? Must preserve info, not summarizing away detail). We'll copy the bullet points verbatim. Let's extract sections. About the role: The initial paragraph before "The Role": "Job Description Job Description At Imply, our mission is to empower people and organizations to achieve more with their data. We believe that better insights lead to better decisions, and that the right technology can remove barriers, spark innovation and create lasting impact. Building on the success of our database business, we have created the industry's first observability warehouse, Imply Lumi. Built by the creators of Apache Druid, Lumi lets organizations store more data, support more use cases and spend less for observability. Imply Lumi is a high-performance, cost-efficient data layer built to decouple existing observability tools with zero disruption. In this role, you will help redefine what is possible with observability and security data. As the leader of our Product Team you will play a critical role in bringing Imply Lumi to life. Lumi delivers lightning fast queries, significant cost savings and seamless integration with leading observability technologies while giving customers the freedom to innovate without vendor lock-in. You will partner directly with our teams who are innovating and building this first-in-class technology that allows our customers to unlock new levels of speed, scale and value from their data. Backed by leading investors including a16z and Bessemer Venture Partners, Imply is on a fast growth trajectory, transforming how organizations manage and gain insights from their observability and security data. Our customers, including Pepsi, Reddit, Roblox, Salesforce, and others, rely on our technology to power faster decisions, reduce costs, and unlock new possibilities. Come join a team of innovators and problem-solvers who are reshaping the future of data!" That's a lot. We'll keep as

    . Then "The Role" heading: but we should not repeat job title as heading; "The Role" is a heading but we can treat as "About the role"? Actually we already have About the role. The "The Role" section includes: "We are hiring a Director of Product Management to lead our team of product managers, shaping the direction and vision of Imply Lumi. This role will own strategy and execution: defining how customers ingest, store, query, and act on massive volumes of machine data in the most performant, scalable, and cost-effective way possible. You'll work directly with our co-founders and CPO to set product direction, and partner closely with engineering, design, and go-to-market teams to define and execute the Lumi roadmap. This is a hands-on role, and you should expect to go deep on customer problems, write specs, and drive delivery alongside your team, not just manage up or coordinate. As a people leader, you'll manage and grow a team of 3 product managers, setting clear direction, coaching for growth, and creating the conditions for them to do their best work. We care as much about the success and development of the people on this team as we do about shipping great product. We are looking for someone who combines deep technical curiosity, strong execution skills, and a collaborative mindset. At Imply, we believe diverse backgrounds lead to stronger teams, and we welcome product managers who have taken varied paths to get here." That's also substantive; could be part of About the role. But we already have About the role covering mission etc. Could merge. However instruction: Prefer a few substantive sections over many thin ones. So we could combine the initial mission and The Role into About the role section. That would be one section with multiple paragraphs. That's fine. Thus About the role will contain two paragraphs: first mission/intro, second the role details. Now Responsibilities: bullet list after "Responsibilities". Let's extract: - Define and evolve the roadmap and own the success of Imply Lumi - Meet regularly with customers and prospects to understand their needs - Work alongside founders and our CPO to align on product vision and roadmap - Drive the launch of new products, capabilities, and features - Work across multiple teams to deliver large complex features - Become the face of your product area both for internal and external stakeholders Check if any duplicates: fine. Now Requirements: bullet list after "Requirements". Let's extract: - 10+ years of product management experience in B2B software, with a focus on infrastructure, observability, security, or data platforms - Experience working with complex distributed systems or backend services for data ingestion, storage, and access - Strong technical fluency—you can navigate architecture discussions with engineers and evaluate trade-offs in scalability, latency, and cost - Proven track record of taking technically complex features to market, with high customer impact and adoption - Clear and concise communication skills across technical and non-technical audiences - Passion for customer problems, curiosity to dig deep into use cases, and a bias for action - Experience as a people manager of product managers - Project management and excellent communication skills; ability to present at the CxO level - Bachelor's Degree in Computer Science, Engineering or similar; MBA is a plus Now Qualifications (Bonus Points): bullet list after "Bonus Points". Extract: - Experience working on observability or SIEM platforms such as Splunk, Datadog, New Relic - Familiarity with open-source technologies such as OpenTelemetry, Fluent Bit, OCSF - Exposure to Apache Druid, Kafka, or other modern data infrastructure stacks - Background in data engineering or database management Now Benefits: bullet list after "What We Offer". Extract: - Medical, Dental and Vision Benefits (employee premiums 100% paid by Imply) - Fertility Coverage - Integrated with our medical insurance - Dependent Care FSA - Mental Health Support via Betterhelp - Life and AD&D Insurance - 401(k) Program - Unlimited Paid Time Off - USA Only - Wellness Stipend - Home Office Equipment Reimbursement - Pre-Tax Commuter Benefits - Pet Insurance Now Pay: line: "Individual compensation will be determined based on the candidate's experience and qualifications aligned with Imply's internal levelings guidelines and benchmarks. The below range encompasses roles with on target earnings. This role is also eligible to participate in Imply's equity plan subject to the terms of the applicable plans and policies. Compensation: $230,000 - $295,000" We need to keep that info. Could be a

    with that text. Not a list. Now we must not include Schedule. Now ensure we don't include boilerplate: EEO, scam warning, privacy policy, etc. Remove those paragraphs. Now output HTML fragment: use

    for each section heading. Use
    • for lists. Use

      for prose. We must not include or . Just the fragment. Let's construct:

      About the role

      At Imply, our mission is to empower people and organizations to achieve more with their data. We believe that better insights lead to better decisions, and that the right technology can remove barriers, spark innovation and create lasting impact. Building on the success of our database business, we have created the industry's first observability warehouse, Imply Lumi. Built by the creators of Apache Druid, Lumi lets organizations store more data, support more use cases and spend less for observability. Imply Lumi is a high-performance, cost-efficient data layer built to decouple existing observability tools with zero disruption. In this role, you will help redefine what is possible with observability and security data. As the leader of our Product Team you will play a critical role in bringing Imply Lumi to life. Lumi delivers lightning fast queries, significant cost savings and seamless integration with leading observability technologies while giving customers the freedom to innovate without vendor lock-in. You will partner directly with our teams who are innovating and building this first-in-class technology that allows our customers to unlock new levels of speed, scale and value from their data. Backed by leading investors including a16z and Bessemer Venture Partners, Imply is on a fast growth trajectory, transforming how organizations manage and gain insights from their observability and security data. Our customers, including Pepsi, Reddit, Roblox, Salesforce, and others, rely on our technology to power faster decisions, reduce costs, and unlock new possibilities. Come join a team of innovators and problem-solvers who are reshaping the future of data!

      We are hiring a Director of Product Management to lead our team of product managers, shaping the direction and vision of Imply Lumi. This role will own strategy and execution: defining how customers ingest, store, query, and act on massive volumes of machine data in the most performant, scalable, and cost-effective way possible. You'll work directly with our co-founders and CPO to set product direction, and partner closely with engineering, design, and go-to-market teams to define and execute the Lumi roadmap. This is a hands-on role, and you should expect to go deep on customer problems, write specs, and drive delivery alongside your team, not just manage up or coordinate. As a people leader, you'll manage and grow a team of 3 product managers, setting clear direction, coaching for growth, and creating the conditions for them to do their

Similar jobs