Reactions from ranked influencers
2 posts
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, we’ve 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.
Kalshi raises the bar for superstar engineering talent.
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.