Backend Database Engineer

We are a stealth-mode firm working on market and transaction-level systems. The work is not consumer-facing, and most of it is not public. We operate with a high bar for correctness, discretion, and long-horizon thinking.

Role Description

You will work on the design, evaluation, and operation of database systems that support transaction-level analysis, system state tracking, and historical reconstruction under strict correctness constraints.

The role focuses on how data is represented, persisted, queried, and evolved over time in systems where accuracy, temporal consistency, and auditability matter more than convenience. Rather than building analytics pipelines or application schemas, the work centers on data models that remain stable under change, enable precise reconstruction of system behavior, and avoid silent inconsistencies.

The objective is to ensure that database-level decisions support reliable reasoning about transactions, states, and outcomes across long time horizons.

Responsibilities

• Data Modeling:

  Design database schemas and data models that capture transactional state, timing, and dependencies without ambiguity.

• Consistency & Integrity:

  Ensure strong data integrity, correctness guarantees, and explicit handling of edge cases and partial failures.

• Query Design:

  Develop and optimize queries for accuracy, interpretability, and predictable performance.

• Schema Evolution:

  Manage schema changes over time while preserving historical meaning and backward compatibility.

• Documentation:

  Produce clear documentation describing data assumptions, invariants, and limitations.

Qualifications

• Education:

  Bachelor's degree or higher in Computer Science, Engineering, or a related field.

• Database Experience:

  Hands-on experience working with relational or transactional databases in production environments.

• Data Rigor:

  Strong understanding of consistency models, indexing, and query behavior.

• Analytical Judgment:

  Ability to reason carefully about data correctness, temporal relationships, and failure modes.

• Experience:

  Experience with SQL-based systems, transactional workloads, or data integrity-critical applications is a plus.