Berachain

(2024–present)

Financial apps and data infrastructure for a blockchain

Berachain — product engineering from interface to infrastructure
Berachain product engineering, from interfaces to infrastructure.

Overview

Trading, rewards, stablecoin and lending products, supported by shared data infrastructure.

Berachain is a blockchain with apps for swapping tokens, earning rewards, minting its stablecoin and lending. I joined before mainnet and helped complete features needed to launch its core products.

As Lead Full Stack Software Engineer, I built the BEX exchange experience, worked on Earn, Validators, Honey and Bend, and led Beep, the data service behind product interfaces. I also ship updates and manage releases, working with the smart contract team to translate protocol changes into interfaces and APIs.

  • BeraHub

    Swap tokens, earn rewards and explore validators.

  • Honey / Bera USD

    Mint and redeem Berachain’s stablecoin.

  • Bend

    Lend and borrow through Berachain’s lending app.

  • Beep

    Turn blockchain events into data for product apps.

01 / BeraHub

Making token swaps and rewards usable

I built the exchange experience for BEX in BeraHub, where users swap tokens and inspect pool data. My work covered the swap interface and supporting GraphQL queries. It had to account for slippage, failed transactions and the freshness of live data so users could understand an action before and after submitting it.

I worked on presenting multiple quote and minting paths as one coherent swap flow. The page combines MetaAggregator quotes from Enso, KyberSwap and Haiku with native minting routes, including ERC-4626 vaults. BEX itself is built on a Balancer V2 fork.

I also worked on Earn and Validators, the interfaces for Berachain’s Proof of Liquidity rewards system. Earn lets users stake eligible tokens and track rewards; Validators shows how validators direct incentives to eligible vaults. Building the Validators page meant bringing together protocol contract state and data from the network’s CometBFT consensus layer.

BEX swap and Earn interfaces on BeraHub
BEX swap and Earn interfaces, composed from BeraHub screens.
02 / Beep

Rebuilding the data layer

I led the design and development of Beep, the service that turns blockchain events into data the product apps can query. Its indexer and API replaced the previous subgraph-based backend. During the migration, full-history reindexing fell from roughly 12 days to 7 hours, so fixes and protocol updates could reach the products sooner.

I owned the indexing approach, schema-first API and OpenAPI documentation, deployment topology, Helm charts, performance and Prometheus monitoring—from design through production.

BERACHAIN / DATA INFRASTRUCTURE

Beep

Berachain

FULL-HISTORY REINDEXING / PREVIOUS BACKEND → BEEP

~12 days
~7 hours

During the migration, a full reindex went from roughly 12 days to 7 hours, shortening the path from a data fix to a product release.

WHAT I BUILT

  • Event-native indexing

    Backfill and live data in one pipeline.

  • A schema-first API

    Documented, predictable data contracts.

  • Production delivery

    Caching, observability and deployment designed together.

Indexer → API → production data
Beep replaced the previous product data backend with an event indexer and API.
03 / Honey & Bend

Building for the edge cases

Honey (now Bera USD) is Berachain’s stablecoin app. I worked on minting and redemption flows that respond to changes in collateral state. In basket mode, users can no longer choose a single asset for redemption, so the interface needs to make that change clear.

Bend is Berachain’s lending app, built on a fork of Morpho. I contributed to its product features, releases and maintenance, keeping the interface aligned with the behavior of the underlying contracts.

Honey / mint and redeem
Honey’s mint and redeem interface must also explain changes in collateral availability.
Bend / product interface
Bend brings lending positions and actions into one interface.
04 / Frontend foundations

Keeping a product suite consistent

I worked with the team on a design system shared across the frontend apps and documented in Storybook. We also separated transaction and protocol logic from UI components, making interface changes easier to review without mixing them with financial behavior.

Bera Design System components arranged in a bento grid
Shared navigation, swap, token selection and feedback components used across the product suite.
05 / Team tooling

Supporting releases and reviews

I introduced and maintained Sentry monitoring across the frontend applications so the team could investigate issues in production.

I built an internal coding agent with Vercel’s eve framework. Product teammates can request code changes from Slack, and the agent helps engineers review pull requests.

Responsibilities

  • Product engineering
  • Data infrastructure
  • Releases & observability

Stack

  • Next.js · React · TypeScript
  • Bun · Hono · PostgreSQL
  • Viem · GraphQL · OpenAPI
  • Helm · Prometheus · Sentry

Next project

The Look of Love

(2022)

An interactive experience to conquer a cat with a glance