Kalshi
Software Engineer, Product
New York Office$200k–$280kfulltimemidAdded 1 month ago
About this role
Build user-facing systems and internal tools for Kalshi, a high-growth prediction market platform. You'll design scalable backend services and data-driven features that power trading, discovery, and position management while working closely with product and design teams.
What you'll do
- Design and implement high-performance backend services and APIs for trading features at scale
- Architect personalization engines, recommendation algorithms, and data-driven engagement features
- Partner with product managers and frontend engineers to pilot and launch new initiatives
- Refine product requirements into clear technical specifications
- Maintain systems supporting rapid feature testing and experimentation
- Support low-latency, dynamic trading interfaces
What they're looking for
- Golang or Java programming
- REST API design and development
- Relational databases (PostgreSQL, MySQL)
- NoSQL databases (MongoDB)
- Cloud platforms (AWS, Azure, or GCP)
- Websockets and event-based infrastructure
- A/B testing and growth experimentation frameworks
- Fast-paced environment execution
Benefits
- Salary: $200,000–$280,000 annually plus equity
- New York office location
- High ownership and autonomy in role
- Work on a mission-driven financial platform
- Collaborative culture valuing meritocracy and craftsmanship
- Equal opportunity employer with commitment to inclusion
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Kalshi
Kalshi builds a prediction market trading platform and exchange infrastructure. The company is hiring frontend engineers, backend engineers, site reliability engineers, infrastructure engineers, and mobile engineers to scale its rapidly growing financial trading systems.
View all jobs at KalshiLikely interview questions
- Walk us through a high-performance backend service you've built. How did you handle scalability, and what databases or caching strategies did you use?
- Describe your experience designing and iterating on REST APIs. How do you balance simplicity with the needs of frontend and partner integrations?