Loading portfolio
Technical Lead / Software EngineerBuenos Aires, Argentina
JuliánBenitez

I'm Julián, a Technical Lead and Software Engineer based in Buenos Aires. At AlixPartners I set technical direction and stay close to architecture, implementation and review. Agala is the nickname I use online. Agala Labs is where I build and operate my own software.
How I work
I lead by building.
I lead multidisciplinary teams at AlixPartners, working across Argentina, the US and Europe. I stay involved in architecture, implementation and review, and help engineers work through technical decisions.
AI in the loop
AI in my engineering workflow.
I use coding agents to explore systems, plan changes and implement them. For complex work, I separate planning, implementation and review, with explicit decisions and executable checks between stages.
Plan
Start from the codebase and product constraints. Resolve open decisions and define a bounded change.
Implement
Give the implementation agent a clear task, relevant context and acceptance criteria.
Review & verify
Review the diff separately, run checks and inspect the result before shipping.
Current tooling
My everyday tools.
What I use to write, navigate and review code.
- AI-assisted developmentCodex
- Exploring codebases, implementing changes and reviewing the result.
- EditorNeovim
- Editing and navigating code, with a LazyVim setup.
- TerminalKitty
- My terminal, with tmux handling windows and panes.
- Gitlazygit
- Reviewing diffs, staging changes and working with branches.
Software platform
Agala Labs.
The technical home for my applications, shared services, UI library, infrastructure and this portfolio.
Nuxt applications. Go services. My own operating layer.
The applications are built in Nuxt. Shared capabilities live in Go microservices, with PostgreSQL underneath and a standardized path to production. The products do not need to share the same backend shape.
This portfolio is part of Agala Labs too. Building the whole setup has been one of my favorite technical challenges. I like owning the path from UI components and service boundaries to servers and releases, then making that path reusable for whatever I build next.
- Applications Nuxt · Vue · TypeScript
- Nuxt applications handle the web experience. Each product keeps the backend architecture its domain requires.
- UI library @agala-labs/ui · Vue 3 · TypeScript
- Shared components cover forms, navigation, overlays, data display and layout, with one semantic token system across applications.
- Shared services Go · HTTP APIs
- Capabilities that belong outside a product live in focused Go microservices with explicit HTTP boundaries.
- Data PostgreSQL
- PostgreSQL provides the persistent data layer for product data and shared services.
- Infrastructure Linux · Docker · OpenTofu
- Servers and workloads are defined as part of the platform instead of being configured as one-off environments.
- Delivery Ansible · Woodpecker CI
- Shared pipelines and deployment playbooks give every new application or service a known, repeatable route to production.
Contact