Chief Research Scientist

The Role

You are the founder's technical counterpart. You can hold an entire cognitive architecture in your head — memory systems, inference loops, attention mechanisms, governance integration — and push it forward without being told what to do next. You don't need a roadmap. You see the architecture, you see the gaps, you fill them.

This is not a management role that happens to involve research. This is a hands-on, code-writing, architecture-shaping role that happens to set direction for the research team.

What You'll Do

• Co-architect the evolution of MABOS alongside the founder
• Define and execute the research agenda for cognitive systems, memory, inference, and attention
• Review and approve all architectural changes to core MABOS subsystems
• Mentor and direct the research engineering team
• Represent Ceridwen.ai's technical capabilities to external partners, regulators, and the research community

Requirements

• PhD in computer science, cognitive science, neuroscience, or adjacent field — or equivalent depth demonstrated through published work and shipped systems
• 10+ years building production-grade AI/ML systems, not prototypes
• Deep expertise in at least three of: cognitive architectures, memory systems, attention mechanisms, reinforcement learning, neurosymbolic reasoning
• Rust fluency strongly preferred. Willingness to work exclusively in Rust required
• You have built something from the ground up that other people now depend on

Compensation

All positions include equity in Ceridwen.ai. Salaries are TBD and will be determined based on role scope, experience, and what you bring to the table. We will not insult you with a lowball offer, and we expect you not to waste our time with inflated expectations disconnected from contribution.

The Builder Clause

We don't care where you went to school. We don't care if you went to school. Our founder is self-taught, started coding at 13, and built a 602,000-line cognitive architecture without a CS degree.

Meet the qualifications, or show us what you've built. Either path works. Both paths demand excellence.

Apply

Ready to move? Send a short note of relevant proof-of-work — past shipped projects, metrics you moved, or a draft of your first 30 days.