I build things
that work.
Code is a means to an end. I've founded DeFi protocols, shipped full-stack features at scale, and everything in between - always starting from the problem, not the technology.
- Triaged and resolved production issues, conducted code reviews, and translated business goals into well-scoped specs and performant code.
- Contributed across web and mobile frontends (Astro, Next.js, React Native) within a Turborepo TypeScript monorepo.
- Worked across multiple backend services underpinned by PostgreSQL/PostGIS, Redis, Kafka, and Temporal.
- Launched NAB — a floor-adaptive stable token that reduces volatility while allowing for appreciation.
- Launched MINT — a single-sided liquidity protocol providing the counterparty side of token pairs on AO's AMMs.
- Owned product design, user interviews, and full build cycle iterating toward product/market fit.
- Managed cryptoeconomic mechanics including bonding, token utility, and ecosystem partnerships.
- Researched and implemented forward-looking technologies across web3 and AI into the product suite.
- Streamlined tech-ops to maintain build efficiency and quality; led project management across workstreams.
- Conducted user interviews and market research to drive the product toward market fit.
- Worked closely with founders and stakeholders to create a technology strategy supporting short and long-term goals.
- Led development and delivery of SDKs and developer tools for the Kin ecosystem.
- Drove economic development and ongoing maintenance of the ecosystem; hosted online developer conferences for community alignment.
- Developed API producers and consumers for loan application, evaluation, matching, and delivery services.
- Built serverless microservices on AWS Lambda with mobile-responsive frontends and self-scaling backends.
- Implemented frontend interfaces in React and Vue.js.
He's the rare engineer who ships above his level. He picks up unfamiliar parts of the codebase quickly, owns features end-to-end from data model to delivery, and consistently thinks about the boring-but-critical edges
I've worked with Will for several months, and he's the rare engineer who ships above his level. He picks up unfamiliar parts of the codebase quickly, owns features end-to-end from data model to delivery, and consistently thinks about the boring-but-critical edges — retries, races, idempotency, what happens when the failure mode is partial. The result is work that holds up in production rather than work that just compiles. Beyond the output, he's a genuinely good collaborator: humble, easy to give feedback to, and quick to fold corrections into the next iteration. He absorbs context from the team rather than working in isolation, which is why his velocity has compounded so visibly. Any team would be lucky to have him, and I'd hire him again without hesitation.
problem?
Let's talk.