Four products. Four different constraints.

Select a project to see its context, my role, the key engineering decision, and the measured outcome.

  • Support · 1,000+ messages 70% faster rendering
  • Travel · build pipeline ≈10× faster builds
  • Travel · shopping cart ≈3× faster interactions
  • EdTech · delivery ≈5 months: empty repo → production
AI-assisted research workspace showing project files, Typst source, compiled document preview, and AI review
AI-assisted research workflow · interface screenshot · open image for full size

Morizo Digital · Feb 2026—Now · Current client engagement

Source, compiled output, and AI review in one research workflow.

01

A collaborative workspace where scientists author LaTeX or Typst, review compiled documents, and work with AI in one interface, with analytics and admin tooling behind it.

  1. 01
    Author source

    LaTeX or Typst in Monaco Editor.

  2. 02
    Compile and review

    PDF.js output with errors mapped to source.

  3. 03
    Research with AI

    Reasoning states, errors, tokens, and response actions.

Product context
Scientific authoring, compiled review, and AI assistance inside one collaborative workspace.
Constraint
Keep source, compile feedback, document preview, and assistant state understandable together.
My ownership
Frontend ownership across authoring, preview, AI chat, analytics, and admin tooling.
Key decision
Connect source, compiled feedback, PDF review, and AI actions in one product workflow.
Primary outcome
Scientists can edit source, review compiled output, and act on AI feedback without switching tools.
  • React 19
  • TypeScript
  • Vite
  • Zustand
  • Monaco
  • PDF.js
  • Yjs
  • Amplitude
Engineering notes
Authoring
Editor shortcuts, autocomplete, minimap controls, auxiliary TeX files, plain-text fallback, and reliable saves.
Compiled output
PDF preview for LaTeX and Typst with compile errors mapped back to source and graceful fallback states.
AI workflow
Per-message model selection, reasoning blocks, token labels, inline errors, and reusable response actions.
Product operations
Amplitude instrumentation, environment-aware runtime config, paginated admin data, and EN/RU localization.
Customer-support workspace with a ticket queue, conversation, and request details
Production interface · open image for full size

Smartway · Aug 2025—Jan 2026 · Second engagement

Real-time support that stays responsive beyond 1,000 messages.

02

An embeddable support widget and ticket-management workspace for third-party integrations and high-volume corporate travel operations.

70% faster rendering for conversations with more than 1,000 messages
Product context
Real-time customer communication, ticket routing, uploads, and operational request handling.
Constraint
Long threads had to stay smooth while public integrations and existing authentication continued to work.
My ownership
Widget architecture, public integration API, performance work, HMAC migration, uploads, and routing.
Key decision
Virtualize long threads and move authentication to HMAC without breaking existing integrations.
Measured outcome
70% faster chat rendering; threads with more than 1,000 messages scroll smoothly.
  • Preact
  • TypeScript
  • Vite
  • Redux Toolkit
  • WebSocket
  • SCSS Modules
  • OpenAPI
Engineering notes
Architecture
Embeddable widget with a public integration API, Feature-Sliced Design, and domain-driven modules.
Performance
List virtualization reduced render work in operational threads of more than 1,000 messages.
Integration safety
HMAC authentication was introduced with backward compatibility for existing consumers.
Operational scope
Validated drag-and-drop upload for 15+ formats plus ticket categorization and routing by travel team.
Smartway corporate travel dashboard with booking search, approvals, and trip overview
Production interface · open image for full size

Smartway · Mar 2021—Feb 2024 · Senior Frontend Engineer → Tech Lead

Modernizing a travel platform while product delivery continued.

03

Long-term ownership across TypeScript adoption, build tooling, runtime performance, analytics, internationalization, mobile, engineering standards, and mentoring.

Build pipeline ≈10× Faster team builds after Webpack → Vite
Shopping-cart performance ≈3× Faster measured interactions after state and render restructuring
Product context
Corporate travel across flights, rail, hotels, taxis, transfers, approvals, analytics, and mobile.
Constraint
A long-lived frontend foundation had to change without freezing active feature delivery.
My ownership
TypeScript adoption, build tooling, cart performance, analytics, i18n, mobile, standards, and mentoring.
Key decision
Modernize the frontend foundation incrementally alongside ongoing product delivery, not through a full rewrite.
Measured outcomes
Approximately 10× faster builds and approximately 3× faster shopping-cart interactions.
  • React
  • TypeScript
  • Vite
  • React Query
  • React Native
  • Storybook
  • Jenkins
  • i18n
Engineering notes
Migration
Introduced TypeScript and migrated the full project, including a custom UI library, within one year.
Delivery system
Moved builds from Webpack to Vite while feature work continued for the product team.
Runtime work
Restructured state and rendering in the shopping cart; built interactive analytics and full English i18n.
Leadership
Established quality standards, CI/CD, documentation, and technical talks; mentored three developers.
Read the full case study
Psychology course marketplace with navigation, featured event, and course cards
Production interface · open image for full size

Smart Online Institute · Feb—Aug 2025 · Production MVP

From an empty repository to a live learning product.

04

End-to-end frontend ownership for a psychology education product: marketplace, learning progress, booking, media delivery, instructor tooling, integrations, and deployment.

≈5 mo. from an empty repository to a production MVP for real learners
Product context
Course marketplace, learner profiles and progress, practice booking, media, and instructor analytics.
Constraint
A new product needed a maintainable frontend, integrations, delivery pipeline, and real-user launch.
My ownership
Sole frontend engineer across architecture, product features, BFF integration, CI/CD, Docker, and deployment.
Key decision
Use a Next.js BFF for API orchestration and automate legacy migration where no API existed.
Delivery outcome
From an empty repository to a production MVP in approximately five months.
  • Next.js
  • TypeScript
  • React Query
  • Zod
  • Strapi
  • Playwright
  • AWS S3
  • GitLab CI/CD
Engineering notes
Product build
Built marketplace, profiles, learning progress, practice booking, and instructor progress visualization.
Media and API
Secure video, audio, PDF, and document delivery from S3 plus a Next.js BFF for API orchestration.
Delivery
Set up GitLab CI/CD and Docker-based deployments from scratch.
Legacy migration
Automated data migration with Playwright scraping where the previous service exposed no API.
Read the full case study

Where the work happened.

Progression from end-to-end implementation to product ownership, migrations, architecture, and technical leadership.

  1. —Now

    Morizo Digital

    Senior Frontend Engineer · Client engagement

    AI-assisted research workspace: scientific authoring, compiled preview, AI review, analytics, and admin tooling.

    Current
  2. Smartway

    Senior Frontend Engineer · Second engagement

    Returned to build real-time support automation: embeddable widget, public integrations, ticket operations, and performance.

    6 months
  3. Smart Online Institute

    Sole Frontend Engineer

    Production EdTech MVP from an empty repository through architecture, integrations, CI/CD, and deployment.

    7 months
  4. Smartway

    Senior Frontend Engineer · Tech Lead

    Corporate travel platform modernization, product delivery, mobile, standards, mentoring, and technical leadership.

    3 years
  5. Germo-S

    Full Stack Engineer

    Solo B2B e-commerce platform with catalog, custom CMS, REST API, and production deployment.

    8 months
Education

Penza State University · Computer Science · 2016—2020

Useful when the frontend becomes the constraint.

I can join as a senior frontend engineer, take hands-on technical leadership, or own a focused delivery scope.

01

Performance rescue

Constraint
Production slowness, long threads, large datasets, or unstable interactions.
Ownership
Profile real behavior, isolate the bottleneck, implement and verify a measurable improvement.

Format Focused audit and implementation

02

Migration in motion

Constraint
TypeScript, state, build tooling, or boundaries must change while delivery continues.
Ownership
Plan and execute an incremental migration without unnecessarily freezing feature work.

Format Embedded with the existing team

03

MVP build-out

Constraint
A product must move from an empty repository or early prototype to real users.
Ownership
Frontend architecture, workflows, integrations, quality, and delivery.

Format Focused project or team scope

04

Embedded senior / tech lead

Constraint
An active team needs hands-on senior implementation and judgment inside the product.
Ownership
Architecture, delivery, code review, standards, mentoring, and technical coordination.

Format Full-time or long-term contract

The work behind the shipped screen.

Evidence from migrations, product delivery, team practices, and real production workloads.

01 / Migration

Change the foundation without losing product momentum.

Full TypeScript adoption, custom UI library migration, Webpack-to-Vite, and incremental architecture work.

  • Full project migrated within one year
  • Approximately 10× faster builds after Webpack-to-Vite
02 / Leadership

Raise the quality of the system and the team around it.

Hands-on standards, code review, documentation, CI/CD practices, technical talks, and mentoring.

  • Mentored three developers
  • Shared guidance through reviews and talks
03 / AI workflows

Apply AI to shipped product workflows and team practice.

Production product
Research chat with model, reasoning, token, error, and action states.
Team practice
Internal LLM guidelines, training, architecture review, and test-generation workflows.
04 / Performance

Treat performance as a product constraint, not final cleanup.

Profile the production workload, remove the work users feel, and measure the same workload again.

  • Virtualized support threads with 1,000+ messages
  • Restructured shopping-cart state and rendering

Senior frontend engineering across products, systems, and teams.

Six years across B2B SaaS, travel, support operations, EdTech, e-commerce, and AI-assisted research.

Danila Igoshin
Penza, Russia · UTC+3 · English (professional) · Russian (native)

I work on complex product states, long-lived codebases, performance, integrations, and workflows that need to remain understandable as they grow. In remote teams, I keep decisions written, progress visible, and ownership clear. I stay hands-on through implementation, code review, and mentoring, from a production problem to a measured result. That makes me useful as a senior frontend engineer, a hands-on technical lead, or the owner of a focused delivery scope.

Experience
Approximately 6 years
Product focus
Complex B2B product systems
Core stack
React · TypeScript · Next.js
Availability
Open to remote opportunities
Working format
Remote · full-time / contract · EMEA relocation
Languages
English — professional · Russian — native
Read the complete résumé

Looking for a senior frontend engineer for a role or project?

Tell me about the team, product, or engineering challenge. I usually reply within one business day.