The roles listed on the careers page are the ones we know we need. A laboratory this young does not always know, and the useful version of that admission is a door left open rather than a sentence about humility.
What you'll work on
That is the question we would like you to answer. Read the open problems and what has actually come out so far. If you see a gap, or a piece of the work you are unusually placed to take, make the case. The strongest early hires anywhere are the ones who define the seat rather than fill it.
Maybe you work on evaluation and can see that our measurement of harm to legitimate work is the weakest link. Maybe you are an infrastructure person who has run this kind of self-managed fleet at a size we have not reached. Maybe you have depth in privacy or regulatory practice and can see what a documented training corpus is going to require of us next year. We do not know what we do not know, which is the entire point of leaving this open.
What we're looking for
Specificity. The strong open applications are never "I am a generalist"; they are "here is exactly what I would work on, here is why it matters for what you are building, and here is the evidence that I can do it." A concrete criticism of something on this site is a better opening than a summary of your career.
Remote-first means writing well asynchronously is not optional. Early means priorities move and ambiguity is the normal state. If both of those read as features, this may fit.
How to apply
Email careers@neuraphic.com with the subject line "Open Application." Send a resume, links to whatever best represents your work, and a short note on what you would work on if you started tomorrow. Every one is read, and every one is answered, including when the answer is no.