Product Owner

E1 EDF Trading Ltd
London
1 year ago
Applications closed

Related Jobs

View all jobs

Data Engineering Product Owner, Technology, Data Bricks, Microsoft

Data Engineering Product Owner, Technology, Data Bricks, Microsoft

Data Engineering Product Owner, Technology, Data Bricks, Microsoft Stack

Senior Data Engineer - Azure

Data Engineer

Data Engineer

Description

:

Data is Energy

EDF Trading is a data business too. Trading is transitioning into a data driven business. High quality data and the agility of the analysis are becoming the differentiator. EDF Trading has a leading footprint in the European energy markets and wants to monetise and optimise data as an asset. ​

The European energy space is complex and has a huge appetite for data. Power production from renewables in response to weather, capacity limitations across borders, storage optimisation modelling... these are just some of the complex data opportunities we trade on every day.

We’re looking for talented people who share our passion for data to join our team and seize these opportunities with us.

Team / department

The Data Team is looking for a Product Owner to lead a multi-functional product team to deliver user-facing data tools and services

Main responsibilities

Create the product vision and be the product ‘champion’ Identify and scope out user requirements and translate these into product backlog epics & features, ensuring that they align to business benefits/KPIs Ensure the product meets non-functional requirements including performance, security, scalability and including technical activities (e.g. technical debt, upgrades, architectural changes) Proactively seek technical guidance from the Data Architect and ensure the development follows the agreed approach and meets agreed standards Develop the product roadmap (including release schedule) & communicate this to the product team Manage and prioritise the backlog, balancing strategic and tactical requirements Develop user stories ensuring they are clear & precise, have sufficient detail and the necessary acceptance criteria are included Sequence and schedule user stories Set iteration/sprint goals Determine resource requirements and manage resource risks Manage the product development progress (monitoring, reporting, risks, issues) and ensure the product seamlessly moves through its lifecycle from development to support Approve iterations/products prior to release and ensure the appropriate level of testing is undertaken Define the product KPIs to define product success and monitor against these, addressing areas of concern e.g. low usage Communicate with stakeholders across EDFT, including the business and technical teams, ensuring they are given the context for all work, understand their roles & responsibilities and are kept updated on progress The key people within the Data Team that you’ll work with are the Lead Architect, Technical Lead, developers, QA & testers, Head of Data Management, Programme Manager and Head of Data Build and improve the product team identity, morale, performance and ways of working* * responsible for this if no Scrum Master

Hours of work:

8.30am – 5.30pm / 40 hours per week, Monday to Friday

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.

Careers

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

If you’re trying to break into data science — or progress your career — it can feel like you are drowning in names: Python, R, TensorFlow, PyTorch, SQL, Spark, AWS, Scikit-learn, Jupyter, Tableau, Power BI…the list just keeps going. With every job advert listing a different combination of tools, many applicants fall into a trap: they try to learn everything. The result? Long tool lists that sound impressive — but little depth to back them up. Here’s the straight-talk version most hiring managers won’t explicitly tell you: 👉 You don’t need to know every data science tool to get hired. 👉 You need to know the right ones — deeply — and know how to use them to solve real problems. Tools matter, but only in service of outcomes. So how many data science tools do you actually need to know to get a job? For most job seekers, the answer is not “27” — it’s more like 8–12, thoughtfully chosen and well understood. This guide explains what employers really value, which tools are core, which are role-specific, and how to focus your toolbox so your CV and interviews shine.

Jobs

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

If you’re applying for data science roles in the UK, it’s crucial to understand what hiring managers focus on before they dive into your full CV. In competitive markets, recruiters and hiring managers often make their first decisions in the first 10–20 seconds of scanning an application — and in data science, there are specific signals they look for first. Data science isn’t just about coding or statistics — it’s about producing insights, shipping models, collaborating with teams, and solving real business problems. This guide helps you understand exactly what hiring managers look for first in data science applications — and how to structure your CV, portfolio and cover letter so you leap to the top of the shortlist.

Education

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

Data science has become one of the most visible and sought-after careers in the UK technology market. From financial services and retail to healthcare, media, government and sport, organisations increasingly rely on data scientists to extract insight, guide decisions and build predictive models. Universities have responded quickly. Degrees in data science, analytics and artificial intelligence have expanded rapidly, and many computer science courses now include data-focused pathways. And yet, despite the volume of graduates entering the market, employers across the UK consistently report the same problem: Many data science candidates are not job-ready. Vacancies remain open. Hiring processes drag on. Candidates with impressive academic backgrounds fail interviews or struggle once hired. The issue is not intelligence or effort. It is a persistent skills gap between university education and real-world data science roles. This article explores that gap in depth: what universities teach well, what they often miss, why the gap exists, what employers actually want, and how jobseekers can bridge the divide to build successful careers in data science.

🍪 We use cookies to enhance your browsing experience on our website. By continuing to use this site, you consent to the use of cookies as described in our Cookie Policy. You can review our Cookie Policy for more information.