Talos Trading
Software Engineer, Tokenization
About this role
Talos is seeking a backend software engineer to develop and maintain high-performance systems powering tokenized asset trading infrastructure. You'll design scalable APIs, integrate with external platforms, and ensure enterprise-grade reliability for institutional digital asset markets.
What you'll do
- Design and develop backend services for tokenization and trading workflows
- Build and optimize distributed systems for performance and scalability
- Design REST, gRPC, and WebSocket APIs for internal and external integrations
- Lead third-party platform and custodian integrations
- Contribute to system architecture decisions for enterprise reliability
- Manage full development lifecycle from design through production monitoring
What they're looking for
- Backend engineering (Go, Java, or C++)
- Large-scale distributed systems design and operation
- REST, gRPC, and WebSocket API development
- Performance optimization and concurrency
- Enterprise-grade software development
- Third-party system integration
- Crypto trading systems (preferred)
- Financial infrastructure experience (preferred)
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.
Talos Trading
Talos Trading builds institutional-grade digital asset trading infrastructure and platforms, providing portfolio construction, optimization, strategy execution, and tokenized asset trading for institutional clients. The company is hiring backend engineers, technical solutions engineers, and go-to-market specialists to develop high-performance core systems, manage client integrations, and drive customer acquisition.
View all jobs at Talos TradingLikely interview questions
- Walk us through your experience designing and operating large-scale backend systems. What was the most complex distributed system challenge you've faced, and how did you solve it?
- Describe your experience building REST, gRPC, or WebSocket APIs for integrations. How do you approach API design when integrating with external third-party platforms?