Home / Engineering / C-BRAIN Principal Software Development Engineer (Remote) - Neurology

C-BRAIN Principal Software Development Engineer (Remote) - Neurology

Washington University in St. Louis · Remote

C-BRAIN Principal Software Development Engineer (Remote) - Neurology is open at Washington University in St. Louis (Remote). The posting gives a salary of $130K - $228K. Posted on Nov 18, 2026, and still on Washington University in St. Louis’s careers page when we last checked, on Nov 18, 2026.

About the role

Location

Remote, US



Scheduled Hours

40

Position Summary

The Consortium for Brain Research and AI in Neurodegeneration (C-BRAIN) is an academic-industry consortium directed by Dr. Randall J. Bateman, Washington University School of Medicine in St. Louis. C-BRAIN brings together academic research institutions, pharmaceutical and biotech companies, technology partners, philanthropic organizations, and government agencies to develop AI-powered tools to accelerate discovery in Alzheimer's disease and neurodegenerative disorders. Washington University serves as the coordinating center for C-BRAIN. C-BRAIN is currently deploying initial versions of the tools and developing plans for benchmarking and evaluation of the tools in addition to platform integration and scaling. C-BRAIN is also working on development of foundational AI models for brain aging and neurodegeneration. See www.c-brain.org.

The C-BRAIN Principal Software Development Engineer is the senior architect and technical lead for the platform behind C-BRAIN's AI research tools, including InsightEngine and OpenScientist. Reporting to the C-BRAIN Senior Technical Product Manager, who leads C-BRAIN platform engineering, within the overall technical direction set by the C-BRAIN Chief Technology Officer (CTO), this role owns the architecture, technical design, and technical delivery of the integrated platform: one system in which research tools, AI agents, and the foundation models C-BRAIN builds share a common data model, permission model, and deployment path. The role turns the platform roadmap and its requirements for scale, security, cost, and interfaces into a target architecture, detailed designs, interface contracts, and working software, and leads the incremental move from today's services toward that target, including durable, sandboxed execution of long-running agent jobs, a gateway through which agents reach C-BRAIN tools, data, and models, Rust services for the security-critical core (the job launcher, model proxy, and execution broker), an event-driven data layer with fine-grained access control, a web workspace with desktop and mobile clients where they add value, and inference on approved and self-hosted open-weight models, while keeping current tools reliable and secure.

The ideal candidate has designed and operated systems at significant data and user scale, has led migrations of production systems without stopping delivery, and can turn an architecture into well-scoped work that C-BRAIN engineers and partner development teams can build to. This is not a prototyping position. C-BRAIN-specific context will be provided; architecture and production engineering fundamentals will not. Knowledge of neurodegeneration research data is a plus, not a requirement.

Job Description

Primary Duties & Responsibilities:

Architecture and Technical Leadership

  • Own the architecture of the integrated platform: define the target system, service boundaries, interface contracts, and the migration path from current services so the platform meets its requirements for scale, security, cost, and interfaces, and record decisions in architecture decision records.
  • Break the architecture into well-scoped work packages with clear interfaces and acceptance criteria that C-BRAIN engineers and partner development teams can build to, and review delivered work against them.
  • Serve as technical lead for a team of about seven engineers, including engineers from partner development teams: set day-to-day technical direction, lead design and code reviews, and set coding standards and the definition of done.
  • Own technical planning and execution for the team: scope and sequence work, lead estimation and sprint planning, run stand-ups and retrospectives when needed, and surface risks and dependencies early.
  • Maintain CI/CD with required tests, type checks, and security scans; branch protection; code owners; and staged promotion from development to staging to production.
  • Mentor engineers through pairing and review, work with the open-source maintainers of the tools C-BRAIN builds on, including contributing C-BRAIN's changes to upstream repositories under shared review, and set team practices for AI coding assistants with human review of every change.

Platform Integration and Migration

  • Lead the integration of InsightEngine and OpenScientist into one platform: bring existing capabilities in as modular tools behind a common agent and job framework and a shared tool gateway, and retire duplicated services.
  • Migrate incrementally toward the target architecture, replacing security-critical and high-throughput components (for example, the job launcher, model proxy, and execution broker) with Rust services behind stable interfaces, keeping agent and scientific code in Python, while current C#/.NET, Python, and TypeScript services stay in production.
  • Build an event-driven data layer: typed event streams and live query subscriptions driven by database change notifications, so user interfaces, services, and agents react to new data and jobs without polling.
  • Lead the decision on the client stack and deliver it: a web workspace that streams agent work as typed events (for example, React and TypeScript on the AG-UI protocol, or Rust frameworks such as Leptos or Dioxus), and desktop or mobile clients where they add value (for example, a Tauri shell), with offline operation and synchronization where required.
  • Provide a plug-in architecture and versioned APIs for adding scientific tools and services, including Model Context Protocol (MCP) servers.

Model Serving and Inference

  • Design C-BRAIN's inference layer so confidential research data is processed only by approved models in approved environments, including the confidential computing environments consortium data agreements require, and keep the platform independent of any single model provider.
  • Deploy and serve open-weight LLMs on GPU infrastructure, and support researchers who run approved models on their own hardware, so the platform can grow without depending solely on centrally hosted compute.
  • Integrate foundation models and assemblies of expert models into the platform with C-BRAIN applied scientists: route each request to the right expert, version models, and serve them reliably as use grows.
  • Package and deploy models trained on C-BRAIN's governed data and model-training platform into C-BRAIN tools through a model registry and release review, with signed artifacts, model cards, and provenance.

Data, Access and Security Engineering

  • Design and maintain a shared scientific data model (organizations, teams, projects, ownership, and third-party datasets) with PostgreSQL row-level security and relationship-based fine-grained authorization.
  • Ensure agents and automated jobs act only with the permissions of the user who submitted them, and enforce tenant isolation across every data store.
  • Build the services that let agents use governed data safely: short-lived credentials for each run, an entitlement check on every tool call, and aggregate queries released only after disclosure checks.
  • Own application and cloud security: OpenID Connect and OAuth 2.0, federated sign-in across member institutions and companies, token and API key design, secrets management, least-privilege service identities, encrypted local storage on client devices, and safe execution of AI-generated code.
  • Build provenance tracking and tamper-evident audit logging so every result traces to its data, code, model, and user, and set data-management policies with C-BRAIN data engineers and governance partners.
  • Run vulnerability management with risk-based remediation; partner with Washington University information security; lead remediation of penetration test findings and readiness for an independent security examination (for example, SOC 2); prepare codebases for public open-source release.

Reliability, Operations and Scale

  • Design for scale: capacity and performance planning for large data volumes, many concurrent users, and long-running agent workloads, using cloud-agnostic infrastructure-as-code, and prove capacity with load rehearsals before major events.
  • Make agent jobs durable and isolated: workflow orchestration that survives restarts and deployments (for example, Temporal or DBOS), a stateless web tier, and a sandboxed container for every job and code execution on Kubernetes (for example, Kata Containers).
  • Build observability (centralized logging, metrics, tracing, alerting, and service-level objectives) and serve as primary technical responder for production incidents. After-hours expectations are agreed with the Senior Technical Product Manager.
  • Operate production services (deployments, rollbacks, migrations, backups, and tested restores) and track and control cloud, GPU, and LLM costs, including model provider quotas and spending limits per user and organization.

Working Conditions:

  • Remote within the United States, per current Washington University policies.
  • Occasional on-site presence required for team meetings and consortium events.
  • Occasional domestic travel may be required for consortium events, partner meetings, or conferences.
  • Standard office environment.
  • Primarily sedentary with standard computer use.

The above statements are intended to describe the general nature and level of work performed by people assigned to this classification. They are not intended to be construed as an exhaustive list of all job duties performed by the personnel so classified. Management reserves the right to revise or amend duties at any time.

Required Qualifications

Education:

Bachelor’s degree or combination of education and/or experience may substitute for minimum education.

Certifications/Professional Licenses:

No specific certification/professional license is required for this position.

Work Experience:

Relevant Experience (8 Years)

Skills:

Not Applicable

Driver's License:

A driver's license is not required for this position.

More About This Job

Required Qualifications

  • Demonstrated ownership of the architecture of a production system at significant data or user scale, including its data model, access control, and evolution over time.
  • Demonstrated experience as a technical lead: guiding the work of other engineers through design, code review, and delivery.
  • Production experience in Rust and Python, with Git, code review, and automated testing.
  • Working proficiency in TypeScript, and the ability to read C#/.NET, sufficient to maintain and migrate existing services and web front ends.
  • Hands-on experience running production workloads on a major public cloud, including containers, identity and access management, and infrastructure-as-code.
  • Demonstrated application security work: implementing OpenID Connect / OAuth 2.0, securing APIs, and remediating vulnerabilities in code.
  • Experience building or operating LLM-based applications with real users.

Preferred Qualifications

The employer’s own description, as published on Washington University in St. Louis’s careers page.

Hiring at Washington University in St. Louis

Washington University in St. Louis has 240 open roles right now, 17 of them remote. Most are in Healthcare, Data & Research and Finance & Trading. The median advertised salary across its roles with a published range is $80K. See all its roles

✓ Actively hiring 105 roles posted in the last 7 days✓ Few old postings 0% open 90 days or moreWhat the marks mean

Similar Engineering jobs

All Engineering jobs
Apply on company site