Frontend engineering · Web3
Six years shipping React, TypeScript, and Solana products at the design-engineering gap. Currently leading design at Equicomtech on CRPKO, a crypto exchange. Open to Web3 frontend roles where product instinct matters as much as code.
I lead design at Equicomtech on CRPKO (crypto exchange) and ship the frontend that implements it. There is no Figma-to-engineering re-interpretation step. I do both. The design that goes into Figma is the design that ships, because I am the person writing the code.
I prototype features in HTML/CSS against real API responses, not in Figma. The design hits backend reality at design time, not implementation time. Implementation effort drops, fidelity goes up, and the team ships the design, not their interpretation of it.
Pubkey (Discord wallet verification + Web3.js), DeFi Triangle (crypto social side project), OME-sim (Solana order matching engine in Rust, Superteam bounty win), CRPKO (crypto exchange frontend). 10 Superteam wins, $2,530 earned across 45 submissions, most Solana-adjacent.
I will not ship a screen that is visually broken because I would have caught it as a designer first. You do not need a design reviewer on every PR. The product baseline is already there.
Design from the intersection of what we can ship (codebase) and what users expect (research). Not from either side alone.
The CRPKO Subaccount build log is this methodology made visible. Every entry written as the work happens. Read the build log
Leading design and shipping frontend across the web app, mobile design, and the live MVP. Currently designing the Subaccount feature with HTML prototypes against live API data. Full build log in case study.
Build logVerification flow tying Discord identity to a Solana wallet. Worked across the integration surface and the user-facing screens.
Case studyA recently-started personal side project exploring the social side of crypto and trading — the experience around the charts, not just in them.
Project pageProduction-grade order matching engine built in Rust on Solana. Won a Superteam bounty. The kind of Solana-native work that pairs cleanly with the FE side.
GitHubBounty work across Solana ecosystem teams. Volume signal that I ship under real constraints: public deliverables, fixed scope, tight timelines.
Full track recordPlain mapping between what these JDs ask for and the evidence already on the table.
Next.js 16 (App Router, Turbopack), Tailwind v4, custom theme system with FOUC-prevention, image optimization pipeline (sharp → WebP), MDX-free markdown rendering, replica route catch-alls for old portfolio archives. Built and maintained solo.
Source on GitHubLive structured research library I built so my team designs from real shipped evidence, not gut feeling. 95 flows / 102 groups indexed across crypto exchanges and adjacent products. Next.js + Postgres + Supabase, public read-only share URLs, Telegram capture bot.
Case studySix-product OPD-care suite (iPad, iOS, Android, Windows, web) for three multi-specialty hospitals. Solo designer for two years. Earlier career, included for shipped-product breadth.
Case studyIf you're hiring an FE engineer who can own the design as well as the code, and you're building in Web3, fintech, or anywhere data density matters, I'd like to hear about it.