End-to-end Databricks platform
Built the platform across ingestion, transformation, governance, observability, data quality, and production-model delivery.
- Model-serving SLO
- 99.9%
- Data-quality incidents
- −40%
Staff Data Platform Engineer · Data infrastructure, reliability, and production ML
Staff Data Platform Engineer specializing in high-volume ingestion, distributed processing, governance, and hybrid architecture—with production ML engineering across the same lifecycle.
Selected production outcomes
Each result reflects delivered production work, not a portfolio simulation.
Built the platform across ingestion, transformation, governance, observability, data quality, and production-model delivery.
Removed ingestion and execution bottlenecks across workloads spanning on-premises infrastructure and cloud services.
Delivered two separate initiatives: migrated 40% of high-volume financial-operations data, then optimized workloads intentionally retained on-premises.
Improved Snowflake and PySpark delivery across PIX, conciliation, CDB, executive KPIs, regulatory reporting, and the enterprise warehouse.
Experience
Platform scope expanded from banking analytics to critical financial data, hybrid estates, production ML, and end-to-end platform ownership.
Own the architecture and operation of a Databricks platform spanning ingestion, transformation, governance, observability, data quality, and model serving.
Led distinct migration and performance programs across a hybrid estate spanning on-premises infrastructure, AWS, and GCP.
Engineered production ML workflows from data preparation and feature design through experimentation, deployment, monitoring, and model improvement.
Delivered critical financial-data products and enterprise warehouse capabilities across Snowflake, PySpark, Kafka, and regulated reporting workflows.
Automated ETL and analytical workflows while improving customer-data reliability, Snowflake performance, and ingestion efficiency in banking.
Technical capabilities
Concepts and operating responsibilities come first. Tools follow the architecture, workload, and organizational constraints.
Operating principles
Architecture decisions are evaluated through production behavior: reliability, change safety, team autonomy, and lifecycle cost.
Ownership, SLOs, recovery, cost, and change control are part of the system—not follow-up work.
A faster component is not an improvement when it creates instability, opaque handoffs, or downstream debt.
Standards, automation, and self-service should make the correct implementation the easiest one to repeat.
Education
B.Sc. in Computer Engineering — Universidade Presbiteriana Mackenzie, 2021
Electronics Technician — SENAI São Paulo, 2015
Selected certifications
Data Architect Nanodegree — Udacity
Data Product Manager Nanodegree — Udacity
Data Streaming Nanodegree — Udacity
Machine Learning DevOps Engineer Nanodegree — Udacity
Machine Learning Specialization — DeepLearning.AI
Machine Learning Engineering for Production (MLOps) — DeepLearning.AI
Data Engineering with AWS Nanodegree — Udacity
Contact
If the role involves data-platform ownership, hybrid systems, high-volume processing, governance, or production ML, send the mandate and context. I review each request before scheduling a conversation.
Direct details
guilherme_s.ferreira@outlook.com