SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 255,000 - 290,000 / annual
Horizon3.ai is a fast-growing cybersecurity company that delivers autonomous pentesting and security assessment operations at scale. The NodeZero platform helps organizations proactively find, fix, and verify exploitable attack vectors before criminals exploit them, serving organizations from small institutions to Global 100 enterprises.
You will serve as the Principal Engineer for the Database Platform — the technical anchor of NodeZero's data infrastructure. This is a deeply hands-on individual contributor role with no direct reports. Your influence comes through technical leadership, architecture ownership, and raising the engineering bar across the team.
NodeZero's data layer is complex: it stores millions of discovered assets, graph-structured attack paths, time-series vulnerability data, and audit-critical pentest results across a multi-tenant architecture where correctness and data isolation are non-negotiable. You will own the most consequential database architecture decisions and ensure the data layer can support NodeZero's growth without requiring proportional operational effort.
Key responsibilities include:
- Define and drive the technical roadmap for the Database Platform in partnership with the Senior Engineering Manager and broader Pentest Platform organization
- Own complex database architecture decisions: schema design, partitioning strategies, migration patterns, and scalability approaches; produce design documents that become the shared technical model
- Be NodeZero's definitive expert on PostgreSQL at scale — query optimization, indexing, partitioning, replication, and connection pooling; set standards the team follows
- Architect and guide the evolution of NodeZero's graph-based asset model representing how discovered hosts, services, credentials, and vulnerabilities relate across pentests
- Own schema design review processes; ensure every migration is safe, reversible, and zero-downtime; build tooling and culture that treats schema changes with production-code rigor
- Mentor P5 and P4 engineers through code review, design review, and pairing; raise everyone else's ceiling
- Partner with Data Ingestion, Asset Inventory, API Platform, and Security Research teams to define data contracts, query performance standards, and architectural guardrails
You will write code, author design documents, and set the technical direction that every engineer on the Database Platform team builds toward.
Horizon3 is a fully remote company with a team of former U.S. Special Operations cyber operators, startup engineers, and cybersecurity practitioners. The company is committed to a culture of respect, collaboration, ownership, and results. Up to 5% travel may be required.
REQUIREMENTS:
- Deep, production-proven PostgreSQL expertise: query planner internals, advanced indexing (partial, expression, GiST/GIN), partitioning strategies, logical replication, vacuuming at scale, and connection pool tuning
- Experience architecting multi-tenant databases at scale: row-level security, tenant isolation, schema-per-tenant vs. shared-schema tradeoffs
- Experience with schema migration at scale in production systems: zero-downtime migrations, backwards-compatible schema evolution, and migration tooling (Flyway, golang-migrate, or equivalent)
- Familiarity with graph data models and graph databases (Neo4j, AWS Neptune) or graph-like query patterns in relational systems (recursive CTEs, ltree, adjacency list)
- Proficiency in Go or Python — able to write production application code, not just SQL
- Demonstrated track record of defining database architecture at scale — from design doc to production — across multiple companies or teams
- Strong opinions on data architecture tradeoffs: normalization vs. denormalization, consistency vs. availability, OLTP vs. OLAP workload separation, schema-first vs. schema-last design
- Ability to reason about long-horizon schema design: what does this schema look like in two years, at 10× current data volume, with three new feature teams writing to it?
- Ability to communicate complex database decisions clearly in writing — for design docs, ADRs, and cross-team reviews — so engineers without deep DB expertise can understand and apply the reasoning
- Proven ability to drive database standards across multiple teams without direct reporting authority
- Experience establishing database engineering culture: schema review norms, migration safety standards, and query performance review processes
- Track record of growing engineers through code review, pair programming, and architectural mentorship — especially engineers strong in application code but earlier in database expertise
NICE TO HAVES:
- Background in cybersecurity data: vulnerability databases, network scan schemas, or attack surface management data models
- Experience with time-series databases (TimescaleDB, InfluxDB) in addition to relational
- Familiarity with data platform compliance requirements: SOC 2 Type II, FedRAMP data handling, or GDPR/CCPA
- Experience with analytical query patterns or BI/reporting workloads on operational data
- Contributions to open-source database tooling or PostgreSQL ecosystem projects
