Data Product Owner (SQL/NoSQL)

Chatham
1 day ago
Create job alert

Data Product Owner (SQL/NoSQL)

Our trusted client, who we have partnered with for several years is hiring a Data Product Owner to play a pivotal role in the data modernisation programme. The chosen Data Product owner will have strong capabilities in launching data platforms and services end to end delivering large scale & complex data transformation initiatives partnering with data engineers, architects and the CDO.  Our client is offering a basic salary of £95,000 + 25% bonus + 28 days holiday + 8% contributory pension + more to be based in Chatham, London and Wolverhampton on a hybrid basis.

To be successfully, the chosen Data Product Owner must have strong experience within the financial services domain coupled with experience of SQL & NoSQL architectures who has proven experience delivering data transformation initiatives aligning to SAFe/Agile ownership to be considered.

The ideal candidate will be will be a seasoned data leader or senior architect / analyst with a blend of experience across data, focusing on identifying and delivering value as part of a large-scale transformation initiative

Core responsibilities:

Define and own the vision, strategy and roadmap for enterprise data platforms aligned to CDO and business strategy
Partner with SMEs, architects, engineers and cross-functional leaders to shape high-value data solutions
Translate product vision into a prioritised, value-based delivery roadmap
Develop and validate business cases, presenting to senior stakeholders and C-level committees
Establish clear success metrics, KPIs and measurable outcomes
Lead ideation workshops to identify customer needs, pain points and innovative solutions
Apply Lean Agile and SAFe practices, collaborating across Program Increment (PI) cyclesChampion best practice across data products including:

BI dashboards and reporting
Data APIs and feeds
Cloud and hybrid data platforms
ML models and services
Data models and governance frameworks
Master data management
Act as the voice of the Data Platform, aligning technical capability with business demand
Ensure full compliance with Risk and Data Governance policiesEssential experience:

Defining and launching enterprise data platforms and services end-to-end
Delivering large-scale data transformation initiatives
SQL and NoSQL architectures
Cloud or hybrid data platforms (Azure experience desirable)
Financial modelling, ROI definition and KPI-driven decision making
Working with senior stakeholders and influencing without authority
Agile, Lean and continuous delivery methodologiesData Product Owner (SQL/NoSQL)

Related Jobs

View all jobs

Data Engineering Product Owner, Technology, Data Bricks, Microsoft

SAS Data Engineer

Data Engineer (SC Cleared)

Data Governance Analyst (PIM)

Data Engineer

Senior Data Engineer - Energy

Subscribe to Future Tech Insights for the latest jobs & insights, direct to your inbox.

By subscribing, you agree to our privacy policy and terms of service.

Industry Insights

Discover insightful articles, industry insights, expert tips, and curated resources.

How Many Data Engineering Tools Do You Need to Know to Get a Data Engineering Job?

If you’re aiming for a career in data engineering, it can feel like you’re staring at a never-ending list of tools and technologies — SQL, Python, Spark, Kafka, Airflow, dbt, Snowflake, Redshift, Terraform, Kubernetes, and the list goes on. Scroll job boards and LinkedIn, and it’s easy to conclude that unless you have experience with every modern tool in the data stack, you won’t even get a callback. Here’s the honest truth most data engineering hiring managers will quietly agree with: 👉 They don’t hire you because you know every tool — they hire you because you can solve real data problems with the tools you know. Tools matter. But only in service of outcomes. Jobs are won by candidates who know why a technology is used, when to use it, and how to explain their decisions. So how many data engineering tools do you actually need to know to get a job? For most job seekers, the answer is far fewer than you think — but you do need them in the right combination and order. This article breaks down what employers really expect, which tools are core, which are role-specific, and how to focus your learning so you look capable and employable rather than overwhelmed.

What Hiring Managers Look for First in Data Engineering Job Applications (UK Guide)

If you’re applying for data engineering jobs in the UK, the first thing to understand is this: Hiring managers don’t read every word of your CV. They scan it. They look for signals of relevance, credibility, delivery and collaboration — and if they don’t see the right signals quickly, your application may never get a second look. In data engineering, hiring managers are especially focused on whether you can build and operate reliable, scalable data systems, handle real-world data challenges and work effectively with analytics, BI, data science and engineering teams. This guide breaks down exactly what they look at first in your application — and how to shape your CV, portfolio and cover letter so you stand out.

The Skills Gap in Data Engineering Jobs: What Universities Aren’t Teaching

Data engineering has quietly become one of the most critical roles in the modern technology stack. While data science and AI often receive the spotlight, data engineers are the professionals who design, build and maintain the systems that make data usable at scale. Across the UK, demand for data engineers continues to rise. Organisations in finance, retail, healthcare, government, media and technology all report difficulty hiring candidates with the right skills. Salaries remain strong, and experienced professionals are in short supply. Yet despite this demand, many graduates with degrees in computer science, data science or related disciplines struggle to secure data engineering roles. The reason is not academic ability. It is a persistent skills gap between university education and real-world data engineering work. This article explores that gap in depth: what universities teach well, what they consistently miss, why the gap exists, what employers actually want, and how jobseekers can bridge the divide to build successful careers in data engineering.