I'm a Staff Software Engineer at Cabify focused on building reliable backend systems with Elixir, Phoenix, Ruby, and distributed architectures.
I care about software that is simple to operate, easy to observe, and resilient under real production constraints.
- Elixir & Phoenix — backend services, real-time tools, LiveView, Ecto, Oban, and production systems on the BEAM.
- Observability — OpenTelemetry, structured logging, traces, metrics, Grafana dashboards, Prometheus, alerting, and production debugging.
- Distributed systems — microservices, event-driven architectures, reliability, service boundaries, and operational simplicity.
- Technical leadership — architecture decisions, mentoring, code quality, technical direction, and cross-team collaboration.
- Developer tooling — improving feedback loops, CI/CD, libraries, internal platforms, and shared engineering practices.
I'm currently exploring how to make Elixir production systems easier to understand, operate, and evolve:
- Better observability patterns for Elixir services.
- Practical OpenTelemetry adoption.
- Phoenix LiveView for internal operational tools.
- Maintainable architecture for long-lived systems.
- The impact of AI-assisted development on senior engineering work.
I write about Elixir, observability, backend architecture, and staff-level engineering.
- Blog: arctarus.com
- Substack: gabrielortuno.substack.com
- LinkedIn: gabriel-ortuno
Recent topics include:
- Elixir observability in production.
- OpenTelemetry, logs, metrics, and traces.
- Phoenix LiveView for real-time internal tools.
- Architecture trade-offs in backend systems.
- Technical leadership beyond code.
Elixir · Phoenix · Phoenix LiveView · Ecto · Oban · Ruby · Rails
OpenTelemetry · Prometheus · Grafana · PostgreSQL · MySQL
Kubernetes · Docker · GitHub Actions · GitLab CI · Distributed Systems
Choose technology by the architecture it removes.
I prefer systems that reduce coordination overhead, make failure modes visible, and help teams move with confidence.
For me, good engineering is not only about choosing powerful tools. It is about making the system easier to reason about for the next person who has to debug, extend, or operate it.
I have been involved in the Ruby, JavaScript, and Elixir communities for many years, including organizing conferences and contributing to shared engineering practices.
I am especially interested in projects around:
- Elixir tooling and libraries.
- Observability and telemetry.
- Developer experience.
- Internal platforms.
- Practical AI-assisted engineering workflows.
You can find me here:
- GitHub: @arctarus
- Blog: arctarus.com
- Substack: gabrielortuno.substack.com
- LinkedIn: gabriel-ortuno


