Tiago ReisData Engineer II · Bosch Portugal

Cloud data engineer · Portugal · Open to conversations

Data platforms
people can trust.

I turn complex industrial and cloud data into reliable systems—combining Azure, Databricks, Spark and an engineer's instinct for how things fail.

Connect directlyPick your channel
Interactive system map

Select a layer to see how I design reliability into the platform.

SYSTEM.DESIGN / EXPLOREReliable data flow
Select a node
NODE_01context.registered
Sources

Capture source meaning, ownership and event time before data begins to move.

Current roleData Engineer II · Bosch
Core stackAzure · Databricks · Spark
FoundationMechanical engineering
Status Building reliable systems
EXPERIENCE + EDUCATION

Engineering shaped across industry and academia.

Present and past organizations that shaped my path from physical systems to cloud data platforms.

01 / PROFILE

Beyond the pipeline.

My engineering career started with physical systems.

As a Mechanical Engineer in manufacturing and automotive environments, I learned to think in processes, constraints, reliability, optimization and measurable outcomes. That mindset eventually moved from machines to data.

Today, I apply the same principles to cloud data platforms—designing architectures, pipelines and data products that must remain observable, scalable and maintainable in production.

CAREER.EVOLUTION

One engineering mindset. A wider system.

  1. 01Mechanical engineering
  2. 02Industrial analytics
  3. 03Data engineering
  4. 04Cloud platforms
  5. 05AI-driven systems

02 / EXPERIENCE

Systems improve. The standard stays high.

A career across industrial operations, applied analytics and production data platforms—unified by reliability and measurable outcomes.

01
2025 — NOWLisbon · Remote

Bosch Portugal

Data Engineer II

Building and operating supply-chain analytics across a SAP-sourced Microsoft data estate, with a focus on data integrity, reliability and decision-critical reporting.

  • Production T-SQL, SSIS, SSAS and SQL Server Agent workflows
  • Root-cause analysis across cube processing and snapshot logic
  • Preventive data-quality checks for demand planning datasets
T-SQLSSISSSASSQL ServerData Quality
02
2023 — 2025Porto · Hybrid

Nordex Group

Data Engineer

Delivered legacy-platform migration work toward a modern Azure data stack and built lakehouse pipelines for operational wind-energy data.

  • Delta Lake Silver and Gold layers for analytical products
  • Up to 22% improvement in SQL and pipeline performance
  • CI/CD, schema controls, monitoring and production incident response
DatabricksSparkDelta LakeAzureScala
03
2022 — 2023Remote

Independent

Data / ML Engineer

Delivered self-directed data and machine-learning work while completing a postgraduate transition into data engineering.

  • Contributed fixes to the open-source Ivy ML framework
  • Built end-to-end data, analytics and ML workflows
  • Connected applied modelling with production engineering practice
PythonMachine LearningAnalyticsOpen Source
04
2018 — 2023Portugal · Global projects

Yazaki · SIMAN

Manufacturing Engineer

Designed and industrialized physical systems before moving from machines to data—developing a lasting instinct for constraints, traceability and measurable outcomes.

  • Applied linear regression to injection-tool cost estimation
  • Coordinated industrialization across international stakeholders
  • Used root-cause analysis and continuous improvement in production
Industrial SystemsOptimizationLeanApplied ML

03 / ENGINEERING PRINCIPLES

Good data engineering is invisible when it works.

The strongest systems make correctness feel ordinary—even when the machinery underneath is not.

01

Reliability

Failure should be visible, bounded and recoverable.

I design observability and operational ownership with the pipeline—not as a dashboard added after the first incident.

02

Simplicity

Complexity needs to earn its place.

The right architecture is the smallest system that preserves quality, scale and a credible path for change.

03

Trust

Data quality is a product capability.

Contracts, lineage, tests and accountable release gates turn technically valid data into information people can use.

04

Context

Engineering starts with the decision.

A technically elegant pipeline has little value unless it improves a real process, product or business outcome.

04 / SELECTED WORK

Projects as engineering decisions.

No screenshot gallery. Each case study explains the system, the evidence and the boundaries that make its claims credible.

02
PRODUCTION DATA PLATFORM · NORDEXProduction experience

Modernizing a platform without losing operational trust.

Migration work across a legacy Microsoft estate and a modern Azure lakehouse—connecting ingestion, Spark transformations, Delta layers, delivery controls and the operational practices needed to keep reporting dependable.

AzureDatabricksSparkDelta LakeADFAzure DevOps
Explore case study
03
SELF-HOSTED PRODUCT ENGINEERINGProduction platform · private infrastructure

Building cloud-like infrastructure at home.

A production Django platform and personal infrastructure lab used to practice secure ingress, reverse-proxy design, containerization, storage and operational automation—without exposing private network details.

DjangoDockerNGINXCloudflareGunicornTrueNAS
Explore case study
04
PUBLIC DATA ENGINEERING PROJECTPublic repository

Making renewable-energy data orchestration observable.

An end-to-end renewable-energy business-intelligence pipeline that uses Airflow to make ingestion, transformation and serving dependencies explicit and repeatable.

AirflowSnowflakePythonSQLDockerBI
Explore case study

05 / ARCHITECTURE PLAYGROUND

Some problems are easier to explain as systems.

Inspect a blueprint, then inject a failure and watch its operating controls respond. The market-intelligence view remains a design study—not delivered work.

SYSTEM.DESIGN / LAKEHOUSE

Lakehouse platform

A layered path from operational sources to trusted data products.

NODE_01Operational sources

Multiple operational source patterns required explicit schema and ingestion controls.

Click any component to inspect its responsibility.
SYSTEM.RESPONSE / INTERACTIVE RUNBOOK

Inject a failure. Inspect the response.

Choose an operating event and replay how contracts, orchestration, quality and release controls contain it.

01
ContractChange detected

The incoming schema fingerprint differs from the registered contract.

02
IngestionBatch isolated

The affected load is diverted from the trusted processing path.

03
LakehouseSnapshot held

Consumers remain on the latest validated version.

04
QualityOwner review

Mapping, tests and compatibility expectations must be updated.

05
ProductPromotion blocked

The release state stays visible until the contract is reconciled.

06 / CAPABILITY MAP

Expertise organized around outcomes.

Tools change. The durable capability is knowing how to combine them into a platform that can be trusted and operated.

DAILY ECOSYSTEM

The tools behind the outcomes.

A visual map of the platforms, languages and operating tools I combine in real data systems.

Microsoft AzureCloud
DatabricksLakehouse
Apache SparkProcessing
PythonEngineering
Apache AirflowOrchestration
Apache KafkaStreaming
SQL ServerData estate
ScalaEngineering
DockerDelivery
Azure DevOpsDataOps
01

Data Engineering

Designing the movement, transformation and operational ownership of data.

ETL / ELTData modellingBatch processingData qualityObservabilityGovernance
02

Cloud & Platforms

Choosing platform boundaries that match scale, ownership and change.

AzureAWSDatabricksAzure Data FactoryS3EMR
03

Processing & Storage

Building trustworthy layers from source records to analytical products.

Apache SparkDelta LakeSQL ServerSnowflakePostgreSQLParquet
04

Languages

Using the right level of abstraction for platform and data-product work.

PythonSQLPySparkScalaT-SQLDjango
05

DataOps

Making change safe through automation, testing and visible operations.

DockerAirflowAzure DevOpsGitCI/CDLinux
06

AI & Analytics

Applying ML where evaluation proves it adds value—and retaining the baseline when it does not.

Machine LearningFeature engineeringPyTorchScikit-learnEvaluationResponsible AI

07 / ENGINEERING NOTEBOOK

How I think about data platforms.

Architecture becomes more useful when the reasoning behind it is visible.

tiago-reis / engineering-notes.mdREAD ONLY

A sophisticated graph that cannot explain a late or incorrect result is weaker than a simpler system with explicit state, ownership and recovery.

08 / FOUNDATIONS

Built on engineering fundamentals.

A formal path from physical systems and optimization into modern data platforms, cloud architecture and machine learning.

2019

MSc Mechanical Engineering

ISEP · Instituto Superior de Engenharia do Porto

Specialisation: Industrial Management
2024

Postgraduate Degree · Big Data & Decision Making

ISEP · Instituto Superior de Engenharia do Porto

Data Engineering, Big Data & Analytics · Final grade 18/20
// CURRENT_FOCUS

Still learning at the edge of the platform.

01AI engineering02Modern data platforms03Distributed systems04Data + LLM architectures05Production ML

09 / START A SYSTEM CONVERSATION

Turn your platform problem into a useful brief.

Choose an outcome, constraint and priority. The result is a conversation starter—not a generic contact form or an automated estimate.

brief.compiler3 inputs · 1 system conversation
01 Choose the outcome
02 Name the constraint
03 Set the priority

Brief updated: Modernize a platform, Legacy estate, Reliability first.

SYSTEM.BRIEF / READY
Modernize a platform · Legacy estate

Move without breaking trust.

Create an incremental path from the current estate to governed, product-oriented data delivery.

  1. 01Source estate
  2. 02Contracted ingestion
  3. 03Governed layers
  4. 04Data products
DESIGN CONTROLIncremental migration boundary

Protect existing consumers while responsibilities move in controlled slices.

FIRST MOVEReliability first

Begin with the failure model, ownership map and minimum trustworthy release contract.

Conversation starter only · no automated estimate, scope or architecture approval