We're building what we wish existed

psyflo started because too many students are struggling alone, and the people who want to help them don't have the tools to reach them all.

Why we built this

I know what it's like to struggle as a kid and have no one at school notice.

When I was young, I experienced trauma that shaped everything: how I showed up in class, how I connected with people, how I saw myself. But no one at school knew. There was no system to catch it, no adult who had visibility into what I was carrying. I got through it eventually, but not because the school helped. In spite of the fact that it didn't.

Years later, I went into public health because I wanted to fix that. I saw the data: 1 in 3 students are struggling with their mental health. School counselors are stretched past the breaking point. Kids are falling through the cracks not because no one cares, but because the systems aren't built to see them.

psyflo is what I wish had existed for me, and what I believe every student deserves. A way to be seen before you're in crisis. A way to build skills on your own. A bridge to the people who can help.

Deanna Oliver, Co-Founder & CEO

You are joining as the first full-time engineer. You will own engineering end to end at Psyflo. You will set the technical direction of the platform alongside the founders, ship production code from day one, and build the engineering foundation that the next five hires will inherit. Your upward mobility here is endless. This is the kind of role where the right person grows into Head of Engineering or CTO as the team scales. You will report directly to the CEO and work alongside our clinical advisor and contract engineers during transition. Team today: two non-technical founders and part-time contractors. You will be the first full-time engineer.

Platform architecture and delivery • Provider dashboard, patient mobile app, practice manager portal, and admin portal across web and mobile. • Shared clinical databases including the ICD-10 diagnosis library, screener library, daily monitoring engine, and therapeutic exercise engine. • Billing logic that turns clinical activity into clean claims data. AI and agentic workflows • Claude-powered features for screener interpretation, check-in summarization, and clinical signal detection. • Multi-agent workflows that coordinate intake, monitoring, escalation, and provider notifications. • Lightweight integrations with the Anthropic API, including tool use, structured outputs, and prompt versioning. • Guardrails and evaluation infrastructure to keep clinical outputs safe, consistent, and auditable. Infrastructure and compliance • HIPAA-compliant production environment including encryption, audit logging, access controls, and BAA management. • SOC 2 readiness, including the policies, controls, and evidence collection needed for a Type II report. • CI/CD, observability, incident response, and on-call coverage for the first year. Technical leadership • Architectural decisions on data models, API design, multi-tenancy, and integration patterns. • Hiring rubric and technical interviews for engineers two through five. • Documentation and engineering practices that scale past the founding team.

• Four or more years of production software engineering experience. • Strong working depth in TypeScript across both frontend and backend. • Production experience with React and a modern meta-framework such as Next.js or Remix. • Solid PostgreSQL and SQL skills, including schema design, migrations, and query optimization. • Experience integrating LLM APIs into production features, including prompt design, tool use, and basic evaluation. • Comfort building multi-step agentic workflows, even if you have not labeled them that way before. • Demonstrated experience shipping HIPAA-compliant systems handling protected health information. • Multi-tenant SaaS architecture experience with clear tenant isolation requirements. • Track record of owning systems end to end in production, including on-call and incident response. Strongly Preferred • Prior experience at a digital health, healthtech, or other regulated industry company is a huge plus. • Founding engineer or first-five engineering hire experience at a healthtech startup. • Familiarity with Supabase, Row Level Security, and edge function patterns. • Understanding of EHR integration patterns. Hands-on integration experience is a plus but not required. • Behavioral health domain experience, either professional or personal. How You Work • You write the documentation before you are asked because you know you are the institutional memory until hire number three lands. • You ship under ambiguity, then come back and harden what you shipped once the requirements settle. • You treat LLM-powered features with the same rigor as the rest of the stack, including tests, evals, and rollback paths. • You will have additional support from an offshore contractor as needed during the first year, so you are not building this alone. • You hold a high bar for clinical accuracy and patient safety because the work touches real people in real distress.