Data engineer · London, UK

Hey, I'm Ignacio
and I do data

I enjoy finding problems that data can solve. I build data pipelines, uncover and document business knowledge, and find the metrics people can actually act on.

01Where I've worked

Experience

From a startup where I was the whole data team to enterprise banking. Pull a folder out of the drawer and drop it on the desk to read the file.

Drag a folder onto the desk
or just clicktap one

02Things I build for fun

Projects

I leverage AI to build all the things that I find useful or interesting. I like finding playful, visual ways to explore information.

More on GitHub →

03Notes I keep coming back to

How I work

A pile of notes from my notebook: how I work, what I enjoy, and a few quotes I've been collecting.

Read the note, then throw it towards the bin.

0 / 15 in the bin

From my notebook

Before picking which problem to solve first, I always ask which one will have the biggest impact. Big fan of the 80/20 rule.

From my notebook

In the AI era, documentation matters more than ever. I enjoy the challenge of writing for the audience in front of me.

From my notebook

In remote teams overcommunication is key

Something I enjoy

Brainstorming a messy problem with a small team.

Something I enjoy

Turning vague questions into the right metrics.

Something I enjoy

Helping non-technical people do their jobs better.

Something I enjoy

Finding fun, visual ways to explore information.

Something I enjoy

Building small tools with AI to fix my own problems.

Something I enjoy

UX and design, not just the data underneath.

Something I read and keep coming back to

The goal is always to build a robust pipeline… from “exciting” to “boring”.

Something I read and keep coming back to

Most of the work we do in data is in an effort to reduce entropy — we model data to remove inaccuracies, we turn commonly asked questions into self-serve reports, and we funnel ad-hoc questions into a formalized request process. This kind of attitude is in our nature as data practitioners and largely serves us well. But in the case of driving decisions with data, we need to challenge our instincts and embrace the chaos.

Something I read and keep coming back to

Success is helping on making decisions fast, not delivering data.

Something I read and keep coming back to

Our job is not to convince others of the value of research – it’s to create value through uncovering information that can change minds.

Something I read and keep coming back to

The data engineer becomes almost like the keeper of good data habits. For instance, if an analytics engineer reprocesses the warehouse at every run with dbt, they can develop bad habits. The data engineer is the gatekeeper, responsible for educating data teams on best practices, most notably around efficiency (handling incremental loads), data modeling, and coding standards, and relying on data observability and DataOps to ensure that everyone is treating data with the same diligence.

Something I read and keep coming back to

One thing that worked really well was the ability to create alignment with stakeholders early in the process by writing up clear requirements documents. Scope creep for data tool development is so common, especially when the tool is expected to magically answer any question they might have of the data. Establishing early on what exactly we were going to build and what set of questions that particular data model would answer saved us some frustrating conversations down the line.

$ cat ignacio-valdelvira.cv --format=text

Ignacio Valdelvira Isla

Data Engineer · London, UK

email: ignvaldelvira@gmail.com
web:
github: https://github.com/ignaciovi
linkedin: https://www.linkedin.com/in/ignaciovaldelviraisla/

## Summary

Data Engineer who starts with the problem, not the pipeline. dbt, Snowflake and Airflow at enterprise scale, with a startup instinct for owning problems end to end.

## Experience

### Senior Data Engineer (contract) — NatWest

→ present · London, UK

  • Delivered data products to the enterprise data marketplace, giving self-service access across the bank while meeting internal governance standards. Prioritised requirements by business impact.
  • Matured the data architecture and data quality practices, championing more efficient tooling like dbt to bring the platform in line with industry best practice.
  • Investigated and documented legacy processes and undocumented business assumptions, creating a clear knowledge base for governance and onboarding.
  • Drove adoption of AI-assisted development, coaching colleagues on using it well and freeing up time for architecture and legacy discovery.

stack: dbt, Snowflake, Airflow, AWS, Terraform

### Senior Data Engineer (consultant) — Hippo

→ · Glasgow, UK

  • Designed and built a secure data exchange hub for ingesting and exporting data across 40+ partner companies, creating one unified, enriched customer view.
  • Cut SQL query runtimes from hours to minutes by optimising ETL pipelines.
  • Started from the business use case before building any pipeline.
  • Made data quality a priority with dbt tests, Monte Carlo monitoring and clear documentation.
  • Applied Kimball dimensional modelling to define business entities and processes.
  • Mentored teams on best practice and kept an eye on technical debt.

stack: dbt, Snowflake, Airflow, dlt, AWS, Terraform, Monte Carlo

### Data Engineer & Data Scientist — Phlo

→ · Glasgow, UK

  • Built the company’s data architecture from scratch with BigQuery, dbt, Airflow, Docker and Airbyte.
  • Customer service: LTV/RFM prioritisation and churn prediction took churn from 10% to an industry-leading 4%.
  • Marketing: customer segmentation and campaign design cut acquisition cost by 60%.
  • Product: introduced A/B testing and KPI monitoring, reducing registration drop-off by 20%.
  • Pharmacy: time-series demand forecasting reduced stock shortages by 10%; Metabase dashboards exposed workflow bottlenecks.
  • Finance: automated monthly reporting in Python and surfaced areas of negative profitability.
  • Data quality through Great Expectations tests, documentation and lightweight governance; cost-optimised SQL with partitions, clustering and incremental models.

stack: BigQuery, dbt, Airflow, Airbyte, Docker, Python, Metabase, Great Expectations

### Full-stack Developer — Phlo

→ · Glasgow, UK

  • Delivered product features with product owners and designers using Agile.
  • Learned industry-standard testing and software practices (unit testing, Jest, React, CSS).
  • Trained new joiners.

stack: React, Jest, TypeScript, CSS

## Education

## Skills

## Projects

## How I work

## Interests

Guitar and singing (open mics, live looping with a Boss RC-500). Advanced certified scuba diver.