About / Senior Frontend Engineer

I turn complex workflows into systems teams can safely evolve.

I’m a Senior Frontend Engineer with 6+ years building React, TypeScript, and Next.js applications. I take ownership from the first architecture decision through release, working with product, design, backend, and QA to turn complex requirements into useful experiences.

React · TypeScript · Next.jsFintech & SaaSPerformance & reliability
Engineer / educatorDmitrii Lobanov
Dmitrii Lobanov Building systems and explaining why

01 / Where I do my best work

Product pressure becomes an engineering shape.

My strongest work sits where user workflows, data ownership, performance, permissions, and long-lived delivery meet.

01

Complex workflows

Interfaces shaped by permissions, asynchronous state, operational rules, and large datasets.

02

Product architecture

Boundaries that clarify ownership and keep systems understandable and replaceable.

03

Engineering leverage

Performance work, migration strategy, shared foundations, and knowledge that teams can reuse.

02 / Working model

From ambiguity to a defensible decision.

Architecture starts with the guarantee a product needs—not with a preferred library or an impressive diagram.

01

Workflow

What must the user accomplish?

02

Constraint

What creates genuine pressure?

03

Ownership

Which system owns the responsibility?

04

Mechanism

What is the smallest sufficient design?

05

Evidence

How will we know it worked?

03 / Production evidence

Built through real operational pressure.

Six-plus years of React and TypeScript work shaped by users, migrations, delivery constraints, and systems that had to keep running while they changed.

Mar 2026 — presentIndependent products

Senior Frontend Engineer

After relocating to Ecuador, I focused on independent product development: Reliable Kanban for optimistic state, concurrency, and recovery, and Polaris for editor, runtime, repository, and AI workflows. These projects extend my frontend expertise with hands-on API and persistence work.

Explore the independent products
Jan 2024 — Feb 2026Tinkoff / T-Bank

Senior Frontend Developer

Owned frontend architecture and delivery for critical workflows on a fintech platform serving 300,000+ users. Improved production loading, interaction latency, and layout stability, and replaced a faulty onboarding integration causing data loss in approximately 10% of submissions.

See the production case study
Aug 2021 — Dec 2023Tinkoff / T-Bank

Frontend Developer

Built the frontend application from scratch and defined its architecture and state-management approach. Reduced unnecessary React renders by 35%, production build time from 20 to 6 minutes, and manual regression testing from 90 to 20 minutes per release. Promoted to Senior in January 2024.

2020 — 2021Earlier frontend work

Trading, enterprise, and real-time interfaces

At T-Soft, I built trading dashboards, forms, and messaging workflows with GraphQL and Apollo Client. At IBS, I delivered data-heavy B2B interfaces across enterprise projects. Earlier work at Promobot connected a React interface to voice and live-data APIs for robot interaction.

300,000+users

Product decisions made for meaningful operational scale.

−70%interaction latency

Production p75 INP improved from 500ms to 150ms across critical workflows.

−67%loading time

Production p75 LCP improved from 6s to 2s across critical pages.

04 / Engineering knowledge

The work becomes more valuable when the reasoning travels.

I turn production lessons into explanations other engineers can question, apply, and improve.

Speaking

Technical meetup speaker

At Tinkoff’s October 2025 meetup, I spoke about state management, bundlers, and the evolution of frontend engineering, drawing on lessons from large React and TypeScript applications.

Mentoring

Graduate project mentor

From November 2024 to May 2025, I guided students building a full-stack React parking-booking application, covering architecture, API integration, state management, reusable components, and debugging.

Operating principles
  • Product pressure should determine architecture.
  • Ownership should be visible in code and interfaces.
  • Performance work needs measurements.
  • Replaceability is a product capability.
  • Knowledge should survive the person who discovered it.

05 / Development practice

AI-assisted work, with engineering ownership.

I use Codex to accelerate focused implementation and review. I define acceptance criteria, inspect generated changes, and validate behavior through tests and build checks. Architecture and code quality remain my responsibility.

Based in Ecuador · UTC−5 · English C1 · Open to remote roles through international B2B contracts.

06 / Start a conversation

Building a product with difficult workflows or architectural pressure?