Backend · Cloud · Platform

Systems that keep moving under load.

I build backend and cloud systems for work that cannot be left to chance: events that must not be lost, workloads that must recover, and data flows that need to remain understandable as they grow.

04selected systems
02architecture case studies
01live platform

Engineering principles

Built around the operating conditions.

DurabilityFailure recoveryObservabilityCost awarenessLeast privilege

Case-study evidence

Proof behind the architecture.

Historical, sanitized evidence from controlled runs; no live telemetry or private data is exposed here.

VulnFlow

Reliable processing

190 findings returned through paginated results; replaying an accepted event preserved one terminal result, while a controlled retry reached the DLQ and recovered through a reviewed redrive.

BenchLab

Isolated execution

Queue-backed execution keeps long-running work outside the API, with language-specific containers and an authenticated callback boundary.

Attack Surface Mapper

Discovery pipeline

Tested Python workflow for discovery, validation, correlation and reporting, with evidence-aware scoring and structured outputs.

JobRadar

Deterministic ingestion

Multi-source ingestion with reliable adapters, explainable ranking and content-hash deduplication.

Professional experience

Current role

Junior Software Developer

Dinamic Area Software S.L. | 4 Aug 2025 - Present

Develop Java/Spring Boot backend services and REST APIs for production applications; contribute to database operations, CI/CD and deployment; and work directly with clients to clarify requirements and validate delivered solutions.

Direction

Build for the failure path, not just the happy path.

I want to work on cloud platforms that process large volumes of data without becoming fragile or opaque. That means thinking about throughput, recovery, observability, cost and security from the first design decision—not adding them after the system is already in production.

My focus is backend, cloud and platform engineering: the infrastructure and services that let product teams move quickly while the system remains reliable when traffic, data and operational pressure increase.

Contact

Let’s talk about the system behind the product.

For roles or technical conversations in backend, cloud and platform engineering, email me at gabrivacarog@gmail.com or connect at linkedin.com/in/vacarogoytiagabriel.