Portfolio Reporting Lead

Bishopsgate
9 months ago
Applications closed

Related Jobs

View all jobs

Data Governance Lead

SAS Data Engineer

Principle SQL Developer

Delegated Authority Data Governance & Bordereaux Manager

Portfolio Reporting Lead
City of London (Hybrid)
£600 - £625 per day (inside IR35)

On behalf of an expanding financial services organisation, I am seeking an experienced Portfolio Reporting Lead to be responsible for managing the Portfolio reporting tool, working with the portfolio team leads to create and automate reporting that integrates product, project and portfolio level reporting. This role is being offered on an initial 6 month contract basis.

The company operate a hybrid work policy and therefore you must be willing to commit to a non-negotiable 3 days per week and must be within commutable distance of their City of London HQ.

Responsibilities:

  • The role will be the reporting lead for the portfolio team interfacing with finance, HR and the product/business teams where relevant. The role will work closely with the Data CoE, tooling and automation focussed, leading the activity to consolidate, automate and streamline all portfolio and centralised technology reporting.

  • This role will create the reporting mechanism that ensures a continuous cohesive view of all Investment (product, project and pipeline).

  • This role will lead the activity around managing the current portfolio tool and the process to implement and embed our future ready and AI focussed portfolio tool.

  • This role will manage and enhance the central Technology KPI dashboard using Power BI and other relevant tooling.

  • The role will also be a central presentation resource supporting with deck building for key Technology wide submissions.

    Responsibilities:

  • A solid understanding of Technology operating models and the evolving technology landscape/trends

  • Experience working in agile environment and has previously worked with Agile and product methodology

  • Strong Power BI, Snowflake and reporting experience

  • Experience with business storytelling and building compelling PowerPoint decks

  • Demonstrable experience in building portfolio dashboards, reports and presentations

  • Experience working with and implementing Portfolio and Product tooling

  • Very strong commercial and financial experience

  • Ability to work with a myriad of stakeholders at varying levels of seniority.

  • Broad technology experience with a good understanding of the underlying technology functions (Engineering, Architecture, data)

  • Experience creating strategy in a product led organisation

  • Experience working with AI portfolio tooling to create insight driven MI reports

  • Systems thinking, problem solving, analytical skills & a collaborative team player with strong relationship management skills

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.