TL;DR: Joined SolanaFM as a Backend Engineer in a fast-paced, high-growth environment. Worked on mission-critical infrastructure serving the Solana ecosystem, including updating the Search API to support fuzzy text search and redesigning general API routes to scale beyond 300 concurrent users. The experience was transformative—learning industry-standard practices from talented engineers while contributing to an ambitious, forward-looking project.
Key lessons: pressure-cooked environments accelerate growth, working alongside talented people elevates your own skills, and applying industry standards to real production systems builds deep understanding.
🛣️ The Journey
Joining SolanaFM at Backfill Pte Ltd was an eye-opening experience. As a backend engineer on a team building critical infrastructure for the Solana blockchain ecosystem, I stepped into an environment that demanded excellence and rewarded rapid learning.
SolanaFM serves as a blockchain explorer and analytics platform for Solana—a high-performance blockchain processing thousands of transactions per second. Our infrastructure needed to match that pace, providing developers and users with real-time insights into on-chain activity. The stakes were high, the technical challenges complex, and the learning curve steep.
From day one, the pace was relentless. This wasn't a slow onboarding into comfortable work—it was immediate immersion into production systems handling real user traffic, real performance constraints, and real consequences for downtime or bugs.
🔥 The Pressure-Cooker Environment
1. ⚡ Fast-Paced by Design
The environment at SolanaFM was intentionally fast-paced. Blockchain moves quickly—new protocols, shifting user demands, competitive pressure from other explorers. We couldn't afford to move slowly.
What made it work was that the pace wasn't chaotic. It was structured intensity: clear priorities, rapid iteration cycles, frequent deployments, and a culture that valued shipping working solutions over perfect solutions. You learned to make decisions with incomplete information, to balance speed with reliability, and to ship confidently even when nervous.
This kind of environment pressure-cooks great engineers. There's no time to overthink. You build, you deploy, you learn from production, you iterate. The feedback loops are tight, which means you learn faster than you would in slower-paced settings.
2. 🎯 Ambitious and Forward-Looking
The project itself was ambitious. SolanaFM wasn't just building another blockchain explorer—we were building infrastructure that developers across the Solana ecosystem depended on. Our APIs powered dApps, analytics platforms, and developer tools. Our uptime and performance directly impacted their success.
The forward-looking nature of the work meant we weren't just maintaining existing systems. We were constantly improving, scaling, and adapting to the evolving needs of the blockchain space. Every sprint brought new challenges that demanded creative solutions.
3. 🤝 Talented and Friendly Team
What made the intensity sustainable was the team. Working alongside talented engineers who were both skilled and genuinely friendly created an environment where you could learn without fear of judgment. When you're surrounded by people who know more than you, every code review becomes a learning opportunity. Every architectural discussion becomes a masterclass.
I took a lot home from those interactions—not just technical knowledge, but ways of thinking about problems, patterns for designing systems, habits of excellence that only come from watching great engineers work.
🛠️ The Technical Work
1. 🔍 Fuzzy Search Architecture
One of my key contributions was updating the SolanaFM Search API architecture to support fuzzy text search. Previously, our search required exact matches, which created friction for users trying to find transactions, addresses, or programs without precise input.
Implementing fuzzy search in a high-performance context required balancing user experience with system performance:
- Evaluating search algorithms that could handle approximate matching at scale
- Optimising indexing strategies to support fuzzy queries without degrading response times
- Testing edge cases where fuzzy matching could return confusing or irrelevant results
- Ensuring the system remained performant under load while handling more complex queries
The result was a search experience that felt more intuitive and forgiving, reducing user frustration and improving the overall platform usability.
2. 📈 Scaling API Routes for Concurrency
Another critical project was redesigning and scaling the SolanaFM general API routes to accommodate more than 300 concurrent users. As the platform grew, we hit bottlenecks that threatened reliability during traffic spikes.
This work involved:
- Profiling existing routes to identify performance bottlenecks—database queries, inefficient algorithms, resource contention
- Redesigning API architecture to support higher concurrency through better connection pooling, caching strategies, and asynchronous processing
- Load testing to validate that the new design could handle target concurrency whilst maintaining acceptable response times
- Implementing monitoring and alerting to catch degradation before it impacted users
Scaling infrastructure isn't just about making things faster—it's about building systems that remain reliable and responsive under pressure. This project taught me how to think about performance not as an afterthought but as a core design consideration.
📚 Learning Industry Standards
Beyond specific projects, the real value of SolanaFM was learning and applying industry-standard practices to actual working projects. This wasn't theoretical knowledge from textbooks—it was practical wisdom earned in production:
- API design patterns: RESTful principles, versioning strategies, error handling conventions that made APIs maintainable and developer-friendly
- Database optimisation: Query optimisation, indexing strategies, connection pooling, and handling high-read workloads
- System observability: Logging, metrics, tracing, and building systems that could be debugged in production
- Code quality practices: Testing strategies, code review culture, documentation habits that made codebases sustainable
- Deployment and DevOps: CI/CD pipelines, blue-green deployments, rollback strategies, and infrastructure-as-code
These aren't things you truly understand until you've applied them in real systems with real consequences. Reading about database optimisation is one thing; diagnosing a slow query that's impacting production traffic is another.
🏫 The Lessons
1. 🔥 Pressure-Cooker Environments Accelerate Growth
The intensity of SolanaFM wasn't for everyone, but for engineers ready to level up quickly, it was transformative. When you're pushed to solve hard problems under time constraints, you develop skills and confidence that would take years to build in slower environments.
The key is that the pressure came with support—talented teammates, clear priorities, and a culture that valued learning. Intensity without support burns people out. Intensity with the right support forges stronger engineers.
2. 👥 Talented People Elevate Your Game
Working alongside engineers who are better than you is one of the fastest ways to grow. Their standards become your standards. Their patterns become your patterns. Their way of thinking about problems shapes your own approach.
I learned more from code reviews and architectural discussions at SolanaFM than I could have from months of solo study. There's no substitute for direct exposure to excellence.
3. 📖 Theory Meets Practice
Industry-standard practices only become real when you apply them to production systems. It's one thing to know that caching improves performance; it's another to implement a caching layer that handles cache invalidation correctly, scales with traffic, and doesn't introduce subtle bugs.
SolanaFM gave me the opportunity to take theoretical knowledge and make it practical. That bridge from theory to practice is where real engineering skill develops.
4. 🚀 Ambitious Projects Demand Your Best
Working on infrastructure that developers depend on raises the stakes. You can't ship sloppy work when downtime or bugs impact other people's businesses. That pressure to deliver reliable, performant systems forces you to care deeply about quality.
Ambitious projects demand your best work, and in return, they make you better.
🎯 The Takeaway
My time at SolanaFM was transformative. The combination of a fast-paced environment, ambitious technical challenges, and a talented, supportive team created ideal conditions for rapid growth. I came away not just with technical skills but with a deeper understanding of what it means to build production systems that matter.
The experience reinforced that growth happens at the edges of comfort—when you're pushed to solve problems slightly beyond your current ability, surrounded by people who can help you level up. SolanaFM provided exactly that environment, and I'm grateful for everything I learned there.
Gallery
Gallery view