Lima, PeruMechanical engineer → software
Mechanical engineer building software systems for real operational processes.
I design domain models, REST APIs and the interfaces on top of them — the internal platforms that replace spreadsheets for commercial proposals, service planning and cost estimation. Shipped to production, used daily, deployed on Azure.
Profile
Four projects, two of them running inside a company. Where the code is proprietary I show the problem, the architecture and the outcome instead — never the source.
Open-source platform for commercial proposals and service planning.
The system I would have built if the two I shipped had been designed as one from the start. Proposals that get revised, priced and audited, then turned into a plan with work fronts, sized resources and requirements — one domain instead of two that have to be reconciled. Written from scratch on my own time, in Django rather than the FastAPI I already knew, and in the open so the reasoning is inspectable.
Architecture · modular monolith
Commercial
Everything about what was offered, at what price, and when it changed.
Internal systems · problem, architecture and impact only
Internal platform for commercial management and proposal tracking.
An internal application for managing commercial activity and following proposals through their lifecycle. It reached production, is used by dozens of people across the organisation, and was a finalist in the Innovation Awards 2026.
Internal platform for service planning and resource sizing.
An internal application for planning services: defining work fronts, sizing the resources each one needs, and generating the resulting requirements. Built on the same backend foundations as MIRA, for the execution side of the business.
Cost estimation for services and proposals, built on historical data.
Software and data engineering in one project: extract and transform historical service and proposal records, model them relationally, and use that history to estimate the cost of new work — instead of starting each estimate from a blank sheet.
The tools I use week to week — not a logo wall, and no invented proficiency numbers.
Where most of my work happens: modelling a domain, then exposing it carefully.
Enough to ship the interface myself, and to keep it typed and small.
Relational modelling and the unglamorous work of making historical data usable.
Getting systems deployed, authenticated and repeatable.
One company, one direction of travel: closer to the software every year.
Engineering Intern — FSE & LCS Proposals
October 2025 — present
Lima, Peru
Hired as an intern on the proposals team and ended up building the software it runs on: the data pipelines first, then two internal systems that went to production.
Pontificia Universidad Católica del Perú
The thesis, in short
A Python pipeline that turns ordinary photographs into a temperature field. It tracks how a printed pattern appears to shift when seen through hot air, then works backwards through that distortion to recover the temperature that caused it — image processing, numerical methods and a lot of NumPy, written as software rather than as a one-off script.
Certifications
Formal grounding for work already shipped — the systems came first.
I trained as a mechanical engineer at PUCP and finished first in my class. What I actually enjoyed was the part where a messy physical or operational problem gets written down precisely enough to be solved — which turned out to be a description of software.
At Metso that shift became my job. I started automating routines that ran on spreadsheets, and ended up designing and shipping internal systems used across commercial and service planning: domain models, REST APIs, React front ends, and the cloud plumbing that keeps them running and authenticated.
I like building things, and I like understanding the whole path — from the process someone is actually doing today to the schema, the API and the deployment. Right now that means going deeper on backend architecture and formalising cloud with Azure certifications, while building Malachite in the open.
If you are building internal platforms, data-heavy backends or moving operations off spreadsheets, I would like to hear about it.