Skip to content

SOFTWARE ENGINEER / CHILE / EST. 2018

FULL STACK / DEVSECOPS / PLATFORM ENGINEERING

BUILD.RECOVER.SECURE.

From source code to production infrastructure. I build platforms, recover legacy systems and design security controls that hold up beyond the diagram.

FILE 001 / HOW I THINK

A system is more than its interface.

01

01 / PRODUCT

APIs · experience · data

02

02 / TRUST

Identity · privacy · tests

03

03 / OPERATIONS

Linux · containers · CI/CD

CONCEPTUAL SCHEMATIC — NOT AN ACTUAL NETWORK

INDEX / SELECTED WORK

Let the work speak.

Documented projects and responsibilities. The value lies in problems solved and engineering decisions, not in the number of frameworks.

01 / 05PUBLIC SECTOR / INCIDENT RESPONSE2026

Recover what others left behind.

Recovery and modernization of legacy platforms, exposed-secret remediation and critical vulnerability reviews.

LaravelPHPNode.jsDocker
Read engineering decisions

Context

Institutional systems with incomplete technical handover and requirements for continuity and auditability.

Technical review, source recovery, secret remediation and controlled deployment preparation.

Decisions

  1. Inventory dependencies and exposure before changing behavior.
  2. Move secrets out of browser bundles and limit service permissions.
  3. Document and verify infrastructure changes before deployment.

Evidence / status

Professional experience documented in the CV. No incident logs or internal outcomes are published.

02 / 05APPLICATION / PRIVACY2026

Security inside the codebase.

Laravel components for personal-data tokenization and auditable data-subject request handling.

PHPLaravelCryptographyARCOP
Read engineering decisions

Context

Personal data demands minimization, traceability and explicit authorization across services.

Reusable components for privacy flows and requests; adopting a package alone does not guarantee legal compliance.

Decisions

  1. Separate identification from authorization.
  2. Keep audit trails without storing sensitive values.
  3. Design explicit fail-closed behavior and tests.

Evidence / status

Public source repository for laravel-anonimizacion. Compliance depends on each implementation.

Explore source ↗
03 / 05PLATFORM ENGINEERING / DEVSECOPS2026

Infrastructure is also code.

Reproducible VPS infrastructure: Linux hardening, VPN access, encrypted secrets and isolated containers.

AnsibleWireGuardDocker rootlessSOPS + age
Read engineering decisions

Context

Infrastructure needs to be auditable and rebuildable without relying on undocumented manual changes.

Ansible roles, administrative access hardening and documented recovery procedures.

Decisions

  1. Automate with declarative and idempotent configuration.
  2. Reduce service privileges and exposure.
  3. Keep credentials outside version control and verify recovery.

Evidence / status

Professional work in progress according to the CV. The infrastructure repository remains private.

04 / 05DEVELOPER EXPERIENCE / TOOLING2026

Engineering worth repeating.

Hefesto Scaffold generates Laravel systems from manifests with administrative panels and embedded quality gates.

LaravelFilamentPHPFrankenPHP
Read engineering decisions

Context

Consistent project creation avoids repeatedly introducing errors in initial configuration, permissions and delivery.

Deterministic generation and a guided CLI architecture proposal.

Decisions

  1. Prefer deterministic, manifest-driven generation.
  2. Make tests and security part of the initial foundation.
  3. Distinguish existing capabilities from future integrations.

Evidence / status

Hefesto Scaffold remains in development. No unverified provisioning benchmarks are claimed.

05 / 05PRODUCT ENGINEERING / SaaS2024–2026

From physical objects to digital products.

KraftDo connects NFC/QR experiences to a SaaS product ecosystem with administration and integrations.

LaravelFilamentNFC / QRPython
Read engineering decisions

Context

Building a product that ties physical items to digital profiles and services.

Full Stack development, integrations, access control and document-processing services.

Decisions

  1. Separate commercial operations, identity and user assets.
  2. Use verifiable flows for external events and services.
  3. Protect user content with scoped authorization.

Evidence / status

Personal project described in the CV. No sales, user or uptime metrics are claimed.

Institutional systems are described at a high level to avoid disclosing internal configurations, people or infrastructure.

02 / APPROACH

BEYOND THE CODE

Architecture means deciding what not to risk.

Serious systems need explicit decisions about security, maintainability and operations. Tools change; judgment remains.

  1. 01

    Understand before changing.

    Inventory dependencies, exposure and behavior before modernizing or remediating.

  2. 02

    Automate what repeats.

    Manifests, pipelines and playbooks reduce manual changes and simplify recovery.

  3. 03

    Design for operations.

    Permissions, logging, backups and runbooks belong to the product.

03 / EXPERIENCE

From backend to platform engineering.

Professional work spanning business systems, government portals, original products and infrastructure.

  1. 2026 — NOW

    Software Engineering & DevSecOps

    Municipality of Graneros

    Application development, platform recovery and defensive security.

  2. 2026 — NOW

    Founder / Engineering

    Hefesto Studio · In development

    Tooling, reproducible architecture and software solutions.

  3. 2024 — 2026

    Founder / Full Stack

    KraftDo

    SaaS and NFC/QR experiences.

  4. 2023 — 2024

    Backend Developer

    Babel

    Public-facing services and Laravel integrations.

  5. 2020 — 2023

    Backend Developer

    Europa Press

    Editorial platforms, APIs and AWS services.

  6. 2018 — 2019

    Backend Developer

    Gux

    Legacy modernization and AWS deployments.