Who does the work, and how

The people who write the code, the technologies they use, and how the work runs from first contact to delivery.

Who does the work

We are two senior engineers, in two countries.

Cassiano Schneider

AI Engineer, Santa Maria, Brazil

Eleven years across engineering and product, with multi-agent systems running in production on LangGraph, Google ADK, MCP and RAG.

  • Python
  • Django
  • FastAPI
  • LangGraph
  • Google ADK
  • MCP
  • PostgreSQL

Jorge Saicoski Sarkis

Backend & Cloud Engineer, Montevideo, Uruguay

Eight years in backend and cloud; at The Home Depot, via TCS, took Go API queries from ten seconds down to about two.

  • Go
  • Node.js
  • AWS
  • GCP
  • Terraform
  • Kubernetes
  • Docker

Working together

Time zone

Brazil and Uruguay, both UTC−3. Full overlap with the US Eastern morning and afternoon.

Communication

Slack, or whichever channel your team already uses, with a written update every two days and a weekly call.

Language

English, Portuguese and Spanish.

How the work runs

  • Discovery: we learn how the operation actually runs before proposing architecture, because the written requirement is rarely the problem.
  • Two-week cycles, with something running at the end of each one, instead of a single delivery at the finish line.
  • Every change goes through code review and automated tests before it ships.
  • We hand over with automated deploys and written instructions for operating what was built.

After delivery

Code ownership

The code is yours from the first commit. The repository lives in your organisation; we work in it by invitation.

Support

Thirty days of fixes at no cost after delivery, and a maintenance agreement when it makes sense.