SOCRATECH · Vol. III · № 47
a notebook of machines & minds
Section III · Curriculum vitae

A working timeline

Four roles across three Mexican cities — cloud backends, big data, fintech infrastructure, and now Ad Tech at Google. Read as one continuous apprenticeship, and as the groundwork for what I am building at Operand.
4ROLES
2022 · present
Mexico City, MX
— Chapter IV —
MMXXV
the present tense
July 2025 · present
Current

Technical Solutions Engineer

Google · Mexico City, MX

Ad technology integrations between enterprise customers and Google Cloud, plus analytical ETL pipelines that aggregate operational and advertising data into dashboards the ad-tech teams actually read. Tracing data-flow issues through product and integration layers until the cause stops being a mystery.

Python SQL Google Cloud BigQuery Cloud Storage
ongoing
— Chapter III —
MMXXIV
the platform year
April 2024 · 2025
Fintech

Software Engineer

Capital One — Kunai · Mexico City, MX

GraphQL client libraries in Go and Python, used across internal teams to pull from shared APIs. Polyglot microservices in Java, Python, and Go behind them. Profiling and load testing on the hot paths; Terraform and Docker on the deployment side. A crash-course in code review as craft.

Go GraphQL Python Java AWS Terraform Docker
~1 yr · 3 mo
— Chapter II —
MMXXIII
the data year
February 2023 · 2024
Data

Data Engineer

BMW Group — Luxoft · San Luis Potosí, MX

Big-data pipelines inside BMW's data estate. Hadoop MapReduce and PySpark on the batch side, Airflow DAGs holding the orchestration together, and Go worker services on a pub/sub event bus for the streaming half. Learned that most "data problems" are really ownership problems with a schema on top.

PySpark Airflow Hadoop Go Python PostgreSQL Elasticsearch
~1 yr · 2 mo
— Chapter I —
MMXXII
the first post
February 2022 · 2023
First post

Software Engineer

Groups360 — Luxoft · Guadalajara, MX

Payment microservices in Python and Go on RabbitMQ and Redis, plus an SDLC analytics pipeline that fed Jira and Git metrics through Elasticsearch into Kibana dashboards. Stripe integrations on the money side. The year that convinced me architecture is mostly the art of deciding what not to build.

Python Go RabbitMQ Redis Kubernetes AWS PostgreSQL
~1 yr
— origin of the record —
A dated engagement on the record
Paper clip marks role type
Primary tool / language
— Endnote —

The tools at hand

The working kit accumulated across the four roles above. The emphasised items are the ones I reach for by default.

Languages
  • Go
  • Python
  • C / C++
  • SQL
Systems & OS
  • Linux
  • Docker
  • Kubernetes
  • Terraform
Data stores
  • PostgreSQL
  • Spanner
  • BigQuery
  • Redis
  • Elasticsearch
Cloud & orchestration
  • Google Cloud
  • AWS
  • Kafka
  • Airflow