Jhon Lucas · Founder & Data/AI Engineering Consultant

I build data systems that survive production.

Data platforms, AI workflows, and blockchain infrastructure for teams that need dependable systems—not another prototype.

I like messy data, clear systems, and infrastructure that becomes boring for the right reasons.

Three systems, shown with the difficult parts included.

Architecture matters, but so do recovery, deployment, observability, and the handoff to the people who operate what was built.

Architecture diagram for the Uniswap V3 event streaming system

Case 01 · Web3 streaming

Uniswap V3 Event Streamer

A production-style event pipeline that turns raw Uniswap activity into a restart-safe, observable stream for downstream analytics.

The hard part

Handling checkpoints and chain reorganizations without corrupting downstream state.

The system

Decoupled Kafka producers and consumers with PostgreSQL, Prometheus, and Grafana.

Python, Kafka, PostgreSQL, Docker, Prometheus, Grafana

Read the repository ↗
Architecture diagram for a large-scale marketplace data lakehouse

Case 02 · Data platform

Marketplace Data Lakehouse

A shared AWS data platform built to make more than 35TB of marketplace data accessible across analytics and business teams.

The hard part

Bringing 30+ databases and 300+ tables into a platform that could scale without creating another operational bottleneck.

The system

Spark on EMR with Hudi, Athena, ECS ingestion, Airbyte, Airflow, and Power BI on top of S3.

AWS, Spark, EMR, Hudi, Athena, Airflow, Airbyte, Power BI

Architecture diagram for the automated data pipeline factory

Case 03 · Platform automation

Data Pipeline Factory

A reusable framework that moved data work out of notebooks and into standardized, production-ready pipelines.

The result

Cut initial setup from days to minutes and reduced pipeline delivery from roughly one month to 1–2 weeks.

The system

YAML-driven project scaffolding and Airflow DAG generation, deployed through Docker, ECS, Terraform, and CI/CD.

Python, Airflow, YAML, Docker, AWS ECS, Terraform, CI/CD

The work is measured after it ships.

Selected outcomes from data-platform and infrastructure work across startups, marketplaces, and Web3 teams.

8+

years building and operating data systems

50–70%

faster pipeline delivery through reusable platform patterns

30%

cloud-cost reduction through ECS and Iceberg migrations

Selected experience

Spectral Labs, OpenBlock Labs, and Olist—working across platform architecture, analytics engineering, infrastructure, and technical mentorship.

Start with the shape of the problem.

I usually work through one of three formats. Each is scoped around a concrete decision, system, or operating problem.

What collaborators remember.

“One of the strongest data engineers I've had the chance to collaborate with. His AWS knowledge is impressive, and he always figured things out fast.”
Murathan Bağdat DeFi Risk Analyst at Chaos Labs · LinkedIn ↗
“Strong data engineering expertise, ownership, and practical problem-solving. He played a key role in building the data platform, feature store, and APIs.”
“Thoughtful, efficient, and takes ownership. He consistently delivered reliable, high-quality data infrastructure.”
Sishir Varghese CEO & Co-Founder at The Grid and Spectral Finance · LinkedIn ↗
“Turns complex blockchain and DeFi data into something reliable and actionable. A pragmatic partner across platform, analytics, and modeling work.”
Zane Peycke Head of Machine Learning at The Grid · LinkedIn ↗

A data engineer who cares about the operating system around the code.

I enjoy turning complicated systems into dependable infrastructure that teams can understand and own.

I'm Jhon Lucas, a data and AI engineering consultant based in Brazil. Over the past eight years, I've worked across startups, marketplaces, and Web3—building platforms, automating delivery, and helping teams make better technical decisions.

I work comfortably across Python, Spark, dbt, Terraform, ECS, FastAPI, and modern AI tooling. The technology matters, but I care more about the habits that keep systems useful after the initial launch.

  • Make failure modes visible before they become incidents.
  • Choose boring infrastructure when boring is enough.
  • Write systems and documentation for the next person.
  • Measure success in operational outcomes, not diagram complexity.

More systems built along the way.

A compact record of platform, analytics, infrastructure, and applied-data work.

Cross-chain dbt transformation layer Analytics engineering

Challenge

Build reliable, cost-effective transformations across Ethereum, Arbitrum, Linea, and EigenLayer without duplicating model logic.

Work

Created reusable dbt macros and incremental models, orchestrated by Airflow across Athena, Snowflake, and BigQuery with testing and partitioning standards.

Outcome

Delivered faster cross-chain insights, more reliable models, and lower transformation costs.

dbt · Airflow · Athena · Snowflake · BigQuery · Iceberg · Python · SQL

Automated Dune Analytics ingestion Platform automation

Challenge

Manual exports from Dune Analytics were slow, error-prone, and prevented teams from accessing blockchain data quickly.

Work

Built self-service ingestion into Athena with ECS, Airflow, Docker, Terraform, and Slack status notifications.

Outcome

Reduced ingestion time by 90%, removed recurring manual steps, and improved reliability and onboarding.

Python · AWS ECS · Athena · S3 · Airflow · Docker · Terraform · Slack API

Data Lakehouse for blockchain and DeFi Data architecture

Challenge

Move beyond a NoSQL-only setup and support blockchain, lending-protocol, and cryptocurrency data in one analytical platform.

Work

Evaluated open table formats, designed the multi-source architecture, and implemented the platform and its analytical access patterns.

Outcome

Established a functional lakehouse that made DeFi and blockchain data consistently available for analytics.

AWS · Apache Spark · Apache Hudi · Airflow · Terraform

Unique EOA Address Analysis DeFi data

Challenge

Track unique externally owned accounts across Aave V1, Aave V2, and Compound events with changing on-chain state.

Work

Extracted lending events, resolved unique addresses, and used Apache Hudi upserts to maintain the tracking dataset.

Outcome

Created a repeatable address-tracking system for efficient DeFi event analysis.

Apache Hudi · DeFi · Python

On-chain Credit Score Pipeline Blockchain data

Challenge

Obtain comprehensive Ethereum transaction data for credit scoring faster and more reliably than the Etherscan API allowed.

Work

Compared Geth and Erigon, deployed an Erigon archive node, and built ECS extraction plus Athena and EMR Serverless processing and wallet models.

Outcome

Delivered a high-performance transaction data system for on-chain credit analysis.

Ethereum · Erigon · AWS ECS · EMR Serverless · Athena · Airflow

Polygon Subgraph DeFi Ingestion Event pipelines

Challenge

Collect lending-protocol events from the Polygon subgraph on The Graph for downstream analysis.

Work

Configured event extraction, processed protocol data, transformed it for analysis, and connected it to the existing data platform.

Outcome

Enabled detailed and repeatable analysis of Polygon lending activity.

The Graph · Polygon · DeFi · Python

MWAA Private Network Deployment Cloud infrastructure

Challenge

An MWAA network configuration created unnecessary traffic costs and security concerns.

Work

Reworked the VPC configuration, removed the NAT dependency, and restricted access through the private VPN network.

Outcome

Reduced data-traffic costs by 90% while improving access control.

AWS MWAA · Terraform · VPC

BI Platform for Retail Business intelligence

Challenge

Translate retail business rules into a dependable warehouse and reporting platform.

Work

Worked with business and consulting teams on service deployment, dimensional modeling, and fact-and-dimension design.

Outcome

Established shared business definitions and the infrastructure required for consistent reporting.

Microsoft SQL Server · SSAS · SSRS · SSIS · Targit

Stockout Reduction Model Applied analytics

Challenge

Frequent stockouts across retail branches were reducing product availability.

Work

Analyzed branch inventory, encoded business rules, and built an algorithm recommending product transfers between stores.

Outcome

Reduced stockouts through data-driven inventory balancing across branches.

Python · Oracle Database · SQL · Matplotlib · Jupyter

RFM Customer Segmentation Customer analytics

Challenge

Marketing teams needed clearer customer segments for more effective campaigns.

Work

Prepared customer data, calculated recency, frequency, and monetary scores, and combined them with cluster analysis.

Outcome

Enabled targeted campaign strategies based on customer value and buying behavior.

Python · Oracle Database · SQL · Metabase

Twitter Data Analysis Academic project

Challenge

Collect and analyze Twitter activity around selected hashtags as an end-to-end academic data project.

Work

Built ingestion with Apache NiFi and StreamSets, then processed and visualized the collected data.

Outcome

Produced a working social-data pipeline and practical analysis of the captured activity.

Apache NiFi · StreamSets · Python

Lambda Observability Alerts Reliability

Challenge

More than 20 AWS Lambda functions had no consistent failure-notification system.

Work

Built Python monitoring, detailed failure messages, automated checks, and Slack delivery.

Outcome

Introduced real-time operational visibility and reduced the time required to detect failures.

AWS Lambda · Python · Slack API

DynamoDB to Lakehouse Pipeline Streaming ingestion

Challenge

Make marketplace events stored in DynamoDB available for timely business analysis.

Work

Captured changes with Kinesis Streams, processed them with Kinesis Analytics, and stored analytical data in S3 for Athena.

Outcome

Delivered a real-time route from operational events to queryable lakehouse data.

AWS Kinesis · DynamoDB · S3 · Athena

CRM Event Webhook Event pipelines

Challenge

Sales teams lacked a real-time path from CRM activity to analytical data.

Work

Created a Flask webhook, processed events with AWS Lambda, deployed through Serverless, and stored the results in S3.

Outcome

Made CRM events available for near-real-time sales analysis and decision-making.

AWS Lambda · Flask · Serverless · S3

Python · SQL · Spark · dbt · Airflow · AWS · Terraform · Docker · ECS · Athena · Iceberg · Kafka · PostgreSQL · FastAPI · AI agents · retrieval systems · blockchain data