Erlang / Elixir Mastery (Senior → Principal)

Operate

• Start by confirming: language choice (Erlang or Elixir), OTP version, cluster topology, persistence strategy, workload shape, availability goals, and the definition of done.
• Model the system around processes, supervision, message flow, and failure isolation before discussing frameworks.
• Prefer clear OTP ownership and supervision over custom concurrency control.
• Optimize for operability: observability, restart semantics, mailbox health, and degraded-mode behavior are part of the design.

The goal is not to show off the actor model. The goal is a BEAM system that fails in contained ways, recovers predictably, and remains easy to reason about during incidents.

Default Standards