№ 04 / About

Rhay Parra

Rhay Parra
fig. 01 — Montevideo

I'm from Venezuela, where I studied industrial engineering and IT in parallel and started shipping code professionally in 2012. From there I moved to Buenos Aires, where I spent five years across streaming, media, banking and telecom work for companies like Telecom Argentina and Globant, and later worked as an architect for a conversational-marketing SaaS. I'm based in Montevideo now, working remotely for US teams.

Today I split my time between two things. At Turnout, a US advocacy platform where human advocates backed by AI help people win disability claims, claim veterans' benefits, navigate healthcare and get their children the right school support, I'm the senior architect: an Nx monorepo with three Next.js apps, a NestJS backend, a Python serverless layer for AI agents, and enough third-party integrations to keep me honest. At Loxben, my own company, I build small B2B products for finance teams with a two-person team, which is a different discipline entirely — every hour has to earn its place.

What I care about is the gap between a system that works today and one that still works in three years. Most of the failures I've debugged weren't bugs in the ordinary sense; they were decisions nobody wrote down, made under constraints nobody remembered. So I write things down: decision records with the alternatives that lost, implementation plans a mid-level developer can execute without me in the room, runbooks for the setup that only happens once a quarter. It's not bureaucracy. It's how a small team stays fast after the second year.

I work best in pairs and small groups, with people who will tell me when I'm wrong and expect the same back. I'm direct in review and prefer a short, precise answer over a diplomatic one, though I try to make sure it's kind as well as correct. Outside of work I read a lot, study the humanities on my own, and practice classical piano every day.

How I work

  1. Write the decision before the code.

    A decision record with the alternatives that lost is the only artifact that still explains the system after the people who built it have moved on.

  2. Team expertise beats the benchmark.

    Moving a product from FastAPI to NestJS made us two to three times faster, not because NestJS is better but because we already knew it.

  3. Boring infrastructure, interesting product.

    GuardDuty over a ClamAV sidecar, Multi-Zone over Module Federation, managed queues over clever ones — the interesting problems should be in the domain, not the plumbing.

  4. No errors is not the same as healthy.

    If a system's failure mode is silence, instrument the silence: last-event age, expected-vs-observed counts, alarms on absence.

  5. Keep the exit open.

    Roles live in our database, not the auth provider's metadata; the CRM sits behind a facade; each product gets its own AWS organizational unit. Migrations are cheap when you planned for them and brutal when you didn't.

  6. Plans should run without me.

    Tasks carry acceptance criteria, schemas and test expectations, so the next person starts working instead of scheduling a meeting.

  7. Say it plainly.

    If the code is wrong, I'll say so and why. I expect the same, and I'd rather lose an argument than ship a bad decision politely.

Skills

Languages
  • TypeScript / JavaScript
  • Python
  • SQL
  • Bash
  • Go
Frameworks and libraries
  • NestJS
  • Next.js (App Router)
  • React
  • Nx
  • Prisma
  • BullMQ
  • Vercel AI SDK
  • LiveKit Agents
  • Pydantic
  • FastAPI
  • AWS Lambda Powertools
  • Serverless Framework
  • Django
  • Express
Cloud and infrastructure
  • AWS
  • ECS Fargate
  • Lambda
  • EventBridge
  • SQS
  • S3
  • KMS
  • RDS
  • CloudFront
  • CloudWatch
  • EMF
  • GuardDuty
  • Rekognition
  • Bedrock
  • AWS Organizations
  • AWS CDK
  • Docker
  • Vercel
  • LocalStack
  • Heroku
  • Firebase
  • GCP
  • Azure
Data
  • PostgreSQL
  • Prisma
  • Redis
  • TimescaleDB
  • DynamoDB
  • MongoDB
Integrations
  • Salesforce
  • jsforce
  • Salesforce Pub/Sub API
  • Invocable actions
  • Auth0
  • Kinde
  • Box
  • Twilio SIP
  • Square
  • Mailchimp Transactional
  • HubSpot
  • Documo
AI
  • Vercel AI SDK
  • OpenAI
  • Anthropic Claude
  • Amazon Bedrock
  • LiveKit Inference
  • Deepgram
  • Cartesia
  • Whisper
  • Azure Speaker Recognition
Practices
  • Architecture decision records
  • RFC-to-phased delivery
  • Approval gates
  • HIPAA-conscious design
  • Audit trails
  • Envelope encryption
  • BAA scoping
  • Infrastructure as code
  • Observability
  • CI/CD
  • Pair programming
  • Planning in Linear and Notion
  • Acceptance criteria

Education and certifications

Education

  • Degree in Information TechnologyUniversity Institute of Technology Juan Pablo Pérez Alfonzo, Venezuela · 2010–2014
  • Industrial EngineeringUniversity of Carabobo, Venezuela · 2008–2013

Certifications

  • AWS Certified Solutions Architect – AssociateAmazon Web Services
  • MongoDB for Node.js DevelopersMongoDB University
  • Server-side Development with NodeJSHKUST via Coursera
  • Front-End JavaScript Frameworks: AngularJSHKUST via Coursera
  • Multiplatform Mobile App Development with Web TechnologiesHKUST via Coursera

Contact

Employed full-time; open to short consulting and architecture-review engagements.

If you have a system that has to grow up, or a decision you're not sure how to write down, [email protected] is the fastest way to reach me.