The Five Seats
What each founding teammate would own
Each seat owns one part of what it takes to build AVERY and bring it to government, defense, and enterprise security teams. Titles matter less than ownership, and the seats will be shaped by the people who take them.
Seat 01
Founding CTO (Chief Technology Officer)
Owns AVERY’s technical direction, starting with what it finds and whether an analyst can trust and act on it.
What you would own
- AVERY’s architecture and technical roadmap, and building the engineering team as it grows.
- Detection logic and signal scorers for command-and-control, lateral movement, and credential misuse.
- MITRE ATT&CK mapping and the evidence attached to every finding.
- Validation through adversary emulation and red-team exercises, with results reported honestly.
Good fit: Detection engineers and threat hunters who have worked with network or host telemetry at scale and are ready to lead AVERY’s engineering.
Seat 02
Founding Head of Data Science & Research
Owns whether AVERY’s detections hold up: baselines, scoring, and evaluation.
What you would own
- Per-entity baselining and how independent signals are fused into a finding.
- Keeping false positives bounded as the number of signals grows.
- Evaluation on public labeled datasets with held-out validation, and the research NorthQuinn publishes.
Good fit: Data scientists and research engineers comfortable with time series, anomaly detection, and evaluation design.
Seat 03
Founding Platform & Infrastructure Engineer
Owns the platform AVERY runs on, built to be secure by design.
What you would own
- The telemetry pipeline, authenticated intake, and data storage.
- Cloud and on-premises architecture that keeps government and defense deployment options open.
- Secure development practices, reliability, and operating cost.
Good fit: Software and platform engineers who have built production data systems that had to be secure.
Seat 04
Founding Head of Go-to-Market, Federal & Enterprise
Owns how AVERY reaches its first users, from design partners to the path to federal contracts.
What you would own
- First design partners and pilots with SOC teams, government agencies, and the defense industrial base.
- Federal business development and the contracting pathways that fit an early-stage company.
- Positioning, pricing, and bringing what customers say back into the product.
Good fit: People who have brought technical security products into federal, intelligence-community, defense, or enterprise organizations.
Seat 05
Founding Head of Security, Compliance & Federal Readiness
Owns what it takes for government and defense organizations to trust and adopt AVERY.
What you would own
- Readiness for the frameworks government and defense buyers require, such as NIST SP 800-171, CMMC, and FedRAMP.
- NorthQuinn’s own security program and secure development lifecycle.
- Customer security reviews and authorization documentation.
Good fit: Security and compliance practitioners who have taken systems through federal authorization or defense-industry assessments.
Your Seat
Not an exact match?
If you could own a hard part of AVERY that isn’t described here, tell us what it is and what you have built.
Start the conversation