Elixir Developer

About

Elixir expertise is rare, and we’re intentionally hiring for depth, not surface familiarity.

This role is for engineers who genuinely enjoy functional programming, concurrency, distributed systems, and the BEAM ecosystem. We’re looking for people who understand OTP concepts deeply enough to use them naturally in real system design — not just explain them theoretically.

If you’ve spent time exploring Elixir because you genuinely enjoy how it works, this role is likely aimed at you.

What You’ll Do

• Diagnose and fix concurrency issues in high-scale Elixir/Phoenix systems.
• Improve backend performance through profiling and bottleneck analysis.
• Build and maintain real-time event-driven backend workflows.
• Contribute to architecture discussions around distributed systems and fault tolerance.
• Improve reliability through OTP supervision strategies and graceful degradation patterns.
• Debug distributed systems using tooling such as :observer, tracing, and mailbox inspection.
• Work on systems where asynchronous reasoning and process isolation are critical.

Who Is the Right Fit

• Has real production experience with Elixir and Phoenix.
• Understands OTP concepts like GenServer, Supervisor, Agent, Registry, and Task through actual implementation experience.
• Is comfortable reasoning about concurrency, message passing, and process isolation.
• Has worked on distributed or real-time systems.
• Enjoys debugging complex async behaviour and race conditions.
• Thinks naturally in functional programming patterns rather than trying to force object-oriented approaches into Elixir.
• Is deeply curious and self-driven in learning distributed systems concepts.

Not a fit if:

• Your Elixir experience is limited to tutorials or small experiments.
• Your OTP knowledge is only theoretical.
• You apply object-oriented design patterns directly into Elixir systems.
• You’ve never worked on real-time or event-driven backend systems.