Our Ai+ Hiring Partner 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 they deal with include:
Designing and maintaining protocols in distributed systems Implementing new features in their querying engines and actor-based graph interpreter
Creating high-throughput backpressured streaming pipelines Ensuring horizontal and vertical scalability Quine, our core technology, is a streaming graph interpreter that 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.
Quine powers many key use cases in cybersecurity, fraud detection, data pipeline engineering, infrastructure optimization, and a long list of others. As a Distributed Systems Engineer, they are seeking someone with interest and experience in distributed systems and data-intensive applications. You will have expertise with functional programming and object-oriented design and development. As a fast-growing team it is important that you can successfully collaborate with developers, architects, UX teams, and product managers, ideally in an early stage company environment.
Location
Support for fully-remote and in-person collaboration as it works best for individuals and the team. Some of their team is based in Portland, Oregon, but they are a remote-first company.
Role and Responsibilities
Learn. Become an expert in this cutting-edge technology. The “work” in “knowledge work” is all about gaining the necessary knowledge. Share. When you’ve spent time building a mental model to solve a problem, teach it to your colleagues so we can all get smarter and build better things together. Code. Great code follows from clear thinking. Write code you’re proud of and help grow the community of other contributors. Collaborate. As a fast growing team our engineers must communicate and work together to achieve goals. Write. Document your work in ways their community of backend software engineers will want to engage with. Represent. As a distributed systems engineer you are their user. Advocate for the needs of their users and contribute to the community discussion on product direction and uses.
Job Requirements
Strong interest and background in distributed systems Experience in Scala, Java, or other strongly typed JVM languages Experience in streaming systems and back pressuring (ideally Akka streams) Familiarity with functional programming and ability to use it pragmatically Solid understanding of concurrency in the JVM Familiarity with Akka or the Actor-model
Nice to have: experience using Cassandra (esp. in large clusters) Nice to have: experience using Kafka About thatDot thatDot is working hard to change how software is built and deployed, to turn high-volume data into high-value data. But it’s the people that they work with make it such a rewarding experience. So you can start to get to know them, here is what they 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.
Code: It’s fun! It’s fascinating. Always hold on to that. Knowledge work: Coding is the easy part. Figuring out the ideas is hard work. Thier mental model is really what they’re building when coding. Code is an expression of your mental model. People: A person ≠ their opinions. They value people even when they disagree with their opinions. Non-traditional backgrounds are highly prized. E.g. Philosophy majors wanted! They complement each other. Everyone is good at something and bad at something. They are upfront about what they don’t know, but they are also not afraid to learn anything that they don’t know. Humility and intellectual security are important for all of them. Hiring process: No coding on a whiteboard, brain-teasers, or guess-what-I’m-thinking questions. Plan to teach them something about the cool work you’ve done in the past. Let them teach you something about the cool work they’re doing now.
