Job Description

We are building the open infrastructure for neurological data that will define
the next era of the field. A foundation that lets brain data remain useful
across institutions, survive decades of retention, and become readable by the
AI tools that will reshape diagnosis and treatment. Our compression technology
is in production at leading research and clinical neurology institutions. We
have a Public Benefit Corporation charter, a founding team with deep clinical,
enterprise, and company-building experience, and a clear technical wedge.

We are hiring our founding Cloud/AI Chief Architect. You will design and lead
the data infrastructure for everything that comes next.

**Who you would be joining**

This is a rare combination for a founding team in neurotech. Building
infrastructure for clinical-grade brain data demands four things at once:
clinical and scientific credibility, enterprise-scale execution, healthcare
go-to-market depth, and serial-entrepreneur experience. Most teams have one or
two. We brought together founders who cover all four.
What we are missing is your domain: cloud and AI infrastructure architecture,
built for sensitive data at scale.

Patient benefit is in our charter. We believe patients should have more
control over their own health data than today's systems allow. The
architectural decisions you make about data governance, consent, and access
build on a foundation designed to outlast any one of us.

**The role**

You will own the data infrastructure that makes longitudinal neurological care
possible at scale, including cloud architecture, the security model, and how
we design for AI as a consumer of the data we hold. You will make the first
engineering hires when funding lands and shape the technical direction of the
company from there.

**What we are looking for**

The landscape changes fast — AI capabilities, regulatory shifts, new threat
models, what hospitals will accept. We expect you to be learning alongside us.
You have done most of this. Where you have not, you are honest about it and
actively building toward it. The right person finds that energizing.

_Cloud and data infrastructure_
• You have built and operated production cloud infrastructure for sensitive
data at scale, somewhere that getting it wrong was not an option. You can talk
about what broke, what you fixed, and what you would do differently.
• You have shipped HIPAA-compliant architecture, navigated BAAs, designed
audit trails, and survived hospital security reviews. Equivalent depth from
financial services, defense, or government will be considered if you can make
the case for how your discipline transfers.
• You have designed federated or multi-tenant systems where data sovereignty,
residency, and access governance were architectural decisions made from the
start.

_Security_
• You design for the world we are building. Crypto-agile architecture, post-
quantum migration, and the AI-era attack surface (prompt injection, model
exfiltration, data poisoning) are things you are actively thinking about and
have started designing for.
• You have shipped systems mapped to NIST CSF, ISO 27001, HITRUST, or CIS
Controls, and you know which one fits a hospital customer versus a research
institution versus a regulated industry partner.
• You have designed encryption architecture at the file and system level. You
have run key management at scale (HSMs, KMS, BYOK, rotation) and shipped
tenant isolation patterns and immutable audit logging that survived real
compliance reviews.

_Designing for AI workloads_
• You are actively designing for the world where AI models are primary
consumers of data. You don’t need to have shipped this at production scale.
Few people have. But you have started, you have opinions, and you can talk
through the architectural questions you are wrestling with.
• You have shipped open source production infrastructure or contributed to
open source communities. Bonus if you can point to projects others now depend
on.

**How you work**
• You use modern AI development tools (Claude Code, Cursor) as a force
multiplier, and you can show what you have built with them in the last six
months.
• Zero-to-one operator. You have built things from scratch in environments
where scope was undefined and the right call had to be made without complete
information.

**The honest tradeoff**

This is an early, founding-team role, and the comp reflects that: equity-
heavy, with cash that grows as the company does. The equity range depends on
the person and how we balance it against salary, so we'll figure that out
together. What's fixed is what you'd get: real architectural ownership, the
chance to set the technical direction from the start, and a mission worth the
next chapter of your career.