A. BUTOVA.

Senior BI Developer · Power BI · MS SQL · SSAS

Anastasiia
Butova

I build management reporting the board actually trusts — from the data model to the dashboard on screen.

I own the full BI cycle: from a Figma prototype to published dashboards, automated refresh and user training. 15+ years in analytics, DWH design and management reporting development.

Download CV (PDF) Discuss a project
Based in
Málaga, Spain
Open to
Remote · project · full-time
Experience
15+ years in analytics
Languages
Russian — native
English — B1
Education
SUSU — Economics
and Management
2 500+ Power BI reports
in production 700 KPIs in the warehouse
I designed ×5 faster reporting
cycle 30+ self-service developers
trained

Selected cases

The projects that show my approach best: the data model and the refresh contract first, visualisation second.

Power BI Report Server · commercial KPIs: plan, actual, forecast

CASE 01

Corporate BI system for the weekly board meeting

Problem

The board met weekly, but KPI, construction and finance reporting was assembled by hand from several systems — the numbers were stale by meeting time.

What I did

  • 15+ Power BI dashboards: KPI, construction, finance
  • Tabular model and Star Schema marts for 120 KPIs
  • Automated refresh: stored procedures + M + SQL Agent

×5 faster preparation of the board pack

Power BI DAX SSAS Tabular T-SQL

DWH architecture and entity model: sources → SSIS / MDS → SQL Server → SSAS → Power BI RS

CASE 02

A new data warehouse: Data Vault → Star Schema

Problem

The same metric was calculated differently in different places, history was not kept, and any source change broke the reports.

What I did

  • Logical and physical data model
  • Data Vault layer and Star Schema marts for BI
  • Data quality controls on every layer

100% of KPI calculation automated, source to report

Data Vault Star Schema MS SQL Server SSIS

Report template in Power BI Desktop and the Tema.json theme file: grid, filter pane, palette

CASE 03

Self-service BI and user enablement

Problem

Every new report went through the BI team, the queue kept growing, and no two reports looked alike.

What I did

  • Corporate report templates: json theme, pbit, pbix
  • Modelling and visualisation guidelines
  • Training and mentoring for 30+ colleagues

×5 growth in reports built by the business itself

Self-service BI json theme Enablement

Two pages out of ten · the report reaches the client in PDF every month

CASE 04

Monthly PDF reporting for a French client

Problem

My first international project. The company needed monthly reporting on a subordinate business unit: a single 10-page PDF with several cuts and analytics, delivered to recipients automatically, with no manual assembly.

What I did

  • Multi-page report: team, geography, revenue, commissions
  • Page-by-page layout designed for print and PDF reading
  • Scheduled export and automated delivery

10 pages of monthly reporting reach the client with zero manual work

Power BI PDF delivery Subscriptions International project

Technical stack

Power BI

  • DAX
  • Power Query / M
  • Report Server, Service
  • json theme, pbix, pbit

Warehousing

  • Data Vault
  • Star Schema
  • Data modelling
  • Data quality controls

SQL and ETL

  • MS SQL Server
  • T-SQL, procedures, functions
  • Query optimisation
  • SQL Agent, SSIS

Models and tools

  • SSAS Tabular
  • OLAP, MDX
  • Excel / VBA, PowerPivot
  • Figma, Jira, Git

Certificates

  • Microsoft Power BI Data Analyst
  • PostgreSQL
  • Microsoft Excel pro

How I work

Systems thinking

A report is part of an architecture, not a picture

Business language

I explain complex things simply and gather requirements first-hand

Comfortable with ambiguity

Start with a prototype, refine metrics as we go, no waiting for a perfect spec

Mentoring

I leave behind a team that builds its own reports

Tell me about your reporting

Open to Senior / Lead BI roles and to projects: reporting audit, DWH design, dashboard development, team enablement.

The message reaches me on Telegram. Your details are used only to reply and are never shared.