As a Solution Architect at Fireblocks, I’ve had the privilege of working at the intersection of cutting-edge technology and real-world enterprise needs in the digital asset space. From day one, it was clear that this company is built on a foundation of innovation, security, and an unwavering commitment to solving complex challenges for our customers.
One of the most rewarding aspects of my role has been collaborating with clients ranging from traditional financial institutions to fast-growing Web3 startups. Fireblocks’ platform is robust, scalable, and constantly evolving. Tools like our MPC-based custody and automated policy engine enable us to deliver secure, flexible solutions that meet each client’s unique needs.
The engineering culture here is top-notch—forward-thinking, agile, and deeply technical. What I appreciate most is that architecture isn’t an afterthought at Fireblocks. The company values long-term thinking and scalable design. As a Solution Architect, I’ve had the autonomy to design solutions that are not only technically sound but also aligned with our customers’ strategic goals.
Cross-functional collaboration is excellent too. Product, engineering, sales, and customer success all work together seamlessly, which makes it easy to bring value to clients and stay ahead of the market. Leadership is accessible, transparent, and genuinely supportive of professional growth and innovation.
If you’re a technologist who thrives on solving real-world problems with real impact—and you want to work on infrastructure that’s shaping the future of finance—Fireblocks is the place to be.
See below as growth brings opportunities.
The fast-paced environment can sometimes lead to shifting priorities, which may require frequent context switching.
Cross-team alignment can be a challenge at times due to the speed of product development.
Workload can be intense during high-growth periods, so time management is crucial.
More structured career pathing and mentorship opportunities would be a great addition.
I interviewed for the Professional Services team. The entire process took a bit more than a month and a half. I had interviews with HR and the VP. After these, I was told that other candidates were being interviewed, so the process would take at lea
The two interviewers were very nice. They asked about my previous job and past projects. Then, they asked questions mainly focused on my understanding and knowledge of programming. There weren't really any direct code questions, but later there was
Asked to describe a recent project and its structure, and any difficulties encountered. The tech lead was a bit aggressive. I noticed when she was writing something over her computer, the other interviewer smiled. The questions were not related to
I interviewed for the Professional Services team. The entire process took a bit more than a month and a half. I had interviews with HR and the VP. After these, I was told that other candidates were being interviewed, so the process would take at lea
The two interviewers were very nice. They asked about my previous job and past projects. Then, they asked questions mainly focused on my understanding and knowledge of programming. There weren't really any direct code questions, but later there was
Asked to describe a recent project and its structure, and any difficulties encountered. The tech lead was a bit aggressive. I noticed when she was writing something over her computer, the other interviewer smiled. The questions were not related to