SPS. PulidoOpen to talk

Santiago Pulido//Backend engineer//Index

Java · Spring · AWS

I build backend systems that move money and hold up when someone tries to break them.

I'm Santiago, a backend engineer who started out in infrastructure and SRE. These days I build payment processing on Java, Spring and AWS. I also hold a degree in Information Security, so I think about how a system can be broken while I design it.

Role
Sr. Software Engineer
Focus
Java · Spring · AWS
Domain
Payments & cloud
Base
Mendoza, AR · UTC-3
Readout● Nominal

Years shipping

6+

Since 2020, from SRE to backend

Runtime of choice

Java 21

Spring 6 · Jakarta EE · GraalVM

Degree

InfoSec

B.Sc. Information Security · 2026

Sec. 02//Log

Six years, from racking servers to running payment systems.

Entries 05
Order Newest first
  1. 2025 — Now

    Active

    itti

    Sr. Software Engineer//WEPA team · Remote, Paraguay

    • Design and build payment processors and cash desks for WEPA, a bill-payment platform.
    • Async, decoupled transaction processing on SQS so payments hold up during traffic peaks and third-party outages.
    • Go services on AWS Lambda, REST API design, data modeling on PostgreSQL and DynamoDB.
  2. 2021 — Now

    Active

    GUDCOD

    Founder//Software studio

    • Multi-tenant ERP for manufacturing and logistics SMBs: one isolated database per client, distributed cache, RBAC with JWT and API keys.
    • End-to-end custom software for clients in production: architecture, backend, UI, data and CI/CD.
  3. 2022 — 2025

    Slingr

    Fullstack Developer

    • Migrated the core backend from Java 11 / Spring 5 to Java 21 / Spring 6 / Jakarta EE.
    • Co-led the frontend rewrite from DurandalJS to Angular 17+.
    • CI/CD pipelines with Docker and Kubernetes on GCP, plus a steady cut of tech debt.
  4. 2021 — 2025

    Toroide IT

    Fullstack & DevOps//Part-time

    • Web apps and multi-environment CI pipelines for builds, tests and deploys.
  5. 2020 — 2022

    VAN P

    SysAdmin / SRE

    • Designed and rolled out networks for hundreds of client connections across several cloud and VPS providers.
    • Linux and Windows server administration, plus internal automation tooling.
EducationB.Sc. Information Security // Universidad Siglo 21 // 2026

Sec. 03//Work

Selected builds: agents, platforms and tools that make other tools.

Index PRJ-001 → PRJ-004
PRJ-001 // 2025Thesis

Self-replicating vulnerability remediation agent

Native agents compiled with GraalVM spread across a cloud environment, find vulnerabilities and fix them on their own. A central platform tracks and steers the fleet.

  • Java 17
  • GraalVM
  • Spring Boot 3
  • MongoDB
  • Angular
  • AWS
View source
PRJ-002 // GUDCODClient work

Multi-tenant ERP

Operations backbone for manufacturing and logistics SMBs. Each tenant gets its own database; access is enforced by roles, tokens and API keys.

  • Java 17
  • Spring Boot 3
  • MongoDB
  • Hazelcast
  • RBAC
PRJ-003 // 2025R&D

Real-time voice assistant

Talk to it and it gets things done. It calls custom tools over MCP and hands longer jobs to n8n workflows.

  • React
  • MCP
  • n8n
  • Realtime voice LLMs
PRJ-004 // 2025R&D

Fullstack app generator

A visual builder: describe the models, pick a stack, and it generates the endpoints and the UI.

  • NestJS
  • Angular
  • MongoDB
  • Docker

Sec. 04//Stack

Tools I trust in production, and the lab where I break things first.

Inventory25 items

Backend

  • Java 8–24
  • Spring Boot / Data / Security
  • Go
  • Node.js
  • NestJS
  • Python

Data & messaging

  • PostgreSQL
  • DynamoDB
  • MongoDB
  • MySQL
  • AWS SQS
  • Hazelcast

Cloud & ops

  • AWS · Lambda · ECS
  • GCP
  • DigitalOcean
  • Docker
  • Kubernetes
  • GitHub Actions · Jenkins

Frontend

  • Angular 13–19
  • Next.js
  • TypeScript

Security

  • Automated remediation
  • RBAC · JWT · API keys
  • Kali
  • Nessus · OpenVAS
Lab // 01

Self-hosted Kubernetes

kubeadm, Gateway API on Envoy, Harbor and my own CI/CD. I'd rather own the cluster than git-push to a PaaS.

Lab // 02

Local LLMs

Running and tuning open models on my own hardware: quantization, KV cache, speculative decoding.

Lab // 03

Agent automation

Unattended coding-agent pipelines driven from the shell: specs in, retries on failure, diffs out.

Sec. 05//Contact

Got a system that needs to hold? Let's talk.

New messageForm // 01
What are you building?

Human check *