Erlang Developer - Distributed Systems

Job Description: You are a high ownership engineer who goes beyond writing code. In this role, you must have the ability to understand complex system problems end-to-end, take accountability for outcomes, and drive solutions from design to production. You will be working on large-scale, distributed, real-time backend systems where correctness, resilience, and performance directly impact live operations. Success in this role requires strong technical judgment, system-level thinking, and the ability to operate with ambiguity. Key Responsibilities: - Design, build, and own distributed backend services using Erlang/OTP - Model complex workflows using concurrency and message-passing primitives - Design and maintain robust supervision hierarchies and fault-recovery strategies - Build systems handling thousands of concurrent processes with predictable behavior - Ensure production readiness: - Observability (logging, metrics, alerts) - Graceful degradation and recovery - Safe deployment strategies - Debug and resolve production incidents, including distributed failures - Collaborate closely with cross-functional teams on system interfaces and behavior - Continuously improve system reliability, performance, and maintainability Qualification Required: Core Expertise: - Erlang with strong production experience - OTP Framework - GenServer, Supervisor, FSM behaviors - ETS and Mnesia - Distributed Erlang - Clustering - Inter-node communication - Handling partial failures and network partitions Systems & Architecture: - Distributed systems design - Actor-model concurrency - Event-driven and asynchronous architectures - Real-time / near-real-time systems Platform & Infrastructure: - Linux (debugging, profiling, system behavior analysis) - Networking fundamentals (TCP/UDP, REST, gRPC) - Messaging systems (Kafka, RabbitMQ, or similar) Datastores: - In-memory: ETS, Redis - Persistent: PostgreSQL or equivalent - Containerization and orchestration (Docker, Kubernetes) - CI/CD, monitoring, and alerting pipelines Additional Details: This role values engineers who take responsibility, reason about failure modes, have strong debugging skills in distributed, stateful systems, are comfortable working with long-running, always-on services, communicate clearly and technically, and have a bias towards making systems work in production. Experience expectations include 4+ years of backend or distributed systems development and 3+ years of hands-on Erlang/OTP experience. This role is not for engineers who only implement predefined logic or avoid production ownership but is for engineers who think in systems, own outcomes, and turn complex problems into working, reliable solutions. Job Description: You are a high ownership engineer who goes beyond writing code. In this role, you must have the ability to understand complex system problems end-to-end, take accountability for outcomes, and drive solutions from design to production. You will be working on large-scale, distributed, real-time backend systems where correctness, resilience, and performance directly impact live operations. Success in this role requires strong technical judgment, system-level thinking, and the ability to operate with ambiguity. Key Responsibilities: - Design, build, and own distributed backend services using Erlang/OTP - Model complex workflows using concurrency and message-passing primitives - Design and maintain robust supervision hierarchies and fault-recovery strategies - Build systems handling thousands of concurrent processes with predictable behavior - Ensure production readiness: - Observability (logging, metrics, alerts) - Graceful degradation and recovery - Safe deployment strategies - Debug and resolve production incidents, including distributed failures - Collaborate closely with cross-functional teams on system interfaces and behavior - Continuously improve system reliability, performance, and maintainability Qualification Required: Core Expertise: - Erlang with strong production experience - OTP Framework - GenServer, Supervisor, FSM behaviors - ETS and Mnesia - Distributed Erlang - Clustering - Inter-node communication - Handling partial failures and network partitions Systems & Architecture: - Distributed systems design - Actor-model concurrency - Event-driven and asynchronous architectures - Real-time / near-real-time systems Platform & Infrastructure: - Linux (debugging, profiling, system behavior analysis) - Networking fundamentals (TCP/UDP, REST, gRPC) - Messaging systems (Kafka, RabbitMQ, or similar) Datastores: - In-memory: ETS, Redis - Persistent: PostgreSQL or equivalent - Containerization and orchestration (Docker, Kubernetes) - CI/CD, monitoring, and alerting pipelines Additional Details: This role values engineers who take responsibility, reason about failure modes, have strong debugging skills in distributed, stateful systems, are comfortable working with long-running, always-on services, communicate cle