Software Engineer, Distributed System

thatDot is hiring a Software Engineer to build Quine and its Enterprise edition. The role focuses on distributed cluster protocols, query and graph-interpreter features, and reliable, back-pressured streaming pipelines.

Responsibilities:

• Designing cluster protocols, extending our query engine and actor-based graph interpreter, and building back-pressured streaming pipelines
• Learn. We value curiosity and share a desire to continuously learn new things, including from each other
• Collaborate. As a fast growing team, we must communicate and work together to achieve goals. That includes both within teams and across our small, dynamic team
• Write. Clarity of thought is best reflected in clear documentation. We document our work in ways our community of backend software engineers will want to engage with
• Represent. Advocate for the needs of our users and contribute to the community discussion on product direction and uses
• Designing and maintaining protocols in distributed systems
• Implementing new features in our querying engines and actor-based graph interpreter
• Creating high-throughput back-pressured streaming pipelines
• Ensuring horizontal and vertical scalability

Requirements:

• Fluency in a statically typed, functional-leaning language (Scala, Haskell, OCaml, F#, Rust…) and the habit of modeling with algebraic types and letting the compiler work for you
• Experience with systems where things fail partially (queues, replicated stores, actors, clusters), and the instinct to ask what happens when a node dies mid-operation
• Hands-on experience building scalable, fault-tolerant applications or data infrastructure, with a correctness mindset: clear, well-tested code, and invariants or specifications when the problem calls for them
• A record of pushing past "good enough," treating a hard problem as an invitation to find a way through or around it
• Clear writing and reasoning, and the ability to learn new technologies and domains quickly
• You turn ambiguous problems into clear, well-reasoned plans without needing every detail defined up front
• You own your work through to the customer's outcome, including debugging, monitoring, and verifying correctness in production, and you anticipate reliability problems early
• You explain your trade-offs clearly and strengthen others through mentoring and rigorous code review
• Strong early-career engineers, including those with distributed systems, programming language or formal methods research backgrounds, are encouraged to apply
• formal verification (Lean, TLA+, etc.), graph databases, Kafka, Cassandra/ScyllaDB