role
Software Engineer
name
summary
Backend, frontend, architecture, and cloud for products that must scale with reliability.
activity / github
1,147 public contributions in the last year.
01 / about
Software Engineer with a path across backend, architecture, and DevOps, building platforms that must scale with reliability — credit, payments, delivery, telecom, video, and data-oriented products. I work end to end: from framing the problem and shaping the solution through implementation, observability, and production support. I am a generalist with judgment: choose the right tool for the challenge, keep architecture maintainable, and ship closely with product, design, and operations. I use generative AI tools as day-to-day leverage — to accelerate exploration and delivery — while owning trade-offs, quality, and what actually ships.
02 / experience
At Nuvemshop I evolve the credit platform — from offering and management through day-to-day operations. The work spans backend and frontend: I build scalable, reliable features, integrate partner APIs for the credit engine (system communication, data exchange, and automation of analysis and approval), and develop the credit frontend with React, TypeScript, Figma, and Playwright alongside design. In a lean squad with product, design, and operations, I also ship internal back-office tools that improve processes and speed up value delivery. When production breaks, I investigate with Datadog (metrics, logs, and root cause) and use generative AI tools as leverage in the development workflow — while still owning quality and what reaches the user.
TypeScript · Node.js · React · Figma · Playwright · PostgreSQL · Redis · AWS · Datadog
As a software architect I designed and implemented food-delivery solutions as microservices on AWS, with constant attention to scale, performance, security, and maintainability. A core part of the role was turning business needs into technical decisions: interviews, refinements, and alignment with stakeholders, producing clear specs for the team. I supported tech leads on coding standards, documentation (diagrams and guides), continuous integration, and agile practices. In critical moments I joined squads hands-on — legacy systems, complex integrations — helping unblock high-priority deliveries without losing the architectural thread.
NestJS · Node.js · TypeScript · Docker · MongoDB · PostgreSQL · Redis · Elasticsearch
On Pagar.me’s SRE team I worked on online payment systems under real availability and scale pressure. Day to day mixed architecture, development, and infrastructure evolution for distributed applications — including supporting squads on Elasticsearch cluster design and operations. I automated provisioning and delivery with Terraform, Packer, Ansible, and Docker on AWS, always aiming at the same outcomes: performance, reliability, and room to grow without production surprises.
Python · JavaScript · Go · C# · AWS · Terraform · Packer · Ansible · Docker
At Nokia I integrated systems for telecom operators: developing, provisioning, orchestrating, and configuring solutions that had to talk across heterogeneous environments. I worked on third-party IoT integrations and ETL pipelines with Greenplum and MySQL, connecting data sources to operational flows. To cut manual work and risk, I automated Linux environments with Ansible and Shell Script, applying cloud practices, Git, Elasticsearch, and design patterns aimed at scale and maintainability.
Packer · Ansible · Shell Script · Linux · MySQL · Greenplum · Elasticsearch · Git
On Globo.com’s video platform I built and maintained backend services and APIs for live and on-demand delivery, focused on performance, scale, and resilience — where latency and stability truly matter. I also contributed to DevOps on automating and improving CI/CD pipeline efficiency, shortening the path from code to production. The work spanned microservices and distributed systems, with a data, cache, and load-balancing stack (PostgreSQL, MongoDB, Redis, Elasticsearch, Nginx) on top of Python, Node.js, and Docker.
Python · Node.js · JavaScript · Redis · Docker · PostgreSQL · MongoDB · Elasticsearch · Nginx
At Neemu I worked on the Big Data team building data-acquisition services for scalable, distributed systems — foundations that must absorb volume without losing reliability. I also joined DevOps, automating routines, improving continuous delivery/deployment pipelines, and managing AWS resources. Day to day mixed Node.js and JavaScript with MySQL, PostgreSQL, MongoDB, and Redis, plus Shell Script on Linux, Docker, and Git. I applied microservices, design patterns, and cloud practices so performance, scale, and maintainability stayed at the center of the decisions.
Node.js · JavaScript · MySQL · PostgreSQL · MongoDB · Redis · Docker · AWS · Shell Script
At INdT (Nokia Institute of Technology) I was on the Cloud & Backend team developing backend services and mobile applications. I built scalable REST APIs integrated with MySQL, using Node.js, JavaScript, Java, and C++ depending on the problem. Development and production ran on Linux, with heavy Shell Script use for automation. Projects demanded close collaboration with other teams, agile practices with Scrum, and continuous improvement of architecture and processes — with Git and design patterns keeping the codebase maintainable.
Node.js · JavaScript · Java · C++ · MySQL · Linux · Shell Script · Git
03 / skills
Backend & APIs — Node.js, TypeScript, NestJS, Python, Go, C#, REST, Microservices
Frontend — React, TypeScript, Playwright, Figma
Architecture — Clean Code, Clean Architecture, Design patterns, Distributed systems, Scalability, Resilience
Cloud & DevOps — AWS, Docker, Terraform, Packer, Ansible, CI/CD, Linux, Shell Script
Data & Observability — PostgreSQL, MySQL, MongoDB, Redis, Elasticsearch, Datadog, Metrics, Logs