Founding Engineer, Session Engine

Reva reads what someone is recovering from and how they feel today, then builds a gentle session tuned to that state. The session engine is the product: the prompt, the schema that keeps a generated session safe and well shaped, the red-flag screen, the routing across models, and the feedback loop that adjusts tomorrow from how today felt.

You would be the fourth engineer. The work decides whether Reva is trustworthy. A session that is a little too much for someone three weeks out of surgery is worse than no session at all.

• Own the generation pipeline: prompt, schema validation, the deterministic red-flag screen, and model routing with fallback.
• Make the safety net boring and reliable. It should catch the obvious every time, before any model is asked.
• Build the evaluation set. Every prompt change is measured against described states with known-safe answers before it ships.
• Keep the cost per session low without cutting quality, which mostly means routing better rather than prompting cleverer.

• Five or more years building backend systems other people depend on.
• You have worked with language models in production and have opinions about evaluation that came from being burned.
• You write Type Script comfortably, or you will within a fortnight.
• You care about the difference between a demo and a thing someone leans on at 7am, tired and a little scared.

A thirty-minute call with a founder, then a paid work session on a real problem from our backlog, two to three hours, then conversations with two people you would work directly with. Four steps, usually inside two weeks. We tell you where you stand after every one.