Available for selected projects

I build systems for real products.

Diagram showing commerce, payments, automation, and platforms. — I design the interface as the doorway into a system that must hold up under users, failures, and change.

Available for selected projectsSoftware Engineer / Product Builder — Colombia · international remote

Areas of work

Backend & APIs
Cloud
Fintech
Applied AI

I don't start from a template

I build around your business.

Every company has different processes, customers, and objectives.

I design solutions that adapt to them, not the other way around.

Your business should not adapt to software.

Software should adapt to your business.

→

Here is what I have already built.

Real products. Real problems. Real decisions.

Aether administration operational assistant

Aether / connected commerce

A store that works beyond the interface.

Buying is only one part of the problem.

Aether connects the customer experience with inventory, orders, operations, and intelligent assistance in one product.

An experience designed for buying

Less friction. More clarity.

Customers find what they need without navigating noise, unnecessary menus, or complicated processes.

Products, availability, and purchase belong to the same experience.

The catalogue can talk too

Search stops being a guessing game.

The assistant understands what the customer needs, finds real options in the catalogue, and helps them move towards a purchase.

It does not answer about a store. It is part of it.

On the other side of the purchase

What happens in the store becomes decisions.

Orders, products, inventory, and operational signals appear in one place.

The goal is not to show more information.

It is knowing what needs attention.

Operations can talk too

Ask instead of search.

Which orders are being processed?

Which products are low in stock?

Aether turns dispersed business information into direct, actionable answers.

One experience, two sides of the business

The customer buys. The business responds.

Aether connects both.

It is not only a storefront with an admin panel or a chatbot added on top. It is a product designed so customers, data, and operations work together.

02 / Selected work

Real projects, explained through technical decisions.

Each project explains the problem, ownership, and decisions that sustain the product. No invented metrics or confidential names.

Commerce + AI agents

Public demo deployed

Aether Commerce

Main flowAether Commerce

01Storefront
02Assistant
03Worker API
04D1 / Stripe

A bilingual commerce product with a storefront, admin, API, payments, and an assistant that can query products and operate the cart through explicit controls.

Open production demo

Problem: Build a store that demonstrated more than an interface: catalog, signed cart, checkout, admin operations, and conversational assistance connected to the real domain.
Ownership: Architecture and implementation of the monorepo, shared contracts, Worker API, D1, storefront, admin, Stripe integration, and AI service.
Decisions: The backend recalculates price and inventory; assistant mutations use cart tokens and idempotency; LangGraph coordinates intent, constraints, tools, validation, and audit in the validated Python path.
Status / outcome: The storefront, API, admin, and assistant Worker are deployed. The full FastAPI/LangGraph variant is Docker-validated; separate PostgreSQL and Redis hosting remains a documented next stage.

Fintech + payments

Private case

Flexible payments SaaS

Main flowFlexible payments SaaS

01Next.js
02Cloud Functions
03Firestore
04Stripe

A platform for splitting payments into configurable installments and coordinating transactional processes across the application and external services.

Problem: Model a flexible experience without losing consistency between the interface, payment state, and external events.
Ownership: Full-stack development and integration of the frontend with a serverless backend and transactional flows.
Decisions: Separate presentation, business logic, persistence, and events; process state changes through Stripe and webhooks.
Status / outcome: Presented without client identity, metrics, or a public link to preserve confidentiality.

Banking + microservices

Private professional work

Services for a banking platform

Main flowServices for a banking platform

01Angular interface
02Node.js services
03AWS Lambda functions
04Azure DevOps delivery

Work in a financial environment where every change had to coexist with delivery controls, clear ownership, and operational stability.

Problem: Evolve banking features in a distributed architecture without compromising traceability or reliability.
Ownership: Feature and service development and maintenance as an external contractor.
Decisions: Decoupled services, serverless functions, delivery automation, and careful change control.
Status / outcome: Production experience described at the permitted level, without internal organization data.

Cloud + financial operations

Private case

Financial platform on AWS

Cloud + financial operationsFinancial platform on AWS

01AWS
02SST
03Amazon RDS
04APIs

An architecture with APIs, authentication, relational data, and reproducible infrastructure for financial workflows.

Problem: Maintain a scalable, understandable technical foundation for an application with financial rules and data.
Ownership: Design the separation between frontend, backend, data, and infrastructure.
Decisions: Relational persistence on RDS, authentication, and automated infrastructure-as-code deployments.
Status / outcome: A publishable technical case without commercial information or unverified metrics.

01 / Value

I do not separate code from its operating context.

An interface is only one part of a product. My work connects architecture, business rules, data, integrations, and continuous delivery.

Backend and architecture

I design APIs, services, and data models around clear boundaries, critical flows, and long-term maintenance.

Node.js / TypeScript
Python
REST / events
SQL / NoSQL

End-to-end product work

I can take a feature from technical definition to interface, tests, and deployment.

React / Next.js
Integrations
Testing
CI/CD

Sensitive systems

Experience in banking, fintech, and payments, where traceability, idempotency, and change control matter.

Stripe
Webhooks
Microservices
Observability

03 / Capabilities

Technology organized by the problem it solves.

No percentages or logo walls. These are the areas where I connect tools with product and operating decisions.

Backend and APIs

Services, business rules, authentication, async work, events, and maintainable contracts.

Node.js
TypeScript
NestJS
Express
Fastify
Python

Product frontend

Accessible interfaces that clearly reflect domain state and constraints.

React
Next.js
Angular
SSR
Accessibility

Cloud and infrastructure

Serverless, observable systems that can be deployed reproducibly.

AWS
Google Cloud
Cloudflare
Docker
Terraform
CI/CD

Data

Relational and document models, migrations, indexes, and persistence shaped around real workflows.

PostgreSQL
MySQL
RDS
Firestore
D1
Redis

Payments and integrations

Checkout, webhooks, subscriptions, refunds, and idempotency around external events.

Stripe
Webhooks
Clerk
Resend
External APIs

Applied AI and agents

Tool-using agents, RAG, grounding, validation, guardrails, and answers tied to available evidence.

LangGraph
Gemini
Tool calling
RAG
SSE
Evaluation

Quality and delivery

Tests, contracts, observability, security, and environment-based releases before production.

GitHub Actions
Playwright
OpenAPI
Logging
Metrics

04 / Approach

I understand the domain before proposing architecture.

I work in reviewable increments and make risk visible early. Architecture should make change easier, not ceremonial.

Context

Goals, users, constraints, critical flows, and existing systems.

Model

Boundaries, data, contracts, threats, integrations, and reversible decisions.

Delivery

Small increments, useful tests, review, and pre-production environments.

Operations

Controlled release, observable signals, maintenance, and evolution.

Complexity must justify its operating cost.

05 / Contact

Is there a serious problem to solve?

Tell me the context, the current state, and what needs to change. I respond better to concrete problems than briefs full of adjectives.

Write on WhatsApp LinkedIn GitHub