Every classification Prion makes, every conversation Claeth monitors, every task a Worker executes — all of it flows through infrastructure that has to be fast enough to be invisible. The backend at Neuraphic isn't a supporting layer. It's the product. If the platform is slow, unreliable, or compromised, nothing else we build matters.
What you'll work on
The latency budget for Prion's classification pipeline is under two milliseconds. That constraint shapes everything — how services communicate, how data moves, where computation happens. You'll design and build the real-time systems that enforce those constraints at scale, across distributed infrastructure that spans multiple regions.
You'll work on zero-trust architecture from the network layer up. Every service authenticates. Every request is verified. Every data path is encrypted. This isn't bolted on after the fact — it's the foundation you'll help design. You'll build the orchestration layer for Workers, the telemetry pipeline that gives operators visibility into agent behavior, and the APIs that external developers integrate against.
The primary languages are Go and Rust. Go for services where development velocity matters. Rust where latency and memory safety are non-negotiable. You'll make those tradeoffs constantly, and you'll need good judgment about when each is appropriate.
What we're looking for
Someone who thinks in systems, not endpoints. You understand what happens when a service fails at 3 AM under load — because you've been the person debugging it. You've built distributed systems that had to stay up, not just systems that were technically distributed. You know the difference between a service that handles a thousand requests per second in a benchmark and one that does it in production with real traffic patterns.
You care about the details that most engineers skip: connection pool tuning, garbage collection pressure, serialization overhead, tail latencies. You've written code in Go or Rust in production — or you have deep systems programming experience and the will to learn. You're comfortable owning infrastructure end to end, from provisioning to incident response.
How to apply
Email [email protected] with the subject line "Backend Engineer." Include your resume, links to relevant work or open-source contributions, and a brief note on the hardest infrastructure problem you've solved and what made it hard.