Product Owner
- Discuss this with your agent
- Open in Claude
- Open in ChatGPT
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Role details
Tech stack
Requirements
Do you have experience in Technical documentation?, Based on the job description provided, here are the top 3 absolute “must-haves” required to be successful in this role: 1. Ownership of Client Experience (CX) Data Strategy & Architecture The primary focus of this role (75% of the overall description) is managing the technical strategy and implementation for Client Experience data products. The ideal candidate must have a dedicated background in Client Experience (CX) and understand how to manage both client feedback survey data and non-survey data ecosystems. 2. Deep Data Governance & “Data Dependency” Ecosystem Expertise A massive technical responsibility for this position is building, leading, and monitoring the division’s “Data Dependency” program. The candidate must possess advanced technical knowledge in: * Data Lineage and Data Architecture * Metadata Documentation and Technical Process Maps * Implementing monitoring capabilities and alert functionalities across data products 3. Financial Industry Background with Advanced Analytics (SQL) To ensure that senior leadership metrics hit strict data quality standards, the candidate must come from a Financial Industry background. They need to be highly proficient in SQL to manage and optimize senior leadership CX metrics code, alongside a strong command of analytics tools like Python, Power BI, Tableau, and AWS S3 Tables.
Apply for this position
This job is hosted externally. Click below to view the full posting and apply.
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Good distractions
Talks and stories from around this role — technically off-topic, practically not.
Moments
Explore playlistsVideos
See allRelated articles
See all
What Are The Top Skills Required For Azure Developers?
How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again
Technical Documentation For Developers
Humanizing Your Documentation