Fireblocks
Mobile Engineer
About this role
Join Dynamic (part of Fireblocks) to build native mobile SDKs that enable developers to integrate embedded wallet functionality into crypto and fintech applications. You'll own SDK features end-to-end—from architecture and implementation through documentation and customer support—while maintaining institutional-grade security and exceptional developer experience.
What you'll do
- Design and implement high-quality native mobile SDKs with focus on API design, performance, and reliability
- Own SDK features end-to-end from architecture through release, versioning, and documentation
- Build and maintain secure components for wallet operations, cryptographic functions, and blockchain interactions
- Define and evolve SDK architecture to support maintainability, backward compatibility, and customer adoption
- Create sample applications, demos, and comprehensive integration guides for developers
- Collaborate with developer relations and support teams on customer integration challenges
What they're looking for
- Mobile development (iOS/Swift and/or Android/Kotlin)
- Mobile SDK design and development
- Blockchain and cryptocurrency systems
- Security-sensitive software (key management, cryptography, financial systems)
- API design and versioning strategies
- Testing, CI/CD, and release management
- Cross-platform frameworks (React Native experience beneficial)
- Code review and technical documentation
Opens the official application on the employer’s site. No login required.
Fireblocks
Fireblocks builds a blockchain-based digital asset platform that enables financial institutions to securely manage and transact cryptocurrencies at scale. The company is hiring Sales Engineers, Mobile/Full Stack Engineers, and AI/Data professionals to expand its core wallet infrastructure, embedded SDK offerings, and data-driven decision-making capabilities.
View all jobs at FireblocksLikely interview questions
- Walk us through a mobile SDK you've built or contributed to—what were the key design decisions around API ergonomics, and how did you handle versioning and backward compatibility?
- Describe your experience with security-sensitive mobile development, particularly around key management, secure storage, or cryptographic operations. What practices did you implement to ensure security?