Elixir-first backend engineer
Anderson Espindola
I build backend systems with Elixir and Functional Programming, focusing on domain clarity, explicit effects, concurrency, and reliable production behavior.
- Elixir
- Functional Programming
- BEAM/OTP
- Distributed Systems
Primary stack
Elixir, BEAM, OTP
Engineering style
Functional, explicit, resilient
Background
Backend systems, SRE, cloud operations
Current Technical Focus
This page is no longer a project gallery. It is a direct view of the technical areas I am prioritizing now, with Elixir and Functional Programming at the center of how I want to build software.
Elixir & BEAM/OTP
My main direction for backend engineering, centered on concurrency, supervision, message-oriented design, and fault tolerance.
- Elixir as the main language direction
- OTP concepts and supervision strategies
- Process-oriented architecture on the BEAM
Functional Programming
Applying immutable data, composition, explicit effects, and clear function boundaries to reduce incidental complexity.
- Pure transformations where possible
- Explicit side-effect boundaries
- Modeling domains with clearer invariants
Backend Systems
The background I already bring from production work with APIs, messaging, caches, databases, and multi-service systems.
- Distributed service boundaries
- Messaging, queues, and realtime concerns
- API design, auth, and data consistency
Reliability & Operations
Production discipline remains part of my profile, especially around observability, deployments, resilience, and system behavior.
- SRE mindset and cloud operations
- Docker, Kubernetes, CI/CD, observability
- Operational clarity under real-world load