Software Engineer, Distributed System — United States

About the job

We're building Quine, a streaming graph, and its Enterprise edition. The work includes designing cluster protocols, extending our query engine and actor-based graph interpreter, and building back-pressured streaming pipelines. Every feature has to work correctly across a cluster when nodes fail, so we want deep type-driven design paired with distributed systems thinking. We're looking for engineers who are suspicious of easy answers and can't walk past something broken without wanting to fix it.

We hire at several levels. Strong early-career engineers, including those with distributed systems, programming language or formal methods research backgrounds, are encouraged to apply. We'll place you at the level that fits and teach the rest, from Pekko and JVM concurrency to cluster protocol design, formal specification, and graph internals.

Location

We are a remote-first company, but we do travel when necessary for customer engagement or engineering collaboration.

Job Requirements

You'll need:

• 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. We'll teach you our Scala.

• 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.

For mid-level and senior roles, we also look for:

• 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.

Nice to have: formal verification (Lean, TLA+, etc.), graph databases, Kafka, Cassandra/ScyllaDB.

Day to day at pAtMyGR

• 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.

About us

pAtMyGR is a growing company that specializes in solving high-throughput data streaming problems (entity resolution, streaming joins, ingest pipelines, incremental computation, pattern matching, etc.) using graphs. Some of the typical challenges we deal with include:

• 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

Quine, our core technology, is a streaming graph that combines key operational features of event stream processing systems like Flink with the graph data structure of databases like Neo4J or Tigergraph. Quine makes it easy to find complex patterns and anomalies in massive data streams and trigger action immediately. Built on native streaming graph technology as the result of 7+ years of DARPA-funded R&D, this hot new technology makes it easy for infinite datasets to be efficiently analyzed in real-time. Ideal use cases for Quine include financial and identity fraud detection, XDR/EDR solutions, network observability/root cause analysis, and e-commerce.

What We Believe About Work

• About more than just a paycheck.

• Should be intellectually engaging.

• Should provide the opportunity to learn and grow.

• Short-termism in tech is bad. It's worth building lasting relationships.

• Punching a clock or counting hours is bad. Results > Hours.

• It's a big part of our lives, but it's not all there is.

Creativity In Work

• Work should be fun!

• Knowledge work: coding is the easy part. Figuring out the ideas is hard work.

• Our mental model is really what we're building when coding. Communicating is an expression of your mental model. First think clearly, then help someone else share your thoughts.

Hiring

• Plan to teach us something about the cool work you've done in the past.

• Let us teach you something about the cool work we're doing now.

Featured benefits: Medical insurance, Vision insurance, Dental insurance, 401(k)