Principal Product Manager, DHI

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for any list of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - About Docker (company description) - The Products Team at Docker is looking for a Principal Product Manager... (role description) - Responsibilities (list) - Qualifications (list) - What To Expect (First 30 days, First 90 days, One Year Outlook) - Docker does not offer visa sponsorship for this role - Compensation & Equity (United States: $280,000 – $300,000 + equity) - Posting Information (Open vacancy, AI in hiring, Interview recordings) - Perks & Benefits (list of benefits) - Equal opportunity employer statement (boilerplate - should remove) I need to structure this into appropriate sections. The rules say to use

  for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But I should only include sections that have real content. Let me map the content: 1. "About the role" or "About Docker" - there's company description and role overview. I'll combine into an "About the role" section with prose. 2. "Responsibilities" - there's a list of responsibilities. 3. "Qualifications" - there's a list of qualifications. 4. "What to Expect" - this is a timeline of expectations (30 days, 90 days, one year). Could be a section. 5. "Compensation" - there's specific pay range. 6. "Benefits" - there's a list of perks & benefits. 7. "Visa Sponsorship" - mention that they don't offer visa sponsorship. Could be a small note. 8. "Posting Information" - minor metadata, could fold into a short

  or drop. I should remove the EEO boilerplate at the end. Now, I need to output HTML fragment with

  headings and

  • for lists,

    for prose. Let me draft:

    About the role

    Docker has been one of the most loved brands in developer tooling, trusted by more than 20 million monthly users and over 20 billion container image pulls. From solo founders to the world's largest companies, developers rely on Docker to build, share, and run their applications across our suite of products including Docker Desktop, Docker Hub, and Docker Scout. We are a globally distributed, remote-first team building the tools that define how software gets built and delivered. As AI agents redefine software development, Docker is at the center of that shift, providing the sandboxed environments, verified images, and secure infrastructure that make autonomous workflows trustworthy by default.

    The Products Team at Docker is looking for a Principal Product Manager for our core Sandbox platform. You will own and drive an investment and product area from high-level concept design to delivery and operation. You will help shape the future of a key area of Docker. You will work closely with developers inside and outside of Docker, our customers, as well as our partners to expand our open ecosystem offering and provide value. As the company and ecosystem grows, you will help to foster teams eager to continuously build, measure, and learn. To thrive in this role, you'll need experience working with developers and a technical knowledge of developer tools. You'll need to know how to work with the developer community and understand the lifecycle of software development, the software supply chain and how AI agents are safely orchestrated and deployed with sandboxes. You'll need a relentless drive to try new things, and an eye for detail. Your long-term success will depend on your ability to own the product roadmap and collaborate with the developer community, and scale our services. Most importantly, you'll need to be okay with taking ownership of big objectives with big goals, working with a cross-functional team, and maintaining a bias for action.

    Responsibilities

    • You own a product area, the long-term vision, the roadmap, the revenue, and the results.
    • You believe in and can articulate succinctly, our customers and their pain points. You empathize and understand the world they live in and the constraints they work through.
    • You will engage deeply with developers and find amazing solutions that solve today's problems while optimizing for tomorrow's vision.
    • You enjoy building products that are easy to adopt and use. You have a keen design sensibility, and you are always looking for ways to improve the usability of your products.
    • You are comfortable with ambiguity and will guide product definition, feature prioritization, and scope, in concert with cross functional teams.
    • You're a fan of iterative development, working with our customers as well as cross-functional teams to hypothesize, measure impact, and learn from previous releases to iterate on future roadmap plans.

    Qualifications

    • You have deep empathy for the needs of developers and are obsessed with talking to your users.
    • You have created and deployed AI agents at scale and dealt with all the challenges and pain points of such tasks.
    • You are comfortable interacting with a command-line interface.
    • You have experience building B2B, SaaS or have a background in Public Cloud.
    • You have experience working with tools in the software supply chain and/or software security.
    • You can break down complex technical problems into small, release-able, user valuable features.
    • You can explain complex ideas simply and communicate across diverse stakeholders.
    • You have effective written, verbal, and visual communication skills.
    • You can analyze data, both qualitative and quantitative, to inform decision making.
    • You have a collaborative approach and ability to work with fast moving, distributed, cross-functional teams.
    • You have experience running products at various stages of maturity, from legacy to greenfield.
    • You are a doer as well as a strategist. We are small and need all hands on deck.

    What to Expect

    First 30 days

    • Get to know Docker! Vision, mission, values
    • Understand the team and business unit's mission
    • Meet the team along with peers across the business unit and company
    • Work closely with designers, researchers and engineers to get to know our user's needs and current pain points.
    • Work with your Manager and team to review and create quarterly goals
    • Understand your product's roadmap and what data is available to make data driven decisions

    First 90 days

    • Understand the company's and business unit's product vision and how it relates to your team's objectives
    • Provide clarity of product vision to your team and how your team contributes to the overall success of the company and business unit
    • Develop deep understanding of our developers and customers and why they love Docker
    • Shape your team roadmap and vision in close collaboration with design and engineering peers.
    • Lead the definition of the team OKRs for the quarter and provide progress reports

    One Year Outlook

    • Lead product initiatives across cross-functional teams to create value for our users
    • Drive the long term direction of your product including contributions to ARR

    Compensation

    United States: $280,000 – $300,000 + equity

    Benefits

    • Remote-first by design – Work from your home, with offices in Seattle and Paris for connection and collaboration.
    • Flexibility that fits your life – We trust you to manage your schedule while delivering great work.
    • Time to recharge – Generous PTO, designated quarterly Whaleness Days, and a designated end-of-year Whaleness break.
    • Home office support – Set up your workspace for comfort and success.
    • Technology stipend – Equivalent to US$100 net per month to help support your work.
    • Learning & development – Annual stipend for conferences, courses, certifications, and continued learning.
    • Parental leave – 16 weeks of paid parental leave after six months of employment.
    • Equity for all full-time employees – Share in Docker's long-term success as we continue to grow.
    • Comprehensive benefits – Medical, retirement, and paid holidays vary by country.
    • Docker swag – Because representing the whale never gets old.

    Docker does not offer visa sponsorship for this role.

    Posting Information: This posting is for an existing open role. Docker may use AI-assisted tools during our recruiting process. Candidates will be invited to opt in to interview recordings to support interviewer calibration and consistent evaluations. Recordings are optional and require explicit consent.

    But wait: The rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." The "Posting Information" is minor metadata, so I'll fold into a short

    . Also, the EEO statement is boilerplate, remove. Also, the rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I used

    for subsections under "What to Expect". That's okay? The rule says use

    for section headings, but doesn't forbid

    for subsections. However, to keep it simple, maybe I should keep all headings as

    and use prose for subsections? But the "What to Expect" has three distinct timeframes. Could make them

    as well? But they are sub-sections. The rule says "use

    for section headings". It doesn't say you can't use other heading levels. But to be safe, I'll use

    for main sections only, and for subsections maybe use or just list them as separate lists with bold labels? However, the example includes "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule" as examples of section headings. "What to Expect" is not in that list, but it's a substantive section. I'll keep it as

    and then use

    for the timeframes? The rule doesn't explicitly forbid

    . But the instruction says "use

    for section