Senior Product Owner: Feedback Loops & AI Enablement

Salesforce, Inc.; Washington (District of Columbia); Hybrid; USD 173,000 - 260,000; Full time

Benefits offered by this job

Accommodations available

AI-assisted tools

Job summary

Salesforce, Inc. is seeking a Sr. Product Owner to lead the Feedback Loops initiative, bridging internal and external feedback across Salesforce clouds. You will translate insights into concrete input for product teams and influence prioritization with senior leaders.

The role blends technical analysis with stakeholder engagement, requiring Python/SQL fluency and the ability to read code and discuss epics, stories, and sprints. Expect a 75/25 split between analysis and hands-on coding.

Qualifications

• Engineering background with ability to read, analyze and discuss code, epics, stories and sprints.
• Fluency in Python and SQL for lightweight tooling and scripting.
• Experience influencing product stakeholders without direct authority.
• Strong written and verbal communication to translate technical detail into product decisions.

Responsibilities

• Own Feedback Loops, our internal product connecting internal and external customer feedback across Salesforce clouds.
• Synthesize feedback and translate into actionable input for product teams.
• Influence product prioritization by presenting synthesized feedback to leaders.
• Close the loop with field teams and customers, showing how feedback was addressed.
• Read and analyze code and technical specs to engage product and engineering teams credibly.

Skills

Python

SQL

Code reading

Stakeholder influence

Education

Engineering degree

Job description

Salesforce, Inc. is seeking a Sr. Product Owner to lead the Feedback Loops initiative, bridging internal and external feedback across Salesforce clouds. You will translate insights into concrete input for product teams and influence prioritization with senior leaders.

The role blends technical analysis with stakeholder engagement, requiring Python/SQL fluency and the ability to read code and discuss epics, stories, and sprints. Expect a 75/25 split between analysis and hands-on coding.