Careers
We are not hiring.
When that changes it will appear here first. If the problem is one you would pick on purpose, write now — the people who reach out before there is a role are the ones we call when there is one.
What we look for
Deep technical depth and pragmatism.
We value people who understand systems deeply: how computation flows, where time goes, how to measure what matters. You should care about user workloads, not abstractions for their own sake. You should be skeptical of benchmarks and rigorous about claims.
Background in compilers, databases, numerical computing, distributed systems, or performance engineering is a strong signal. Curiosity about how your code actually runs matters more than resume keywords.
The first two roles
Where the work goes next.
The first hire takes the runtime from a benchmark harness to a library other people integrate without us in the room. The second sits with a customer's workload trace and gives an honest verdict on it, including the verdict that they should keep their current baseline.
Get in touch
Say so early.
Email admin@hornesci.com with a note on what draws you to the problem space. Low-level performance work on fixed sparse operators is the shape of it. The use-cases page is the fastest way to tell whether it is your kind of problem.