AI automation engineer

Systems that keep running. On their own.

I design, deploy and operate AI automation on my own infrastructure. Then I keep it running.

Portrait of David Ciro
David Ciro. Medellín, Colombia. UTC-5, full overlap with US hours.

Seven systems.
Four running right now.

Built, deployed and operated by me. No one watching them overnight.

Four ways to work together.

Fixed-scope project

You have a system in mind and want it delivered. I scope it, build it, deploy it and hand it over documented, with the automation, the integrations and the infrastructure it needs to run without me.

  • Defined scope
  • End-to-end delivery
  • Documented handover

Monthly retainer

Ongoing capacity for teams running automation in production: new workflows, integrations, incident triage and the maintenance nobody has time for: expiring tokens, provider API changes, silent failures.

  • Monthly hours
  • Operations included
  • Async communication

Team augmentation

I join your team for a sprint or a quarter and work inside your process: your repo, your board, your review flow. Useful when the automation or AI-integration work is real but doesn’t justify a full-time hire yet.

  • Your process
  • UTC-5 overlap
  • Weekly or sprint-based

Technical audit

A review of automation you already have running, with findings backed by evidence: what breaks silently, what has no error path, what will not survive a second client. You get a prioritised report, not a sales pitch.

  • Evidence-backed
  • Prioritised report
  • Short turnaround

No public rates. You get a number in my first reply.

Most of what I build starts as a pilot and becomes a platform. Knowing what not to make configurable is the part nobody can improvise.

Systems, not prototypes

Bots handling conversations over an official WhatsApp provider, pipelines publishing on a schedule, workflows filing invoices every day.

Async-first

Slack, Notion, pull requests and written documentation. UTC-5 overlaps the entire US working day.

My own infrastructure

AWS EC2 behind nginx, Docker and self-hosted n8n. I don’t need anyone else to deploy what I build.

Systems shipped to production
5
Building since
2020
Full overlap with US hours
UTC-5

Usual stack: React, TypeScript, Astro, Node.js, Tailwind CSS, Flutter, n8n, Redis, Remotion, AWS, Figma, Git

Experience

  1. Since 2025

    Co-founder · Product & Infrastructure

    Galactic AIMA

    I lead product development and run the infrastructure: the self-hosted n8n on AWS EC2 that the whole team’s automations run on, services provisioned with Terraform and reached through SSM instead of open SSH, and the AI systems the agency sells. I also own QA and fixes on a client platform in production.

  2. Since 2022

    Freelance Developer & UI Designer

    Independent

    Design and development of digital products for clients across Latin America and Spain. Full-stack work with React, Astro and Next.js; interface design in Figma; workflow automation with n8n.

  3. Since 2020

    Visual & Motion Designer

    Own projects and collaborations

    Visual identities, social media assets and motion graphics. The foundation behind the design judgement I bring to every product.

  4. 2020-2024

    Software Development Degree

    Institución Universitaria Pascual Bravo

    Software engineering fundamentals, databases, networking and systems architecture, plus continuous self-teaching in modern web development and automation.

Automation & AI
n8n, LLM APIs, Embeddings, Redis, Webhooks
Development
React, Astro, TypeScript, Node.js, Flutter
Infrastructure
AWS EC2, Terraform, Docker, PostgreSQL, Git
Full profile on LinkedIn

Let’s build the next one.

Tell me what you need running. I reply in writing, with questions, a rough plan and a number.

Async-first. UTC-5, full overlap with US hours.

Or write directly

A couple of lines is enough. What the system should do, and what’s blocking you today.