Andrea Minin · Engineering portfolio

Complex products from concept to production.

Backend engineering and software architecture grounded in explicit decisions, operational constraints, and maintainable delivery.

Track record

Working in software since 2003.

2003–2008

Grupo Arcor

Analyst programmer. Internal operational and accounting systems, plant process automation, stock control and logistics flows.

2010–2012

Winery

Data analysis and systems development support.

2015–2021

Independent

Freelance software developer, remote.

2021–2026

Lottery technology provider

Senior developer, front-end lead, development coordinator, software delivery lead.

Engineering focus

Systems, platforms, and production constraints.

Backend Engineering

Service boundaries, transactional workflows, data contracts, idempotency, and integration behavior.

Distributed Systems

Reliability, consistency, asynchronous workflows, observability, and failure-mode analysis.

Cloud Platforms

Deployability, security posture, resilience, infrastructure governance, and runtime operations.

Product Engineering

Technical decisions connected to user workflows, business constraints, and delivery sequencing.

Delivery approach

Architecture carried through implementation and operation.

  1. Context

    Clarify users, domain constraints, integrations, and engineering risks.

  2. Decisions

    Document boundaries, contracts, quality attributes, alternatives, and trade-offs.

  3. Implementation

    Deliver in increments with tests, automation, and observable behavior.

  4. Operation

    Evolve systems through production feedback, incidents, and measurable reliability.

Professional case studies

Regulated lottery platforms, 2021–2026.

Five years at a lottery technology provider serving Argentine provincial lotteries, as senior developer, front-end lead, development coordinator, and software delivery lead. Public platforms are named; internal product names are withheld.

One platform, many provincial lotteries

Online bettingMulti-tenantPaymentsCertified RNG

One codebase and one set of services run the online betting channel of provincial lotteries. Each lottery's commercial agreement defines its own interface, features, business rules, and authentication model.

In production

Per-lottery configuration

  • The same services run with mandatory sign-in for some lotteries and open access for others.
  • Payment integration for multiple providers and channels, configured per lottery.

Cupones No Ganadores: certified RNG draws

Technical leadCertified RNGLotería Correntina

End-to-end system behind Lotería Correntina's second-chance draws among non-winning Quiniela coupons: batch extraction from the central system, a certified RNG engine consumed as a REST service, per-zone draws with a verifiable evidence package, a broadcast presenter for TV, and public publication.

Draw lifecycle

  • Extraction. Non-winning coupons are consolidated from the central system on a configurable schedule.
  • Draw. Draws run per period and per zone, closing with a downloadable package of verifiable evidence.
  • Publication. A presenter application drives the TV broadcast; results stay on the public site for 15 days.

Assurance

  • Designed the certified RNG engine, a Spring Boot REST service.
  • Presented in ALEA audits and against WLA-SCS:2016 (built on ISO/IEC 27001), which requires independent RNG verification before an electronic draw can go live.
  • Prepared the services, black-box tests, and audit reports.
  • Draws are audited by a public notary.

Operations and stack

  • Administration panel with an annual calendar, draws by calendar and zone, and role management.
  • Spring Boot services; Next.js for administration and the public results site.

Public evidence

From manual releases to continuous delivery

Software delivery leadAWSGitHub Actions

Delivery practice for the provider's production applications, from environment strategy to release gates and cloud governance.

Continuous delivery

  • Led the migration of more than five production applications from manual deployment on nginx servers to continuous deployment on AWS with GitHub Actions.
  • Releases went from 15–30 minutes at best, and hours with fixes or rollbacks, to minutes.
  • Automated tests and telemetry gates became conditions for advancing through the pipeline.

Environments

  • Replaced a two-environment setup (functional testing and production) with per-branch environments for dev, QA, and higher stages.
  • Brought deployment practice from infrastructure into development (shell scripting; nginx, Tomcat, AWS) while keeping ownership of production deployments.

Cloud governance and coordination

  • Established governance standards for AWS accounts and environments — access, segmentation, and deployment conventions — across product lines onboarded onto the platform.
  • Coordinated development, QA, infrastructure, business, and external vendors: release planning, acceptance criteria, architecture review, and risk management.

Lottery back-office and integrations

Java · Spring BootNext.jsKeycloak

Systems that lotteries and their agency networks operate on.

Systems

  • Accounting system for lotteries and agencies: Java and Spring Boot, Next.js, Keycloak identity, Kafka messaging.
  • Lotemovil, the interface for agencies and sub-agencies, on the same stack.
  • Internal invoicing between the provider and the lotteries.
  • Critical internal accounting modules for revenue flows and reporting.

Integrations

  • Internal API for communication with external parties, including third-party games and a data integration with a regional telecom operator.
  • Public institutional sites built on WordPress with Elementor.

Independent engagements

Seven years delivering directly to clients, 2015⁠–⁠2021.

Remote freelance software development for small and medium businesses and independent professionals. The last months overlap the first months at the lottery technology provider.

Delivery

  • End-to-end web applications and internal tools: requirements, build, deployment, and ongoing maintenance.

Legacy systems

  • Refactoring and maintenance of inherited systems, API integration, and process automation.

Client ownership

  • Direct engagement with clients: functional analysis, scope, roadmap, and agreed deliverables.

Products

Independent products.

Personal products, each with its current status stated explicitly. Source code is private.

Python · Computer vision · Offline

Peritia Lab

Offline computer-vision lab that assists forensic video and image review: people counting and tracking, OCR, text-described object search, license-plate reading, and face capture within a perimeter. Every result keeps the configuration used and identifies source material by SHA-256; the examiner decides and the tool assists.

Distributed as a traceable portable executable.

In field use · Working toward OAA accreditation

Request a demo

Next.js · Supabase · TypeScript

Tarifa Justa

Checks residential electricity bills against the official tariff, step by step, with a catalog of distributors, cooperatives, and public providers by province and municipality. Current coverage: residential categories R1–R6 for Edenor and Edesur. The calculator stores no data; a consent-based community audit is planned.

MVP · Public preview

Open the MVP

Web app · WhatsApp API · Mercado Pago

ValeFiado

A digital credit notebook for small merchants: record what a customer takes on credit and what they pay, so both sides see the same account. It records credit only and does not move money.

Integrations: WhatsApp API, Mercado Pago per merchant (payment links and QR), QR code reading, and in-app messaging.

Operational · Launch pending

Visit valefiado.com

Public engineering evidence

Reference implementations with explicit scope.

These repositories are portfolio artifacts, not claims of production deployment. Each exposes decisions, constraints, and reviewable material.

TypeScript · MCP · Local LLM

open-job-hunter

MIT-licensed MCP server that discovers job listings across multiple sources and scores them against a profile with a local model on Ollama, so profile data stays on the machine. Zod validation, Docker, and GitHub Actions CI.

Review repository Visit the landing page

Architecture · ADR · Reliability

Architecture Playbook

Service boundaries, event-driven integration, consistency trade-offs, security, observability, and production-readiness governance.

Review repository

AWS · Resilience · Terraform

AWS Platform Reference

Multi-AZ design, network segmentation, disaster recovery, declarative infrastructure, compliance concerns, and FinOps.

Review repository

Technical capabilities

Responsibilities supported by public artifacts.

Backend Engineering
Software Architecture
Distributed Systems
API Integration
Transactional Workflows
Cloud Platforms
Observability
Technical Governance

Selected technologies

Tools connected to engineering responsibilities.

Backend

  • Java
  • Spring Boot
  • Node.js
  • NestJS
  • Python

Frontend

  • React
  • Next.js
  • TypeScript

Data

  • PostgreSQL
  • Oracle
  • MongoDB
  • Redis
  • Supabase

Messaging

  • Kafka
  • RabbitMQ

Identity and access

  • OAuth 2.0
  • OIDC
  • JWT
  • Spring Security
  • Keycloak

Platform

  • AWS
  • Docker
  • Kubernetes
  • Terraform
  • GitHub Actions

Testing

  • JUnit
  • Jest
  • Testing Library

Content platforms

  • WordPress
  • Elementor
  • Shopify

Architecture

  • REST APIs
  • Event-Driven
  • ADR
  • C4

Education & credentials.

Diplomatura en Blockchain y Finanzas Digitales

UTN FRBA, 2024

Tecnicatura Superior en Programación de Aplicaciones

UTN, coursework completed, degree not finished

Participation in ALEA audits and WLA-SCS:2016 assurance processes for electronic draws

Languages

Spanish (native) · English (professional reading and writing)

Contact

Engineering conversations with technical context.

Available for senior backend, solution architecture, platform, and technical leadership opportunities.