Gabriel Silva

Software Engineer · Solution Architect · Founder

Building reliable software where backend, cloud and product meet.

I design and operate systems end to end. Six years spent close to production, owning the whole path.

Get in touch View projects GitHub LinkedIn
Gabriel Silva

About

A generalist who went deep on systems.

I am a software engineer, solution architect and founder based in Brazil. I started in full stack work, moved deep into infrastructure, and now lead engineering across the entire stack.

Today I run Medlupi, a healthcare platform I took from an empty repository to paying clinics. I own the backend, the frontend, the cloud, the DevOps and the product. Along the way I have led teams of more than ten people, shipped systems that serve millions of daily requests, and collaborated with teams across Europe and India.

I care about the parts that do not demo well. Reliability, cost, clear boundaries, and code the next engineer can actually own. I am now looking for international Software Engineer roles where those things genuinely matter.

Principles

How I think about engineering.

  • Ownership

    I build things end to end and stay responsible for how they behave once they reach production.

  • Simplicity

    I reach for boring technology first and add complexity only when the problem clearly demands it.

  • Performance

    I measure before I optimize, then spend effort where it changes the experience or the bill.

  • Observability

    Every production system should be able to explain itself through metrics, logs and traces.

  • Scalability

    I design systems that absorb growth in traffic and in team size without a painful rewrite.

  • Learning

    I stay curious, study deliberately, and share what I learn with the people around me.

Experience

Where I have done the work.

  1. Founder & Full Stack Engineer

    Medlupi2025 — Present

    Problem. Clinics run on fragmented tools that fit their workflow poorly and rarely respect local health data law.

    Built. The whole platform from scratch. Scheduling, electronic health records, digital prescriptions and patient management, plus automated WhatsApp reminders and an AWS environment tuned for security and cost.

    Impact. Went from MVP to first paying clinics in under three months, running product, engineering, infrastructure and sales alone.

    • Next.js
    • NestJS
    • PostgreSQL
    • Prisma
    • AWS
    • LGPD

  2. Tech Lead

    Scoder2023 — 2025

    Problem. A studio acting as the technology arm for many companies needed systems that could grow fast without falling over.

    Built. Led an international telecommunications project for a network of schools, then designed and led a platform that now serves more than fifty partner companies and millions of accesses per day.

    Impact. Cut AWS spend by around R$5k per month through infrastructure as code and observability, while mentoring the engineers on the team.

    • TypeScript
    • Node.js
    • AWS CDK
    • Observability
    • Leadership

  3. DevOps Engineer

    Teceo2023

    Problem. A fashion startup connecting brands with retailers was carrying high infrastructure costs and limited room to scale.

    Built. Migrated the entire estate from DigitalOcean to AWS, provisioning Kubernetes, Traefik, Elasticsearch, RabbitMQ, Redis, four databases and several applications with AWS CDK, plus site to site VPN links to partners such as TOTVS.

    Impact. A reproducible, cheaper platform and a cleaner path to scale, with the whole environment described as code.

    • AWS CDK
    • Kubernetes
    • RabbitMQ
    • Redis
    • Elasticsearch

  4. Full Stack Engineer

    Eureka Labs2021 — 2023

    Problem. A software house serving large national companies had strong teams that rarely shared what they learned.

    Built. Worked across design, frontend and backend, then founded an internal R&D group called Shoulders that produced shared libraries, standards and study groups. Became a reference backend engineer and moved into the DevOps team.

    Impact. Raised the engineering baseline across teams and found the infrastructure work that shaped the rest of my career.

    • React
    • Node.js
    • Backend
    • DevOps

Selected projects

Systems, not screenshots.

Medlupi

A healthcare SaaS built and operated solo.

Problem
Small clinics needed one dependable system for scheduling, records and billing that also respected Brazilian health data law.
Architecture
A Next.js client talks to a NestJS API backed by PostgreSQL through Prisma. Reminders and other slow work run off a queue so requests stay fast. Everything is deployed on AWS with security and cost in mind.
Challenges
LGPD compliance, tenant isolation, and keeping the bill small while operating the full stack as one person.
Impact
From empty repository to paying clinics in under three months.
  • Next.js
  • NestJS
  • PostgreSQL
  • Prisma
  • AWS

Cloud cost & infrastructure

Treating the bill as a reliability signal.

Problem
Rising cloud spend and environments that were hard to reproduce and expensive to keep idle.
Architecture
Kubernetes workloads behind Traefik, provisioned entirely with AWS CDK. Right sized compute and data tiers, with metrics wired in to attribute cost and failure to the services that cause them.
Challenges
Migrating live systems without downtime, keeping infrastructure changes reviewable, and connecting partners over site to site VPN.
Impact
More than R$20k per month saved for one AWS client, and a repeatable path to scale for the rest.
  • AWS CDK
  • Terraform
  • Kubernetes
  • Traefik
  • Prometheus

Private telecom network

Secure connectivity for a network of schools.

Problem
A group of schools needed private, controlled communication across sites, with several vendors involved on different continents.
Architecture
A private SIM network with centralized policy and secure links between sites, coordinated across partners in Europe and India.
Challenges
Aligning multiple companies, time zones and standards into one coherent, secure design.
Impact
A working private network foundation and the trust to keep leading the wider program.
  • Networking
  • Security
  • Architecture
  • Coordination

Go microservice rewrite

Ten times faster on the same hardware.

Problem
A JavaScript microservice on a hot path was slow and hungry for memory as traffic grew.
Architecture
Rewrote the service in Go with careful attention to allocations and concurrency, keeping the same external contract so nothing downstream changed.
Challenges
Matching behavior exactly while profiling to find where the time and memory actually went.
Impact
More than ten times faster and far lighter on memory, with headroom to spare.
  • Go
  • Profiling
  • Concurrency

Toolkit

Tools, organized by what they do.

Languages

TypeScript · Go · JavaScript · Python

Backend

Node.js · NestJS · REST · Event driven services

Infrastructure

Docker · Kubernetes · Traefik

Cloud

AWS (2x certified) · DigitalOcean

Messaging

Kafka · RabbitMQ · SNS & SQS

Databases

PostgreSQL · Redis · Elasticsearch · Prisma

Observability

Prometheus · Grafana · Elastic · New Relic

DevOps

AWS CDK · Terraform · GitHub Actions · GitLab CI

Architecture

Distributed systems · Multi tenant SaaS · Solution architecture · LGPD

Contact

Let us talk about the systems you are building.