Senior Data & Analytics Engineer

Javier Moraga

Systems-oriented Data Engineer designing scalable analytical infrastructure for operational environments.

96%
Latency cut · LATAM Airlines
Rebuilt ops reporting — 24h batch → 15-min streaming on Pub/Sub + Dataflow
85%
Query speedup · Clínica Alemana
Led SAS → BigQuery migration · decommissioned 5 legacy silos · CI/CD from day one
40%
Manual effort eliminated · Claro Chile
Full pipeline automation · 99.9% accuracy across multi-TB telecom datasets
Available immediately

Currently interviewing — full-time or long-term contract.
Replies within 24h · References on request.

Overlap with major hubs
NYC · 7h
SF · 4h
London · 6h
Berlin · 5h
Sydney · async
Clients & domains LATAM Airlines · Clínica Alemana · Entel · WOM Chile · Claro Chile
Aviation · Healthcare · Telecom
Scroll to explore
96%
Latency reduction

24h operational reporting collapsed to 15 minutes. LATAM Airlines.

85%
Query speedup

SAS → BigQuery migration. 5 legacy silos decommissioned. Clínica Alemana.

40%
Effort eliminated

End-to-end automation. 99.9% accuracy sustained. Claro Chile.

10+
Years in production

Healthcare, aviation & telecom. Always shipping. Always observable.

Operational ambiguity costs organisations more than slow pipelines.
The problem is rarely the data — it's the distance between data and decision.

01

Work history

10+ years across regulated industries. Remote-capable and shipping from day one.

2025 – Present Healthcare Clínica Alemana
BigQuery
dataform
Python
CI/CD · GitHub Actions
Terraform
Data Studio
Looker
Jira

Data & Analytics Engineer

Clinical reporting ran on legacy SAS infrastructure — fragmented across departments, with no lineage, no observability, and no path to real-time decision-making.

Led end-to-end migration to BigQuery with dbt-modelled semantic layer and automated CI/CD via GitHub Actions. Medallion architecture: raw → staging → marts. Tests on every mart before go-live.

85% reduction in query processing time. 5 legacy silos decommissioned. Real-time clinical analytics enabled for the first time. Deployed across Chile remotely.

85% Faster queries — SAS to BigQuery
clinical data platform
2023 – 2025 Aviation LATAM Airlines
Pub/Sub
dataform
BigQuery
Airflow
CI/CD
Python
Data Studio
Spreadsheet Google
Jira
Confluence

Data Engineer

Network disruptions at LATAM required live operational data. A 24-hour batch pipeline meant that every disruption response was based on yesterday's picture.

12M events/day from Jira and flight-ops systems · 5 countries · 40+ downstream dashboards · 120+ daily operational users.

Replaced the batch process with event-driven streaming on Pub/Sub + Dataflow + BigQuery. Exactly-once guarantees via Dataflow deduplication. Schema contracts enforced by Protobuf at ingestion; breaking changes blocked by CI.

Latency: 24h → 15 minutes. Network operations now steers live during disruptions instead of running next-day post-mortems. Distributed delivery across Chile, Brazil and Peru — async model throughout.

96% Latency reduction · 24h batch
→ 15-min streaming pipeline
Jul – Oct 2023 Consulting A3D
Data cataloging
Documentation
SQL

Data Analyst

Data sources across the company had no formal documentation — access procedures, schemas, and ownership were tribal knowledge. New analysts needed weeks to become productive.

Created a comprehensive data source catalog covering every production data asset: user guides, access procedures, schema documentation, and source-to-report lineage maps.

Reduced information search time significantly across all analyst and BI users. The catalog became the standard onboarding resource for new hires joining the data team.

Dec 2022 – Jun 2023 Telecom Entel
SQL Server
AWS
Athena
AWK / sed / Bash
Power BI
Spreadsheet Google
Monday

Senior Collections Analyst

5M+ postpaid subscribers analyzed across billing cycles, commercial channels, payment methods, and geographic regions. Wireline + wireless product lines.

Diagnosed and fixed a RUT-K parsing bug in the AWK/sed notification pipeline that silently excluded ~24% of accounts. Rebuilt the extraction logic across 5 notification channels (IVR, SMS, APP, MAIL, WSP). Built risk quadrant scatter plots segmenting 16 regions by arrears rate vs. client volume — wireline and wireless separately.

Notification coverage: 76% → 99%. ~460K accounts recovered per billing cycle. Executive dashboards delivered to management with KPI tracking for suspension rates, notification reach, and commercial channel performance.

99% Notification coverage ·
from 76% after RUT-K fix
Jul 2018 – Sep 2022 Telecom WOM Chile
Bigquery
Netezza
SQL Server
Microstrategy
Spreadsheet Google
Excel
Data Studio

Analytics Engineer

Rebuilt churn prediction model and underlying feature pipeline on multi-TB subscriber datasets using PySpark + Snowflake. Self-serve analytics dashboard deployed to commercial teams.

15% model accuracy improvement. 40% reduction in query operating cost. Churn interventions shifted from reactive to predictive.

15% Model accuracy uplift ·
churn prediction rebuild
Oct 2015 – Jun 2018 Telecom Claro Chile
SQL Server
Oracle
Linux
Excel
MicroStrategy

Data Engineer

Designed and operated end-to-end pipelines handling multi-TB network performance datasets. Automated manual reporting workflows across 8 business units. Introduced Kafka-based streaming for real-time network alerting.

40% elimination of manual effort. 99.9% data accuracy sustained. First real-time alerting infrastructure at the company.

40% Manual effort eliminated ·
99.9% accuracy sustained

A system that's fast but unobservable is a system that fails quietly.
Observability is organisational clarity — not an engineering luxury.

02

How I think

Engineering philosophy shaped by 10+ years in regulated, high-stakes environments.

Reducing operational ambiguity
through observable data systems.

The best data infrastructure is the kind organisations stop thinking about — because it just works, it's trusted, and it unblocks decisions instead of creating them.

That requires deliberate architecture choices, not just fast pipelines.

Cost is an architectural input, not an afterthought

Query cost and compute spend shape every design decision alongside latency and reliability. I've reduced operating costs by 40%+ without touching accuracy — because those trade-offs were planned, not patched.

Observability ships in the same PR as the pipeline

Data quality checks, lineage, SLA alerting — these aren't backlog items. They're the definition of done. A system you can't observe is a system you can't trust under pressure.

Streaming vs. batch is a business call

LATAM needed 15-minute latency for live operations — that justified streaming complexity. Batch is cheaper, more resilient, and usually right. The architecture should follow the decision, not the engineer's preference.

The semantic layer is where trust is built

When a metric means the same thing to every team and every dashboard, organisations stop arguing about data and start using it. dbt transforms are business logic codified and tested — not just SQL.

Legacy systems earned their place

Migrations succeed when you understand what the old system got right. SAS and Oracle pipelines exist because they worked. Carrying forward what was trusted — while retiring what was fragile — is the real engineering challenge.

Every engineering decision is also a governance decision.
The systems below were designed with that constraint in view.

03

Selected systems

Architecture decisions, trade-offs, constraints, and outcomes — not dashboards.

Aviation · AI Operations

Amelia AI Chatbot — Operational Analytics

End-to-end analytics platform for LATAM's AI customer service chatbot across 5 countries. 11 interactive charts tracking MAU evolution, error taxonomy, NPS satisfaction, and channel adoption from launch through scale.

Highcharts RAG pipeline NPS analytics Multi-country
Flight Ops Events RAG Ingestion Amelia NLU (5 countries) Analytics Layer 11 interactive dashboards
270KPeak MAU
5Countries
11Charts
83%NPS improvement
Healthcare · Metadata-Driven Platform

Medical Templates Framework — Clínica Alemana

Metadata-driven ingestion engine that replaced 320+ hardcoded PL/SQL procedures with a single JSON-native pipeline on BigQuery. CDC-aware, idempotent, and self-rebuilding — the schema is data, not code.

BigQuery JSON-native Python ingestor CDC governance
Oracle EHR JSON Export 3-level reconciler (drift-tolerant) BQ catalog + json_general Auto-rebuilt views
320+Templates ingested
1mo→1hTime per new template
99%Time-to-insight cut
0Code deploys per change
Healthcare · Migration Engine

SAS → BigQuery Migration System — Clínica Alemana

A deterministic engine for migrating ~300 SAS Enterprise Guide processes to BigQuery. Resolves true execution order via topological sort (the visual order isn't the run order), flags risky patterns before translation, and drives AI with one master prompt so 300 migrations stay consistent.

BigQuery Topological sort Python Generative AI Dual-run
.egp parser Dependency graph Kahn topological sort (self-validated) Risk detection + master prompt AI translation → dual-run
~300Processes in scope
16/16Executable order
48Max nodes resolved
1Master prompt · 300 procs
Telecom · Revenue Assurance

Cross-Platform Reconciliation

Bridging 6 distributed systems — BSCS, DWH, HSS, ICC, SYMSOFT, PCRF — to detect billing-vs-network subscriber discrepancies across 4.5M active lines.

Netezza SQL Oracle BSCS SQL Server AWK/sed
4.5MActive subs
CLP 426M/moRevenue at risk
Telecom · Customer Engagement

Churn & Retention Analytics

Weekly churn intelligence across BAM mobile + Fiber home. Cohort heatmaps, CAP-exhaustion correlation, and an A/B campaign that halved churn.

A/B testing Cohort analysis NPG funnel
8.9→4.1%A/B churn result
23K+Retentions
Telecom · Cost Control & Fraud

Heavy User Detection Engine

Three monthly controls — data (≥50 GB), voice and SMS (300+ destinations) — with per-operator cost modelling across Claro, Movistar and Entel interconnection rates. Fraud HOOK flags and test-line exclusions built into the query output.

Netezza SQL PCRF services RTX billing SYMSOFT SMSC Rating groups
CDR Traffic Stage 1: Aggregation (≥50 GB) Stage 2: PCRF service join Stage 3: Classification + Cost model Report → Marketing, Finance, CX
CLP 549MWOM network cost
CLP 84MInterconnection cost
3Controls / cycle
11×Entel vs Claro rate
Telecom · DataOps

The "K" Bug — Pipeline Debugging

Auditing legacy AWK/sed scripts uncovered a RUT parsing failure that silently excluded 24% of accounts from billing notifications across 5 channels.

AWK sed Bash SQL Server
76→99%Coverage
~460KAccounts recovered
Telecom · Business Analytics

Collections Risk Quadrants

Transforming flat percentage grids into scatter-plot risk matrices. Wireline vs Wireless segmentation across 16 regions with the 0.00% data quality catch.

SQL Highcharts Risk segmentation
16Regions
0.00%Anomaly caught
Healthcare · Platform migration

SAS → BigQuery — Clinical Data Platform

Legacy SAS infrastructure fragmented across departments — no lineage, no observability. Phased migration to BigQuery with dbt marts and CI/CD via GitHub Actions.

BigQuery dbt GitHub Actions Power BI
85%Query speedup
5Silos retired
0→1Real-time analytics
04

Remote delivery

10+ years operating across distributed teams. Async-first from day one.

Written-first communication

Decisions, trade-offs, and pipeline behaviour live in docs and PR descriptions. Not in someone's head, and not in a meeting that happened while you were asleep. Written communication is how distributed teams build shared understanding across time zones.

Own the outcome, not the hours

Clear weekly commitments, visible progress, and a status update before anyone has to ask. Remote work fails when expectations are implicit. I make mine explicit from week one.

Default to async

Loom walkthroughs over screen-share calls. Detailed PRs over scheduled reviews. Meetings reserved for what genuinely requires them. My calendar is not the bottleneck in your delivery schedule.

CI/CD as a communication layer

Pipelines deploy on PR merge. Tests run before anything reaches production. My timezone doesn't affect your deployment schedule — the system handles it.

Professional English, always

Daily working language for 10+ years — technical and stakeholder-facing, written and spoken. Stand-ups, architecture docs, incident post-mortems, executive readouts.

Working hours overlap

Anchored at Santiago, Chile (UTC-3) · 9:00–18:00 window

My windowUTC-3 · Santiago
09–18local
NYC · ESTUTC-5
~7hoverlap
SF · PSTUTC-8
~4hoverlap
London · BSTUTC+1
~6hoverlap
Berlin · CETUTC+2
~5hoverlap
Sydney · AEDTUTC+11
async+1–2h flex

Flexible on schedule — often start earlier for EU overlap, extend late for US West deep-collab. Australia / APAC: async-first with written handoffs, Loom walkthroughs, and PR-driven reviews. ~1–2h sync available on request.

Current stack
Warehouse · Modeling
BigQuery Dataform Athena Postgres Oracle
Languages · Processing
Python SQL Pandas Linux Shell Scripting
Orchestration · Streaming
Airflow Dataflow Pub/Sub Jenkins
Cloud · Infra · CI/CD
GCP AWS Terraform GitHub Actions
Analytics · BI · Async
Looker Data Studio Power BI Tableau Jira Loom

Hiring across borders has two parts: can we do it legally,
and is this person a good bet for the team.

05

Working together

Legal pathways, life context. Logistics handled before the offer letter.

Work authorisation pathways
AU Australia TSS 482 visa via ACLFTA · exempt from Labour Market Testing for Chilean nationals · faster sponsorship process
US USA H-1B1 Chile FTA visa · 1,400 reserved annually for Chilean professionals · no lottery, no cap pressure · renewable indefinitely
EU Europe EU Blue Card eligible · Highly Skilled Migrant pathways for NL, DE, IE · IT specialist fast-track in most member states

Hiring legally is solved territory across all three regions. References on the official pathways available on request.

Javier Moraga
Beyond the pipelines

A relocation,
not a contract gig.

I'm not looking for a six-month gig. I'm looking for a place to build a chapter — with my partner and our dog Rocky alongside.

The portfolio above is the work I do when I'm settled — that's the version I'd bring to your team.

Partnered · stable household Dog parent · Rocky Relocation-ready · not contract-hopping
06

Let's talk

Interviewing now · Replies within 24h

I build systems
organisations can
act on.

"Streaming vs. batch is never just a tech decision —
it's an organisational decision in disguise."