About the role
Sales Engineer Empirical Security is a quantum leap forward in exposure management, building custom models at scale to help organizations predict and prioritize the threats most likely to endanger them. Enterprises can no longer keep up with the flood of potential exploits caused by the AI era; only Empirical gives resource-strapped security teams the predictive capabilities to punch way above their weight class. We're looking for a dedicated, experienced, and basically brilliant Sales Engineer to be the technical conscience of every enterprise deal. You'll partner with account executives to run demos, scope proofs of value, and answer the hardest questions a CISO or head of vulnerability management can throw at a modeling company. This is
the role for someone who wants to sell, but wants to sell on the merits of the math.
What you'll do: Own the technical side of the sales cycle from discovery through close, working shoulder-to-shoulder with an account executive on every named opportunity. Run live demos of the Empirical Global and Local models against a prospect's own CVE list, and translate what the score is doing into language a practitioner can act on. Design and execute proofs of value that measure Empirical against whatever the customer is using today, whether that is CVSS, KEV, a competing scoring product, or a homegrown model. Write the technical response to RFPs, security questionnaires, and architecture reviews without needing three weeks and a red team of internal reviewers. Serve as the bridge between the customer and Empirical's data science and product teams, feeding real deployment friction back into the roadmap. Present at trade shows, customer roundtables, and analyst briefings when the situation calls for a technical voice in the room. You would be an excellent candidate if... You have three or more years as a sales engineer, solutions architect, or technical account manager at an enterprise security software company. You can hold your own in a conversation about ROC curves, calibration, and base rates, and you can explain any of them to a security director who does not want a statistics lecture. You have hands-on comfort with the vulnerability management stack, including scanners like Tenable, Qualys, or Rapid7, and ticketing and workflow tools like ServiceNow and Jira. You can write enough Python or SQL to pull a customer's data into a notebook, run a comparison, and put a chart in front of the account team the same afternoon. You are comfortable in front of a whiteboard with a skeptical CISO, and you know when to push back on a bad requirement rather than nod through it. You have worked at a smaller startup, or you are genuinely excited about what it takes to help a phenomenal one grow. Extra credit if: You have run a bake-off between prioritization methods before, and you know how to construct one that a customer will actually trust. You have familiarity with EPSS, the Prioritization to Prediction research series, or the broader body of work on exploit prediction. You have worked with regulated buyers in financial services, healthcare, or critical infrastructure, and you understand the audit questions that come with them. A Final Word Don't check off every box in the
