What we look for
Strong programming, and taste in code
We write code a teammate can pick up cold: readable and testable over clever. We care more about how you think than which language you have lived in.
Systems thinking under ambiguity
You can design something you will still be extending next year: cleanly separated, with your assumptions written down and room to grow. And you keep moving with incomplete information instead of waiting for a perfect spec.
A feel for failure modes
Our systems meet malformed feeds, partial fills and adversarial inputs, where being correct and being fast both matter. You instinctively think past the happy path.
Quantitative rigor
Probability and statistics, empirical skepticism. We test our own ideas against the data before using them.
Ownership
You see what needs doing and do it, without waiting to be asked.
Direct communication
Knowledge is shared by default. Ideas get argued hard; people don't.