About
Engineering across product and operations.
I work on Python backend engineering, APIs, and integrations. My experience in architecture, cloud, and IT management helps connect technical decisions to product needs and production operations.
About
Software engineering, from backend to production
I work as a Senior Backend Software Engineer at Volix, developing APIs and services in Python. My previous experience spans architecture, cloud, infrastructure, and technical leadership.
My work includes systems for Hospital Sírio-Libanês, Grupo Bandeirantes portals, and TV platforms for hotel groups. Across these contexts, I follow software from requirements through delivery and ongoing operation.
- Years of experience
- 4+
- Projects delivered
- 10+
- Countries
- 2
- Users reached
- 100k+
Working principles
Criteria that remain when the technology changes.
Production is part of the design
Operations, failure modes, security, and observability enter the conversation from the start.
Clarity before complexity
The best architecture is one the team can understand, maintain, and evolve safely.
Decisions led by evidence
Metrics, context, and impact guide technical choices and priorities.
Leadership close to engineering
Technical management improves when it maintains real contact with code and production.
Technologies
Stack
High-Performance Backend
Cloud
DevOps & Observability
Advanced Frontend
Mobile Development
Streaming & Video
Artificial Intelligence
Frequently Asked Questions
How I work in practice.
Architecture criteria, technology choices, and responsibilities when delivering software.
Where do I focus my technical work?
I work across the full stack, with a focus on backend engineering, infrastructure, and operations. This includes Go APIs, React and Next.js applications, databases, and delivery automation on AWS and GCP.
How do I choose languages and tools?
I use Go, TypeScript, JavaScript, Python, Kotlin, and SQL in different contexts. The choice depends on product requirements, behavior under load, team expertise, and the cost of maintaining the solution.
What is my experience with scale and performance?
The documented Hospital Sírio-Libanês backend handles over 20 million requests per month, with a 6 ms average API response and a 92% cache hit rate. These measurements describe that service; the API average does not represent the latency of the entire TV experience.
How do I connect frontend and backend?
I work from interfaces through API contracts, using React, Next.js, and TypeScript. Delivery includes accessibility, loading and error states, data consistency, and the performance users actually experience.
How do I approach infrastructure and operations?
Build, deployment, monitoring, and recovery are part of delivery. I use CI/CD pipelines, containers, metrics, and alerts to track service behavior and investigate failures with context.
What guides my architecture decisions?
I start with requirements and operational constraints. I define component responsibilities, model the data, and set integration limits. The team needs to understand the architecture and evolve it without turning every change into a complete migration.