Lead Front-End Engineer  ·  I build high-performance, scalable front-end systems & library-grade tooling

I lead front-end teams and ship the products behind them — 7+ years across fintech, crypto, healthcare & SaaS. I'm at my best where the front end gets genuinely hard: performance at scale, reusable systems, and real-time, data-heavy UIs. I lead full-stack delivery and build the internal tooling that other engineers build on.

const hoziefa = {
  role:        "Lead Front-End Engineer",
  focus:       ["scalable UI systems", "performance", "design-system tooling"],
  stack:       ["TypeScript", "React", "Next.js", "React Native", "Node", ".Net"],
  state:       ["Zustand", "Redux", "TanStack Query", "Context (Flux, tuned for scale)"],
  ai:          ["LLM / RAG features", "OpenAI", "Anthropic Claude"],
};

🌳  An unlimited-depth multi-tenant configuration tree — controls every level of settings across an arbitrary, unknown hierarchy, with depth-first traversal, in-UI search navigation, and caching; stays fast and stable at any depth.

🧩  A design-system-first UI library that handles advanced product needs — headless hooks, AI-ready MD/MDX docs, reusable across many products and cutting feature delivery time ~40–50% after onboarding. Publishing to NPM with a live gallery.

⚡  A Flux-style state layer on React Context, tuned for scale — selective subscriptions, memoization, and render control to push Context well past where it normally breaks down.

🕑  A worldwide timezone engine for a multi-tenant SaaS — the front end converts every value between the user/tenant timezone and a pure-UTC backend, on display and on submit.

📈  A real-time trading platform & its design system — a Turborepo/pnpm monorepo feeding multiple apps, with high-frequency, data-heavy UI built to stay smooth under exchange-grade load.

I lead front-end teams and partner across back-end, QA, and mobile. I set the standards, build the shared tooling, architect the solutions, and stay hands-on in the hard parts — real-time data, render performance, and the systems teams' reuse. I write tests as I go (TDD) and care more about what ships and holds up than about being right in a meeting.