We're a fully distributed team and as required by federal law this role is open only to any US citizen based in the US.


➡️  Overview | What we do | The Role | Compensation | The Company | **Apply** | The Interview

Overview

“Okay, but what would I be working on?”

Our flagship product is a message processing pipeline that runs detection rules written in MQL — "Message Query Language", our first-party DSL for querying email messages. This core function protects organizations from phishing. The Sublime Security platform monitors and analyzes all incoming email for an organization's employees, flagging suspicious messages for the security team to triage.

Here’s a conceptual view of how a rule is processed and what a flagged message looks like in our UI:

8e6858b6-45f4-4d06-ac8f-58cf0d5b3eae.png

mdv.png

Behind MQL for writing detection rules are ML classification models, external services, functions like WHOIS lookup, headless browsing, and more.

Our systems handle large datasets and perform inherently complex and resource-intensive operations. However, our core competency—detecting and remediating attacks—requires extremely low latency. As a result, we have very little tolerance for performance degradation.

We can host a customer’s Sublime instance, or they can deploy our entire product stack on their own infra via AWS CloudFormation on ECS or Azure Resource Manager on Kubernetes via AKS. This diversity of deployment type adds some complexity to our development lifecycle. Our goal is to consolidate our infrastructure setup to make it easy for users to deploy Sublime in any environment.

A backend deployment engineer will focus on:

Because we’re a small engineering team of generalist engineers, you sometimes may be asked to build general backend application features or fixes as needed.

Keep reading for specific examples of what you’d work on!