Garri FigueroaEspañol

Software Engineer · Fullstack and Cloud Infrastructure

Garri Figueroa

I build software for operations where the field is offline, the stakes are physical, and the paperwork is a legal obligation.

What I am building

Software Engineer · Founding Team Member · CaptaLog

  • Ruby on Rails 8
  • MySQL 8
  • Amazon RDS
  • Amazon EC2
  • React Native
  • Expo
  • TypeScript
  • SQLite
  • MCP
  • Founding team member, involved in product, technical and business decisions.
  • Designed and built the offline-first mobile app from scratch in React Native on Expo, for iOS and Android. Over a year of continuous development; live on the App Store and Google Play.
  • Defined and implemented the synchronisation strategy: fire-and-forget dispatch from the device plus a symmetric reconciliation pass, so field data is captured without connectivity and device/server divergence is resolved without data loss.
  • Integrated the mobile app and the web platform through versioned sync contracts: the backend generates and publishes the contract for every payload and the app consumes it as a fixture, so its transformation tests fail when the contract moves. Divergence between the two sides surfaces in CI instead of in the field.
  • Designed and implemented the platform's authentication on OpenID Connect with PKCE.
  • Fullstack development of the web platform, including the inspection checklist engine with multiple question types and nested structures.
  • Established the testing practice across both repositories: separate unit and integration suites on the mobile app, and unit, integration and system tests with measured coverage on the web platform. Linting, formatting and static security analysis run on every commit.
  • Designed and built the MCP integration, exposing the platform to AI assistants for task creation, checklist editing and publishing, issue management and document lookup.
  • Agent-assisted development as the standard workflow: one isolated worktree per task, agents implementing and reviewing against written repository conventions, and an in-house MCP server giving them access to the platform domain. Technical judgement, review and the decision to merge stay human.
  • Production observability instrumentation and failure resolution on field devices, where the error rarely reproduces on a desk; including silent validation errors that caused complete rendering failures in the editor.
  • Competitive analysis of the field inspection software market as input for product decisions.

Selected work

Captalog

Live Founder and technical lead

Offline-first platform for safety compliance in construction, mining and energy. Field teams run checklists and inspections on sites with no connectivity; everything syncs when it can, and the audit trail has to hold up afterwards.

  • Ruby on Rails 8
  • React Native
  • Expo
  • MySQL 8
  • Amazon RDS
  • EC2
  • Go
  • MCP

www.captalog.com

Valopes

Live Software engineer

Carbon footprint measurement and waste management platform: IoT ingestion and infrastructure as code on AWS.

  • Ruby on Rails
  • AWS
  • CloudFormation
  • S3
  • CloudFront
  • IoT

www.valopes.com

Yuntapp

In progress Author

Digitises the Chilean certificate of residence: residents request, pay for and download it online while their neighbourhood association verifies identity remotely. The PDF carries a QR code and a public verification URL.

  • Ruby on Rails 8
  • Docker
  • Kamal

All projects

Open source

I contribute where I hit real problems, not to farm activity.

uunicorn/python-validity#256

Synaptics fingerprint sensors on Linux. Brought up a factory-empty 06cb:00b7 (0xd51 silicon) from zero flash partitions to working enrollment, then contributed the result as a positive control for a reset_blob failure that had another contributor stuck for months, plus a fix for a startup bug that permanently bricks the driver if a firmware upload is interrupted.

libfprint!626

Hardware-validated the native Validity/Synaptics driver on silicon its author had no access to, and reported two blockers found in the process, including one affecting devices he had already validated.

Both involved reading USB protocol traces, signed firmware blobs, and TLS handshakes against a sensor with no public documentation.