Omid Javaheri

AvailableTehran

Frontend Engineer

I build production web apps that stay fast and usable.

React, Next.js, and TypeScript — for trading platforms, product sites, and Web3. I care about performance, shared UI, and shipping with small teams.

View work Let's talk

Status: Available
Location: Tehran
Last role: Tara Chain
Focus: Web3 product UI
Experience: 3 years
Stack: React · Next.js · TypeScript

Introduction

Frontend for products people already use.

Most of my work sits in production: trading dashboards, restaurant operations, brand sites, and wallet-connected Web3 apps. The job is to make the next action obvious, and to keep the interface fast after the third feature lands.

I go full-stack with Next.js when the product needs it. What does not change is shared UI, careful rendering, and code a small team can keep shipping.

Selected work

Projects from production.

All projects

Live · ghajarifood.com

01 / Product

Ghajari Food

A suite of Next.js apps for restaurant management, accounting, online ordering, menus, and kitchen operations.

Responsibilities

Built the frontend for restaurant operations: ordering, menus, kitchen, accounting, and management — as a suite, not separate one-off apps.
Implemented NextAuth with role and permission-based access so staff, admin, and customer views shared one session model.
Connected real-time kitchen and order workflows to a .NET backend over SignalR.

Achievements

Scaled one application to about 10K daily users and 500 online orders per day.
Gave kitchen, admin, and customer flows the same UI system instead of three separate stacks.
Made access control and live updates part of the product, not an afterthought.

Role: Frontend Engineer
Team: Desna
Stack: Next.js · TypeScript · NextAuth · SignalR
Type: Product
Year: 2025

Case study Live

Gas Station

A Web3 gaming platform with wallet-connected swap, P2P trading, marketplace, and gamification.

Responsibilities

Built wallet-connected product UI with a three-person frontend team: swap, P2P trading, marketplace, multi-account, and in-game asset flows.
Integrated Solana wallet connection so transactions ran through the product, not a mocked connect button.
Implemented gamification — levels, rewards, missions, and achievements — on the same UI system as the economy features.

Achievements

Took the platform to the final pre-launch stage as one product, not a set of disconnected Web3 widgets.
Kept wallet state, marketplace, and rewards on shared frontend patterns so new surfaces did not mean new stacks.
Launch was later postponed by the client; the frontend was ready to ship.

Role: Frontend Engineer
Team: Tara Chain
Stack: Next.js · TypeScript · Solana Wallet · Sass
Type: Web3
Year: 2026

Case study

Live · polarisapp.ir

03 / Logistics

Polaris

A logistics route system with map visualization, multi-stop planning, and driver-facing views.

Responsibilities

Built the operations frontend for multi-stop route planning, live map tracking, and driver-facing views.
Wrapped Mapbox in product components so map logic did not leak into every screen.
Held planning and tracking state in Zustand instead of scattering it through the tree.

Achievements

Put planning and live tracking in one product instead of disconnected tools.
Made map and route state reusable across operations and driver views.
Reduced duplicated tracking logic that used to be copied per screen.

Role: Frontend Engineer
Team: Desna
Stack: Next.js · TypeScript · Tailwind CSS · Mapbox
Type: Logistics
Year: 2025

Case study Live

Capabilities

What I take on.

Frontend Engineering

Product UI in React and Next.js, with TypeScript as the default.

React
Next.js (App Router, SSR, SSG, ISR)
TypeScript
JavaScript
Tailwind CSS
shadcn/ui

Architecture

Shared systems that keep new surfaces from becoming new stacks.

Component systems / design systems
SSR / CSR / ISR
Code splitting
Rendering strategy
Performance (Lighthouse)
Storybook

State & Data

Client state, forms, and live data — without a new pattern per screen.

Zustand
React Hook Form
Zod
REST APIs
WebSocket
Server Actions

Product Engineering

Frontend as part of the product, not a coat of paint.

Design and product collaboration
Shared form architecture
i18n
Role-based access
Design systems
Feature delivery

Web3

Wallet-aware product UI, not isolated demo pages.

Wagmi
Viem
Wallet connection
Wallet switching
Solana wallet
On-chain product flows

Tools & Infrastructure

Enough of the surrounding stack to ship and operate.

Git
Docker
NextAuth
MongoDB
MinIO
VPS deploys

Experience

Recent roles.

Full timeline

Sep 2025 — Jul 2026
Frontend Engineer
Tara Chain · Tehran, Iran
Frontend for Web3 product surfaces: wallet connection, shared UI, gamification, and multi-language product experiences.
Jun 2024 — Sep 2025
Frontend Engineer
Desna · Tehran, Iran
Frontend engineering across brand and product sites, with a focus on performance, shared UI, and consistent form/state patterns.
Aug 2023 — Jun 2024
Frontend Engineer
OptionBaaz · Remote
Frontend on an Iranian stock-market platform — trader-facing views, admin tools, and real-time market data.

Approach

Things I keep coming back to.

Simple systems scale better

Shared UI and clear state patterns beat clever abstractions when a small team has to keep shipping.

Performance is a product feature

How a page renders is how it feels. Splitting, caching, and lazy loading belong in the first version, not the cleanup.

Reuse without over-engineering

Extract what actually repeats. Leave the rest. A design system should speed delivery, not freeze it.

Build for people, not just tickets

Traders, operators, and players do not care about the stack. They care if the next action is obvious and fast.

Contact

Let's build something useful.

Open to frontend roles and product work. Based in Tehran.

Get in touch omidjavaheri.eng@gmail.com