Hi, I'm Mateus.
Backend · Systems · Performance
I work primarily with C++ and Python on backend systems where performance, storage, and production behavior matter. Before moving into backend engineering, I spent several years closer to hardware and embedded systems. That background still shapes how I approach software end to end.
A few engineering problems I've worked through in production systems, including performance, data distribution, and extending existing serving paths. Some internal details have been generalized or omitted.
Architecture · Storage · Scale
I started by investigating OOM failures in a data-export path. Tracing the data further exposed the same full-dataset assumption on the serving side, which led me to evaluate alternative designs and prototype a local LMDB snapshot approach.
Performance · Production
A high-volume processing path was using sorted pagination even though its database access already provided the ordering it needed. I traced the extra work, moved the path to regular pagination after validating equivalent output, and saw average production runtime drop from ~0.65s to ~0.15s.
Architecture · Compatibility · Delivery
I led the serving-side work to support a new format without changing the behavior of existing traffic. With a tight first-release deadline, we classified the new inventory early and isolated its matching behavior, while deliberately choosing a smaller first release over a cleaner but much broader cross-stack change.
02Experience
Backend engineering for performance-critical production systems in C++ and Python.
C++ software for connected and embedded devices, spanning device communication, remote management, and performance work.
Python tooling, test automation, and CI infrastructure for automotive software.
For full employment history and education, see my resume or LinkedIn profile ↗.
I started in electronics and embedded systems, where software was always connected to something physical. Over time I moved toward backend and production systems, but I kept the same habit: I want to understand how the layers underneath behave, especially when performance or reliability depends on them.
Today I work mainly with C++ and Python. I'm particularly interested in distributed systems, storage, performance, and production problems that require tracing behavior across more than one layer.
I'm currently building more hands-on experience with Go and deepening my distributed-systems design knowledge. I also still enjoy the builder side of engineering and projects that bring software and hardware together.
04Contact
I'm currently open to backend and systems engineering opportunities, particularly roles involving performance, distributed systems, storage, or production-scale software.
Email me