Open to new roles

Iaroslav
Grishunin

Senior Frontend Engineer with 9+ years building products people enjoy using — from design systems and platform architecture to real-time 3D experiences.

See my work Request CV

Years experience

Brands shipped

Platforms led

Components built

What I bring

Architecture, leadership,
and craft.

I work at the intersection of engineering rigour and product thinking — comfortable owning a codebase end-to-end, leading a team, or sitting down with designers to get the details right.

⬡

Frontend Architecture

Designing scalable, maintainable systems — from hexagonal architecture and monorepo structures to platform-agnostic packages that work across brands and platforms.

◈

Design Systems

Building component libraries in close collaboration with designers — Figma tokens, Storybook, naming conventions, and live theming at scale.

△

Technical Leadership

Acting as tech lead across teams — owning roadmaps, driving architectural decisions, conducting interviews, and setting quality standards.

◎

Full Stack Delivery

Primarily frontend, but comfortable across the stack — REST and GraphQL API design, Python/Django backends, PostgreSQL and MongoDB.

⬡

3D & Interactive UI

Real-time 3D viewers with Three.js, React Three Fiber, and Cannon.js — material editors, shader controls, and physics in the browser.

◇

Mentorship & Culture

I invest in the people around me — through code review, pairing, documentation, and creating environments where everyone feels safe to grow.

Selected highlights

Projects that shaped
how I think.

A handful of moments where the work was technically interesting, the stakes were real, and the outcome mattered.

Architecture

New Casino Platform — Hero Gaming

Designed a new frontend architecture for a platform serving 18 brands. Introduced hexagonal architecture, built platform-agnostic packages (core, app, i18n) and led a team of 7 through full implementation.

Design System

Cross-Brand Design System

Led the design system from zero — Figma variables, naming conventions, and Storybook components that scaled across multiple casino brands with live theming support.

3D & Real-Time

3D Collaboration Viewer — Xuver

Built a browser-based 3D viewer with a drag-and-drop material editor — real-time control over textures, shaders, and environmental properties. Introduced TypeScript and CI at the startup.

Team Lead

Crypto Casino — Hero Gaming

Led a team of three building a new cryptocurrency casino from scratch — owning technical decisions, a full product redesign, and a performance optimisation initiative end-to-end.

Personal projects

Built for myself,
open to everyone.

Side projects I build to scratch my own itches — real tools I actually use, shipped with the same care I'd give production code.

Tool

MixRef — Mixing Cheatsheet

My memory is terrible and I'm bad at mixing, so I built a reference tool I can actually open mid-session. EQ frequency guides and compression settings for drums, guitar, bass, vocals (including screams, growls, fry screams) and mastering — with genre filters for metal, jazz and rock, and a searchable glossary of 50+ terms explained in plain language.

Live site GitHub Vanilla JS · SCSS · Cloudflare Workers

🛠️

More in the works

Building in public — follow on GitHub to see what's next.

@oslavdev

How I work

From brief to
production.

How I approach a new project — from first principles to shipped product.

Understand the problem

Before writing a line of code, I want to understand the business context, the user, and the constraints. I ask a lot of questions early so I'm not solving the wrong thing well.

Propose an architecture

I draft an architecture proposal — covering structure, data flow, package boundaries, and tradeoffs. I share it early, invite disagreement, and iterate before any implementation begins.

Set standards early

Linting, type checking, testing conventions, CI pipelines — I set these up at the start, not as an afterthought. It makes everything that follows faster and less painful.

Build in the open

Regular check-ins, visible progress, documented decisions. I keep the team aligned and make sure no one is surprised by a direction change two weeks in.

Ship and improve

Delivery isn't the end. I monitor, collect feedback, and treat the first release as the baseline. Good products are iterated, not just launched.

Design system

Components built
to scale.

A live preview of a component system — switch the theme to see tokens in action.

Buttons

Badges Default Success Warning

Input

Cards

18 brandscross-brand tokens

1 systemsingle source of truth

live themingruntime token swap

Tech stack

Tools I reach for.

Nine years of picking up what the job needs. These are the ones I know best.

TypeScript React Next.js React Router 7 Remix Three.js React Three Fiber Node.js Express Apollo Server GraphQL WebSocket Redux Toolkit Tailwind CSS Styled Components SCSS Storybook Figma GSAP Vitest Jest React Testing Library Cypress E2E Testing ESLint Biome TSDoc Postman Beekeeper Studio GitHub Actions CircleCI Docker Cloudflare New Relic Sentry PostgreSQL MongoDB Prisma Zod Python Django

How I work

Engineering is a
team sport.

Transparency first

I make decisions in the open, document reasoning, and share context early — so teams can move fast without stepping on each other.

Inclusive by default

The best ideas come from people who feel safe to speak up. I actively create space for that — in reviews, in planning, in every day work.

Long-term thinking

I'd rather slow down slightly to build something right than ship fast and spend the next year paying it back. Maintainability is a feature.

IaroslavGrishunin

Architecture, leadership,and craft.