AVAILABLE NOW  ·  ANALYTICS ENGINEER  ·  IL / REMOTE

Analyst by trade.
Builder by habit.

Anastasia Bogacheva — analytics engineer. I build analytical systems for money that has to be counted correctly — payments, risk, fraud, compliance. When the tooling doesn’t exist, I build it myself.

// IF IT HAPPENS TWICE, AUTOMATE IT.

06+ YEARS IN DATA
147M ROWS, BIGGEST TABLE SHIPPED
04 SQL ENGINES SPOKEN
03 SYSTEMS BUILT AFTER HOURS
SELECTED WORK — 01

Proof from the day job.

CASE A — FRAUD & RISK ANALYTICS

TRUSTED IN OUT ALLOWED BLOCKED CAP = ƒ(INBOUND)

Fraud exposure needed a policy answer: how much outbound volume should a customer's trusted inbound activity actually earn? I built the eligibility analytics — simulated four policy thresholds, quantified the volume at risk, and shipped the Power BI views risk leadership steers by, with violation reporting by country and segment.

OWNED — datasets · threshold simulations · reporting layer WITH — risk & compliance stakeholders
BIGQUERYPOWER BIRISK

CASE B — WAREHOUSE MIGRATION

MSSQL — 14 MODELS BIGQUERY — SAME 14 = Δ WAS ROW_NUMBER ORDER — PINNED

A risk-scoring pipeline the business already trusted had to move engines without the numbers moving. I migrated the 14-model chain from SQL Server to BigQuery and validated it to row-level parity — including root-causing a silent cross-engine mismatch to nondeterministic ROW_NUMBER ordering, then pinning it and proving the match.

OWNED — BigQuery implementation · parity validation · root-cause WITH — data engineering
READ THE DEBUG NOTE — WITH THE SQL ↗
MSSQL → BIGQUERYDBTPARITY

CASE C — PIPELINES AT SCALE

147M ROWS / 18 GB — PARTITIONED SCANNED ONLY THESE BYTES ↓

New messaging-session data had to become queryable without becoming expensive. I built the dbt staging and Airflow orchestration for a 147-million-row, 18 GB table, partitioned so queries stopped paying for it — then ran a warehouse cost hunt through INFORMATION_SCHEMA that turned partitioning and clustering into visibly smaller bills, with analyst workflows unchanged.

OWNED — dbt staging models · Airflow DAG · partitioning & cost analysis WITH — data platform team
DBTAIRFLOWCOST TUNING

EMPLOYER WORK DESCRIBED AT A SAFE ALTITUDE — FULL DETAIL IN CONVERSATION.

SYSTEMS — 02

Tools I didn’t wait for.

SYSTEM 01 — LIVE

JobSeek

A job-search intelligence framework — part of a larger AI career operating system built in Obsidian. Listings flow in, get scored against my profile, and land in Telegram, with an interview-prep engine that builds a briefing for every callback.

  • Live Telegram delivery pipeline
  • Scoring engine tuned to the Israeli market
  • Interview-prep engine — a briefing per callback
  • Python + Obsidian, documentation-first
THE FULL TOUR — ARCHITECTURE & SCREENSHOTS ↗
LISTINGS IN SCORING TELEGRAM TRACKER PREP ENGINE FIG. 01 — JOBSEEK / FLOW
SYSTEM 02 — IN USE RIGHT NOW

Analyst Vault

An eight-skill analysis suite for Claude Code: business context → exploration → methods → statistics → SQL → visualization → reporting, with an orchestrator that sequences the whole workflow.

  • Eight skills, one orchestrator
  • Reproducibility as a rule, not a hope
  • Uncertainty surfaced, never hidden
  • This site was built inside it
FULL SCHEMATIC — THE FLAGSHIP PAGE ↗
ORCHESTRATOR CONTEXT EXPLORE METHODS STATS SQL VIZ REPORTING FIG. 02 — VAULT / SEQUENCE
SYSTEM 03 — DAILY DRIVER

LifeOS

A personal tracking system with RPG mechanics — habits, energy and streaks become quests and stats. Same pipeline architecture as JobSeek, pointed inward: tracked in Obsidian, rendered as generated dashboards.

  • Same architecture as JobSeek — proof the pattern reuses
  • RPG mechanics laid over real habits
  • Core-plugins-only Obsidian, static generated dashboards
  • Built because the app version of this didn’t exist
HP XP DAILY QUESTS FIG. 03 — LIFEOS / SHEET +1
OPERATING SYSTEM — 03

How I run analysis.

  1. 01

    If a question is asked twice, it deserves a system.

  2. 02

    Reproducibility beats cleverness.

  3. 03

    Business context before SQL.

  4. 04

    Surface uncertainty — don’t hide it.

  5. 05

    Don’t automate a bad process.

STACK — 04

The working surface.

ANALYTICS ENGINEERING BigQuery · dbt · Airflow · Data Vault 2.0 · star schema · semantic layers · Power BI
DATA ENGINEERING Python · advanced SQL · incremental ELT · partitioning & clustering · query tuning · automation
ANALYTICS Metrics & KPI design · experimentation · dashboard design · data validation · stakeholder communication
FOUNDATIONS PostgreSQL · SQL Server · ClickHouse · Tableau · Superset · Google Cloud · Git / GitLab · Linux · Obsidian
ABOUT — 05

Behind the cursor.

I’m Anastasia Bogacheva — an analytics engineer for regulated money data: risk, compliance and payment operations at a global payments company, and before that automation and integration in a major bank’s infrastructure department — DWH, ETL and capacity work that was data engineering before I called it that.

I enjoy turning messy analytical questions into systems that answer themselves. I care about reproducible pipelines, honest numbers, and saying “the data can’t tell us that” out loud when it’s true.

LATEST PAYONEER — ANALYTICS ENGINEER · RISK, COMPLIANCE & PAYMENT OPS
BEFORE VTB BANK — AUTOMATION & INTEGRATION EXPERT · DWH, ETL, CAPACITY
PATH INFRASTRUCTURE ANALYTICS ANALYTICS ENGINEERING AI-ASSISTED SYSTEMS
LANGUAGES EN — WORK · RU — NATIVE · HE — IN PROGRESS
Anastasia Bogacheva — portrait
FIG. 04 — PORTRAIT, ACTUAL  ·  SCALE 1:1
STATUS: OPEN TO WORK

Hiring for a data role?
Let’s talk.

Tell me what your data has to survive — auditors, regulators, fraud models — and I’ll reply with how I’d build for it.

kneelisad@gmail.com

CENTRAL ISRAEL · CITIZEN — NO SPONSORSHIP NEEDED · INTERVIEWS IN EN / RU

NOW BUILDING — ANALYST VAULT · AN AI-NATIVE ANALYTICS WORKFLOW ↗