Tomisin Leshi
Full-stack engineer. Five years at LINK building the systems that move money across African borders.
Value Insight
I joined LINK GLOBAL on the frontend. As the routing layer became the product, I moved to backend, designed the multi-corridor architecture, and ended up leading all technical decisions. I ship from API design to the React dashboard.
Proof of Work
- 1:Built the product UI and internal tooling, then moved to backend as the routing layer became the core product.
- 2:Designed the multi-corridor routing architecture that now handles 10+ corridors, including NGN, GHS, KES and ZAR.
- 3:$270K+ in Stellar Community Fund grants for building compliant cross-border payment infrastructure.
- 4:1st place, Base Batch hackathon Europe, for Checkout by LINK GLOBAL: on-chain merchant checkout on Base and Solana.
Where I Worked
- Own the technical direction of the payments platform: architecture, infrastructure, reliability and the engineering roadmap.
- Designed the routing layer that picks the best provider for each currency pair. Three to four million dollars has moved through it.
- Grew the engineering team from just me to four engineers across backend, frontend and security.
- Secured three Stellar Community Fund grants for infrastructure work.
- Sat in on provider and partner negotiations and architecture reviews.
- Moved the v1 retail product onto the upgraded platform through an API service.
- Set up the architecture and code review practices the team still uses.
- Acted as the bridge between founding decisions and day-to-day delivery.
- Built the product's first customer-facing screens, including onboarding and transaction flows for the v1 retail web app.
Introduced microservices for POS and wallet integration, and built the REST API behind daily mobile POS and wallet requests.
Built Python/Django endpoints for an AI business dashboard serving 2K+ concurrent users.
Programmed control and telemetry for an autonomous underwater vehicle, with PID-based navigation in C++.
How I Build
Most bugs live in the gaps: between your API and the next service, between an event and its handler, between what you log and what actually happened. The stack I reach for makes those gaps visible.
Education
Executive Development Programs, Architectural and Building Sciences
Blockchain, Web3 Developer
Bachelor of Engineering, Computer Software Engineering
Activities: Robotics, basketball, Dance