Skip to content
View aeljandro2's full-sized avatar

Block or report aeljandro2

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
aeljandro2/README.md
Manuel Núñez. Backend and AI Systems Engineer. From the electron to the agent.

I have worked on every layer between a power cable and an AI agent: electrical systems, circuit boards, firmware, cloud backends, real-time apps, and now agents. Each job added a layer. Together, they let me design systems end to end.

The story

Chapter 01: The machine. 2013, electricity, underground mine.

It started underground. My first job kept the electrical systems of a mine's heavy equipment running. Lesson one: real systems fail, and someone has to understand why.

Chapter 02: The electron. 2014, electronics, off-grid solar.

I designed off-grid solar systems for rural communities in Honduras: the circuit boards, the embedded C firmware, the whole system. Engineering for places where nobody can call support.

Chapter 03: The fleet. 2017, operations and cloud, indoor farms.

Remote from Honduras, I kept a fleet of about 150 connected indoor-farming machines running for a US company, with Python health checks and event-driven automation. It was my first cloud work. I also designed the control system for its vertical farms.

Chapter 04: The product. 2020, device to cloud, first sketch to market.

A US hardware startup, from its first sketch: Arduino code in a shared Dropbox. Six years later: a connected device with about 500 units in the market, a serverless AWS backend, real-time mobile apps, and an engineering team of about 20 that I lead.

Chapter 05: The agent. 2026, AI agents. I design, agents build.

Today agents write the code, so my job moved up a layer: I design the system, then direct and review the agents that build it. One of them operates our team planner through the same API as the web app, signed in like any teammate.

Blueprints

Blueprints: 20 systems I can design, each drawn as inputs, a stack, and outputs. Connected fleet, self-testing cloud, agent operations desk, OTA release train, agent-to-agent API, live telemetry, knowledge copilot, event-driven store, clinic booking, multi-tenant SaaS, solar microgrid, farm autopilot, inbox to ERP, shipment radar, research swarm, edge vision, zero-trust access, data lake and SQL agent, offline-first mobile, agent evals and tracing.

Not a portfolio: these are systems I can design with what I know today. Any client can sit on either side, devices, phones, people, or other agents, and the stack in the middle is infrastructure as code. The first one is the one I run in production.

Proof

  • ~20 engineers led across firmware, backend, and web.
  • ~500 devices in the market, from the first prototype to the first production batch.
  • 12x faster firmware transfer between microcontrollers: 2 MB in 45 seconds instead of 9 minutes.
  • 0 resolvers changed when an AI agent started operating a production GraphQL API: it signs in as an ordinary user, so authorization stays in one place.
  • 2,000+ commits since 2020, most of them in private repositories.

Toolbox

Toolbox. AWS: Lambda, API Gateway, AppSync, IoT Core, Device Shadow, DynamoDB, S3, Cognito, IAM, EventBridge, SQS, SES, CloudFront, WAF, Route 53, ACM, Secrets Manager, Systems Manager, CloudWatch, EC2, VPC, CloudFormation, AWS CDK, Amplify. Backend and data: Python, Node.js, TypeScript, GraphQL, REST, MQTT, PostgreSQL, row-level security, Supabase, JWT, OAuth 2.0, HMAC, webhooks, cron jobs. AI and agents: Claude API, Claude Code, MCP, agent-facing APIs, capability manifests, multi-agent workflows, structured outputs, custom skills, human in the loop. Integrations: Stripe, Gmail API, Shopify, carrier tracking, Amazon SES, self-hosted mail, Resend, Vercel, three.js. Systems: C++, C, ESP32, ESP-IDF, FreeRTOS, LVGL, UART, SPI, I2C, BLE, WiFi, OTA updates, PID control, Linux, Bash. Delivery: Git, GitHub, Docker, Playwright, Vitest, CMake, PowerShell, React, Next.js. I design the system; agents help me build it. From the electron to the agent.

LinkedIn

Most of my work lives in private repositories; the contribution graph below counts it.

Pinned Loading

  1. esp32-psram-stl esp32-psram-stl Public

    Put the C++ standard library in the ESP32's PSRAM: header-only C++17 allocators for vector, map, unordered_map, string, and your own objects. Arduino and ESP-IDF.

    C++ 14 2