Betable is hiring awesome software engineers.
Betable is the only platform that allows unlicensed game developers to build legal gambling games for any device. We handle the math, the money, and the legal; game developers do what they do best: games.
We're looking for engineers that can build the APIs that our game developers use. Engineers that understand the virtues of testable, composable service-oriented architectures. Engineers who love an algorithmic challenge and are ready to dust off their college statistics textbooks (not really - we already have a copy). We use Cassandra heavily and program in Go, Java, and Node.js. You may not know all or even any of these technologies but you're quick to learn and comfortable building distributed systems. We're changing online gambling for the better and we need your help.
Betable engineering is an elite team of hardworking dreamers and tinkerers. We’re pragmatic, but we don’t let that interfere with our perfectionism. We’re fluent in computing concepts from anonymous memory management to monadic zeros.
We’re building a platform. Engineering innovation is our competitive advantage. We’re doing something new and different in an industry that hasn’t seen any real innovation in the last century. That excites us.
We try to be technology agnostic, preferring suitability to ideology. Our services are small and chatty, communicating through well-defined interfaces. Sometimes we compose them in ways that are surprising even to us. We think that’s healthy for a platform company. In general, we believe that sound system architecture and design are more important than any particular technology.
Day to day we use Node.js, Cassandra, Jenkins, Go, Java, Puppet, and GitHub. We like continuous integration. In fact, we like most forms of process automation. Sometimes our tools make us happy, sometimes they make us sad. When they make us sad, we make them better.
We like to work. We love to play. We don’t consider these activities mutually exclusive.
There aren’t many of us. We’re looking for more.
You’re an engineering powerhouse who wants to work on challenging problems with a group of equally amazing colleagues. Your depth of knowledge in many areas of computing should qualify you as a specialist, but your breadth of expertise demands that you describe yourself as a generalist. Sometimes you think the two aren’t so different, but you resist that sort of reductionism.
You’re well rounded. You have hobbies that don’t involve computers. Despite your expertise, you sometimes surprise casual acquaintances with your profession. You can’t carry a tune but you sing anyways. Your recreational reading includes works by Kurt Vonnegut, W. Richard Stevens, and Dr. Seuss.
You’re not sure whether P equals NP, but the possibility leaves you feeling both titillated and terrified. Sometimes, while considering the repercussions, you lose composure.
Mutable state is your frenemy. You appreciate what Scala has managed to do on the JVM. You’ve developed several profiles of the language, each Turing complete. You’re curious about the future of Go. You’ve toyed with several syntactic variants of your own competing language based on the π-calculus. You’re an expert at SQL, but would never describe yourself that way.
You had a check for $2.56 from Donald Knuth. You cashed it when your bank started displaying digitized check scans in your transaction history because you hate physical media.
You can explain technical concepts to non-technical people. Non-technical people enjoy the experience. At parties your conversations transition seamlessly from Emacs vs. vi to Beatles vs. Stones.
You consider coding a craft – as much art as science. It’s your creative outlet. You consider quines a form of poetry. You often describe code as beautiful.
You’re self aware. Some of these statements don’t apply to you, but you can read between the lines. Others upset you. You understand why at a fundamental level. You can argue your position, and you can win.
Sound like you? Join us.