Skills

Skills matter only when they help a team ship, operate, and improve a real system.

Areas of practice

01Backend & Systems

Systems that hold up beyond the happy path.

I build services, APIs, data flows, and integrations that need to stay reliable as requirements and dependencies change.

Backend engineering is my forte: dependable services, reliable integrations, and clear system boundaries.

Technologies

  • Java
  • Spring Boot
  • Node.js
  • FastAPI
  • REST/SOAP APIs
  • SQL
  • PostgreSQL
  • Redis
  • Elasticsearch
02Product interfaces

Turning complex systems into simple experiences.

I build responsive interfaces and frontend architecture that make complex products easier to use, from the overall structure to the details people interact with.

I connect interface decisions to the systems and data behind them.

Technologies

  • TypeScript
  • JavaScript
  • React
  • Next.js
  • Tailwind CSS
  • HTML
  • CSS
  • React Native
03Agentic Engineering

Agentic workflows with controls built in.

I connect language models to company data and external tools through workflows designed for controlled, reliable execution.

My work includes 18+ permission-aware MCP tools, tenant-scoped access, approval gates, audit trails, and cross-tool workflows.

Technologies

  • Agentic AI
  • LLMs
  • MCP
  • Tool Calling
  • RAG
  • PostgreSQL/pgvector
  • Redis
  • FastAPI
  • Celery
04Web3 & Protocols

Building across chains, wallets, and decentralized infrastructure.

My Web3 work has included smart contracts, cross-chain protocols, wallets, and decentralized infrastructure, from product interfaces to protocol integrations.

My Web3 projects have covered interfaces and decentralized systems across multiple protocols.

Technologies

  • Solidity
  • Ethers.js
  • Viem
  • Wagmi
  • Axelar
  • IPFS
  • WalletConnect

How I build

  1. 01

    Understand the problem

    Translate business goals into functional and non-functional requirements, separating must-haves from good-to-haves.

  2. 02

    Keep complexity intentional

    Clarify the problem and solve it with the simplest design that meets the requirements; avoid abstraction without a clear need.

  3. 03

    Ship, observe, improve

    Ship for production, learn from real usage, and iterate to keep systems reliable as they grow.