Today, we're batch shipping 80% of the mobile code we’ve written this past quarter. First, a breakdown of the other 20%: across 42 releases, our 5-person squad launched the first perpetual futures in the US and trading experiences (explore overhaul, 15-minute charts, live chat, World-Cup hub, inner-circle, etc.) that have led Kalshi to top the App Store rankings for most of the past month. But all of this was just a fraction of the team’s firepower. At night, we were quietly working on a big project: “V2”, a complete rewrite of our app and the biggest technical leap I’ve seen since I joined the company 6 years ago. 4000 commits and 1 million lines later, the numbers are in and they justify the crazy sprint we just went through: - CPU usage: 369% peak -> 15% peak - Memory use: 350M -> 70MB - Install size: 315MB -> 95MB (for reference: RH @ 934MB, Coinbase @ 310MB) - External dependencies: 94 -> 11 - Test coverage: 17% -> 100% When you get the update, Kalshi should immediately feel significantly faster, smoother, sleeker, and more responsive. For our product velocity, V2 represents a massive shift as well: we now have a single codebase from which the team can push changes to our backend, iOS, and Android builds. The only code that runs on the client is the code that the team wants to run on the client. We have end-to-end type safety, CI with version-tagged deploys, and client<->server integration tests. We’d already gotten in the habit of daily releases, but with our latest tooling, it’s now a breeze. We’re keeping the team lean, but if you are incredibly talented, work hard, and want to build the next generation financial market,. DM me or apply on our careers website.

When I joined Kalshi back in 2020, the company had just received the regulatory designation it needed to act as a prediction market in the US (after years of work from @luanalopeslara and @mansourtarek_ ), but we still had to actually build the exchange. As an engineer, it felt like such a gift to be a part of that process: the whole team had such conviction in these markets. We dreamed of the day they would be hooked up to trading terminals and referenced by news anchors worldwide. I thought: “if we can just get the systems up and running, people will come.” When we processed our first trade, it felt amazing. But I was also hit with the reality that what we had was not enough: how could we scale to millions of markets a day? How could we support collateral return and margin on events? How do we make even low volume markets liquid? Unlike building a matching engine, these were (and some remain) open questions that hadn’t been solved by a financial exchange before. Thankfully, the team is composed of many of the most hardworking and passionate people I’ve ever met, so though tackling these problems has meant a lot of late nights, it’s never meant a late night alone (shout out to @_rainerds who has been my grinding buddy since the beginning). I'm so grateful to be working alongside each one of you. There is still so much left to do. If you’re interested in joining us, I’d love to chat!