Director of Product Management, Developer Experience

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Salesforce", "The Role", "In This Position, You Will", "What We’re Looking For", "Preferred Qualifications", "Unleash Your Potential", "Accommodations", "Posting Statement". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings. We have: - About Salesforce: description of company. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Salesforce" which is about company. Could treat as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. We need to decide which sections we have content for. We have role description: "The Role At Salesforce, the Developer Experience & Observability organization...". That's role description. Could map to "About the role". Also responsibilities: "In This Position, You Will ..." list of duties. That's responsibilities. Requirements: "What We’re Looking For" includes required qualifications. That's requirements. Preferred Qualifications: separate. Skills: maybe not explicit; we could infer from requirements but better not to create if not explicit. Benefits: there is a paragraph about benefits later: "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Also earlier "Unleash Your Potential" mentions benefits and resources. So we have benefits content. Pay: there is salary range: "The typical base salary range for this position is $197,300 - $313,700 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $237,700 - $344,700 annually." So we have pay. Schedule: not mentioned. So we should not include Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: accommodations, EEO, etc. Remove "Accommodations", "Posting Statement", "Unleash Your Potential"? Actually "Unleash Your Potential" is marketing fluff but maybe we can keep as part of benefits? It's not specific benefits. Might be considered boilerplate? It's somewhat generic but mentions AI agents accelerate impact. Could be considered fluff. Safer to omit unless it contains specific benefits. It says "Our benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact so you can do your best." That's vague. Better to omit. We need to preserve all substantive information. So we need to include the company description? Might be considered "About Salesforce" which is not required heading but could be part of "About the role"? The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. If we have content that doesn't fit, we could still include as

without heading? Probably we should include as

under appropriate heading or as a generic

if no heading fits. But they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Safer to stick to those. Thus we need sections: - About the role: include description of role and maybe company overview? Could combine "About Salesforce" and "The Role". We'll put company overview as part of About the role. - Responsibilities: the bullet list from "In This Position, You Will". We'll turn each sentence into

. - Requirements: the bullet list from "What We’re Looking For". We'll turn each bullet into

. - Qualifications: maybe "Preferred Qualifications". We'll treat as Qualifications? Actually Qualifications heading could encompass both required and preferred. But we have separate sections for Requirements and Qualifications. We'll put required under Requirements, preferred under Qualifications. - Skills: not explicit; we could skip if no specific skills listed. Could infer from requirements but better not to create thin section. So omit Skills. - Benefits: list of benefits. - Pay: salary ranges. We must not include sections with filler like "commensurate with experience". We have concrete numbers. Now produce HTML fragment. Structure:

About the role

... company description and role overview ...

Responsibilities

• Set the product vision and strategy: Define a compelling direction, sequenced roadmap, and investment priorities
• Translate strategy into clear requirements and iterative delivery. Make deliberate choices about what to build, buy, improve, or retire, balancing developer needs, technical debt, security, cost, and long-term business goals.
• Champion the voice of the developer: Build trusted customer relationships through interviews, advisory boards, surveys, workflow research, and product telemetry. Uncover the root causes of developer friction, translate those insights into focused product opportunities, validate solutions, and close the feedback loop.
• Drive AI-native developer productivity: Identify opportunities for AI coding tools and agents across the SDLC. Prototype and evaluate emerging tools and workflows, considering quality, developer trust, security, human oversight, and cost. Turn the highest-value experiments into reliable products used in everyday development.
• Measure and improve outcomes: Establish baselines and success measures for developer experience, delivery performance, adoption, and AI effectiveness. Combine DORA delivery metrics and SPACE-informed measures with build/test feedback times, CI reliability, developer sentiment and satisfaction measures such as NPS/CSAT, and qualitative research. Use this evidence to identify bottlenecks, prioritize investments, and validate improvements in speed, quality, and satisfaction.
• Influence & collaborate at scale: Build strong, trusted partnerships across partner teams and drive influence at all levels of the organization. Resolve competing priorities, navigate technical tradeoffs, and communicate clear recommendations to engineers and executives.
• Prioritize high-impact investments: Prioritize the product backlog while balancing developer feedback, technical debt, security requirements, and long-term business goals to maximize platform value.

Requirements

• Product leadership and judgement: 6-10+ years of technical product management experience (or equivalent) with demonstrated success owning large-scale developer platforms, infrastructure platforms, developer tools or DevOps products.
• Technical architecture & SDLC fluency: Strong understanding of modern software development practices and developer workflows across source control, build systems, testing, and CI/CD. Experience with complex development environments such as large monolithic applications, monorepos, and/or distributed cloud-native microservices.
• AI-native, hands-on approach: You use AI to improve how you work. You can build prototypes, automations, and agents using tools such as Claude Code, Cursor, Codex, or equivalents. Examples include Slack workflows that capture developer feedback, surface recurring issues, and track follow-through.
• Customer obsession and analytical rigor: A track record of combining customer research, product data, and experimentation to understand technical users, make better product decisions, and deliver experiences developers adopt and value.
• Exceptional communication and influence: The ability to turn complex product and technical tradeoffs into clear written narratives, roadmaps, and executive recommendations while building trust with engineering teams.
• Enterprise and trust mindset: Experience building products where scale, security, privacy, compliance, reliability, and performance are fundamental requirements, with an understanding of the additional evaluation and governance considerations for AI tools.
• Thriving in ambiguity: Natural comfort with ambiguity and the ability to bring clarity, focus, and alignment across large, matrixed organizations and in a fast-evolving landscape.
• Education: BS or MS in Computer Science, Software Engineering, or a related discipline (or equivalent practical experience).

Qualifications

• Previous experience as a software engineer, engineering leader, or in another technical role.
• Prior ownership of an internal developer platform (IDP), service catalog, developer portal, or similar large-scale developer-facing system.
• Experience evaluating or deploying AI-assisted software development tools and cloud-based coding agents at scale.
• Strong background in developer advocacy or developer relations.

Benefits

• Time off programs
• Medical, dental, vision
• Mental health support
• Paid parental leave
• Life and disability insurance
• 401(k)
• Employee stock purchasing program

Pay

The typical base salary range for this position is $197,300 - $313,700 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $237,700 - $344,700 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable.

We should not include any extra text like "About Salesforce" separate. We incorporated company description in About the role paragraph. Let's craft About the role paragraph: "Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce. At Salesforce, the Developer Experience & Observability organization is on a mission to deliver a world-class development environment for more than 15,000+ internal engineers. We build the integrated products, platforms, and tooling that engineers – and an increasing number of AI agents – use to take code from idea to production. Our scope spans the full software development lifecycle (SDLC), from local and cloud-based development environments through source control, build systems, testing, code review, CI/CD, deployment and observability. We are fundamentally reimagining the SDLC for the agentic era. Our ambition goes beyond faster code generation: we are redesigning how engineers and AI agents build software together by removing toil, shortening feedback loops, and helping teams ship high-quality software with confidence. This means turning emerging AI capabilities into trusted developer experiences that work at enterprise scale. We are looking for a Director of Product Management to join our DX Product Management team. In this role, you will own the strategy, roadmap, and measurable outcomes for key developer products and platforms that sit in the path to production for all Salesforce engineers. This is a high-impact individual contributor role with broad organizational influence. You will partner closely with engineering and executive leadership, champion developers as customers, and turn their most important problems into products they adopt and value