Skip to content
Eduardo Montilva
Email me the CV
Senior Software Engineer · Latam · Remote · UTC-4

I build the backendsystems, data pipelinesand infrastructurethat products run on.

Backend, Distributed Systems & Applied AI. These days that means event-driven services in Kotlin, Java and TypeScript, Python pipelines that ingest millions of records, and the GKE clusters all of it is deployed on.

LinkedInGitHubDownload the CV
The front panel of a Heathkit EC-1 educational analog computer: rows of coefficient potentiometers, red and black patch sockets, and a voltmeter.
1960. A Heathkit EC-1 analog computer: the problem is wired up with patch cords and the answer is a voltage.Michael Holley · Computer History Museum · public domain
In software7 yearssince the first engineering role
CurrentlyBeast IndustriesSoftware Engineer II
Based inLatam · UTC-4remote, overlapping with the Americas
In production3 productsbuilt and run end to end
Ask

In a hurry? Ask the page.

A small assistant answers questions about my background, using only what is on this page. When the page does not cover something, it is told to say so instead of guessing.

Download CV

Ask anything about Eduardo's work. Answers come from a language model reading this page, so treat them as a summary rather than a quote.

Press Tab to accept the suggested question, Enter to send.

About

An electrical engineer who ended up in backend.

Most of what I build is event-driven: services that react to a queue, the pipelines that load their data, and the Kubernetes setup they are deployed on. I write Python, TypeScript, Java and Kotlin day to day, Rust when something has to be fast, and a lot of SQL.

At Beast Industries the Python platform the data and ML work runs on is my design, and so are the documents behind several of the team's storage and search choices. A good part of each day goes to other people's pull requests and to getting new backend engineers up to speed.

I trained as an electrical engineer at Universidad Simón Bolívar and spent my first years splitting time between power systems consulting and software. Software won, but the power systems side never quite left. It is still what I build for fun.

What I work on
Data pipeline diagramEvents, video data and transcripts flow into a Python and Databricks pipeline, then through embedding and model work, and out to internal services and user-facing products.eventsvideo datatranscriptspipelinesPython · DatabricksembeddingsGPU batch · NLPservicesproductsmillions of records / day
How the assistant above finds an answer
A wall of round gauges and strip-chart recorders in a 1945 control room.
1945. Round gauges and strip-chart recorders on a control-room wall.Historic American Engineering Record · Library of Congress · public domain
Products

Three things I run in production.

I built and run each of these on my own: the backend, the data, the billing and the page that sells it.

  • OriginStat

    live
    originstat.com ↗

    Cookieless web analytics that ties every visit to the revenue it produced.

    A customer's payment provider sends its webhooks here, so the sources report does not stop at "1,200 visits from X": it says how many of those visitors bought, for how much, net of refunds, and which channel the churned ones came from. Polar, Stripe, Lemon Squeezy, Paddle and Dodo arrive at one endpoint. The ingest path runs in under a millisecond of CPU with no database call, and the whole thing lives on Cloudflare.

    Cloudflare WorkersAnalytics EngineD1Durable ObjectsHono
  • SocialEar

    live
    socialear.app ↗

    Social listening across Reddit, Hacker News, Lobsters, YouTube, Instagram, TikTok and X.

    Watches the places a product gets talked about, reads every match for sentiment and intent, and sends an email or Slack alert while the thread is still open. Each source is polled once and shared by everyone watching it, which is what makes it affordable; YouTube is read by what is said in the captions. Server-rendered on Cloudflare, with a public REST API and its own credit metering.

    Cloudflare WorkersD1QueuesDurable ObjectsWorkers AIPython
  • bakepdf

    live
    bakepdf.app ↗

    Merge, split, compress, sign and convert PDFs in the browser, without uploading them.

    The PDF engine runs client-side, including redaction, so there is no upload to wait for, no server CPU per request and nothing to delete afterwards. Chat, summarise and OCR need a model, so those three go through a Worker. Files a user chooses to save are stored as ciphertext the server cannot read.

    TypeScriptCloudflare WorkersD1R2pdf-libpdf.js
Experience

7 years building software, after training as an electrical engineer.

  1. July 2024 - Present

    Remote

    Beast Industries (@MrBeast)

    Software Engineer II

    • Senior-scope engineer on a team of about fifteen, reporting to the Director of Engineering and the Director of Data, AI and ML. Most days start with other people's pull requests. New backend hires usually get me as the person who walks them through the codebase, and questions about Python, Java or the ML side tend to end up with me.
    • The company's Python codebase started as an empty repository I was handed. I chose the architecture, how services are laid out, the CI and how they deploy. Today it holds twelve microservices that process thousands of videos, posts and accounts a day, the embedding jobs, and the collection services that feed them through rotating proxy pools. Databricks takes the heavier batch work.
    • The embedding pipelines are mine. They used to call third-party model APIs one record at a time and topped out near 60,000 records a day. Moving inference onto our own GPUs in batches got that to about 2 million. Transcript analysis, topic classification, sponsor detection and brand-safety scoring all sit on top of those embeddings.
    • Took an AI image and thumbnail generation service from an empty repository to production: model integration, the async job queue, storage and the public API. It handles hundreds of jobs a day and has been stress-tested at a thousand. I got per-job latency down from around 90 seconds to 30.
    • Built the services that aggregate and estimate metrics over millions of videos and channels, and a retrieval-augmented generation service that lets more than 2,000 users ask questions of the analytics data in plain language.
    • Wrote the design documents behind several of the team's infrastructure choices and saw them through to adoption: Qdrant for vector search, Manticore and Quickwit for full-text search, and the schemas and data contracts for ClickHouse, MongoDB and Cloud Spanner.
    • Design event-driven systems on RabbitMQ, backed by PostgreSQL, Cloud Spanner or ClickHouse depending on whether the workload is transactional or analytical. Some of the consumers I reworked now handle up to 100x more messages per second than before, and a set of queries that used to run for over ten seconds come back in 300 ms or less.
    • Maintain roughly 70 Helm-deployed services on GKE through Argo CD. About twenty of them run on a deployment pattern and architecture I designed. Moving service-to-service traffic onto private VPC networking cut the network bill sharply. The infrastructure-as-code, ingress, certificate and DNS automation and the OpenTelemetry tracing are mine as well.
    • Built the observability around the payments integration: status-code tracking for the payment provider, exception capture, and alerts to email, Slack and Discord. I am on the on-call rotation and respond to production incidents.
    • Write the Kotlin authentication services (token issue and refresh, session handling) that the web and mobile clients sign in through, and work across a large Java and Kotlin monorepo covering analytics, data collection, ranking, outlier detection, search, payments and alerting. Currently adding NestJS and TypeScript services alongside it.
    • Work on the Next.js frontends and the React Native app when a feature needs someone to take it end to end.
  2. November 2022 - July 2024

    Remote

    Talamo Iberica

    Backend Developer & Project Manager

    • Designed and built a blockchain platform with services in TypeScript, JavaScript, Python and C++, including the security and peer-to-peer communication layers.
    • Wrote the REST APIs and WebSocket protocols (Node.js, Express, PostgreSQL) carrying peer-to-peer traffic and client-to-backend communication.
    • Split the system into microservices to handle several thousand requests a day from the platform's users.
    • Planned sprints, task breakdown and workflow for a team of more than 10 developers.
    • Set up the CI/CD pipelines used to deploy blockchain nodes and APIs.
  3. February 2019 - November 2022

    Remote

    Freelance / Private Contract Work

    Software Engineer

    • Delivered backend systems for e-commerce, blockchain and SaaS clients using Python (FastAPI, Flask), Node.js with TypeScript, Java, C++ and some Go.
    • Designed relational and document schemas across PostgreSQL, MySQL and MongoDB.
    • Built the data acquisition pipelines that fed downstream machine learning models.
    • Trained and shipped models in production: CNNs for image classification, RNNs for text generation, regression models, and transformer-based language models.
    • Set up CI/CD pipelines on AWS.
    • Wrote React hooks and components for data fetching and state, working with the clients' frontend developers.
  4. February 2019 - July 2022

    Contract

    Independent Consultant

    Electrical & Power Systems Engineer

    • Modeled and simulated the SIEPAC Central American transmission network (100+ busbars, 15 substations) in DigSILENT PowerFactory and ETAP, running AC and DC load flow studies.
    • Wrote optimal power flow algorithms in Python and MATLAB, including nonlinear and MINLP formulations with equality and inequality constraints.
    • Developed stability control strategies for synchronous generators, motors, wind turbines, photovoltaic systems and EV charging stations.
    • Designed the low-voltage distribution for a residential building inside the TACOA substation in La Guaira: short-circuit calculations, panel sizing and cable sizing.
    • Built transmission line and tower models in PLS-CADD and PLS-Tower, with protective device coordination.
    • Designed photovoltaic systems and simulated them in Simulink under realistic operating conditions.
  5. December 2018

    Universidad Simón Bolívar

    B.Sc. Electrical Engineering

    Thesis: Analysis of the Electrical Interconnection System of the Central American Countries (SIEPAC Network)

Four steel transmission towers carrying high-voltage lines across desert hills near Hoover Dam.
2003. The Hoover Dam transmission line crossing the desert hills.Douglas M. Edwards · Historic American Engineering Record · public domain
Projects

Mostly where power systems and software meet.

Things built outside work. The three power-system projects are about one picture: solving the flows across a network, estimating its state with a graph network, and choosing which machines run.

Transmission networktwo generators, two loads, one corridor at its limit
Transmission network one-line diagramEight busbars in a meshed network. Two generators feed power through the lines to two loads, with one corridor carrying more than the rest.generationpower flowat its limitload
Skills

The same handful of methods, on both sides of the work.

Solving a power flow and training a model come down to the same problem: descend a surface to its minimum. Here are three of the methods I use, released from the same starting point.

Optimizationsteps to converge
Three optimizers converging on the same minimumContours of a badly conditioned quadratic. Gradient descent zigzags across the valley in 32 steps, Adam curves along it in 20, and a damped Newton method reaches the minimum in 5.sgd · 32adam · 20newton · 5
Languages
PythonJavaKotlinTypeScriptJavaScriptRustCC++GoSQLMATLABBash
Backend
SpringNestJSFastAPIFlaskExpressNode.jsRESTWebSocketsgRPCRabbitMQEvent-drivenMicroservices
Data
PostgreSQLCloud SpannerClickHouseMySQLMongoDBRedisDatabricksBigQuerySupabaseQdrantManticoreQuickwit
ML
PyTorchTensorFlowStable-Baselines3EmbeddingsRAGNLPCNNsRNNsTransformersGNNs
Optimization
Newton-RaphsonInterior pointL-BFGSSGDAdamConvex optimizationNonlinear programmingMINLPGenetic algorithmsOptimal power flow
Cloud
GCPAWSKubernetesHelmArgo CDDockerTerraformCI/CDOpenTelemetryGrafana
Frontend
ReactNext.jsVueReact Native
Engineering
DigSILENT PowerFactoryETAPPLS-CADDPLS-TowerSimulinkAutoCAD
Spoken
Spanish (native)English (professional)
Three tall current transformers with ribbed porcelain insulators in the Hoover Dam switchyard, with steel lattice structures around them.
2002. Current transformers in the Hoover Dam switchyard. They step line current down to something a meter can read.Deborah Dobson-Brown · Historic American Engineering Record · public domain
Contact

Open to backend, infrastructure and applied AI work.

I work remotely from UTC-4. Leave your address and the CV lands in your inbox, with mine as the reply-to. A line about what you are building helps.

LinkedInGitHub
Email
eduardomontilvag@gmail.com