Senior Software Engineer · 6+ years in production

I engineer the parts users feel and teams have to live with.

This is not a mirror of my LinkedIn. It is a small engineering notebook about speed, architecture, modernization and the decisions behind production software.

Zhassulan Serikuly
current modereduce complexity
loopprofile → simplify → prove
6+
years in production

From React internship work to senior ownership across international product teams.

1-3M
users served

Production interfaces operating at meaningful product scale.

200+
projects delivered

Across web, mobile and data-intensive platforms.

75+
projects optimized

Performance, architecture and maintainability improvements.

Engineering notebook

Four decisions worth discussing in an interview.

No job-description bullets here. Each case is structured around a constraint, an engineering move and a measurable outcome.

01

Architecture at product scale

Ciklum

Make ten modules feel like one system.

Constraint

A growing React/Next.js product surface had to stay coherent while 10+ modules evolved in parallel for a platform serving 1–3M users.

Engineering move

Built a shared React/Next.js component library and a type-safe REST/GraphQL API layer with NestJS — standardizing strict TypeScript, WCAG AA compliance and shared product workflows so new features could start from an established system instead of local conventions.

Outcome

The architecture reduced feature implementation time by roughly 30% while creating a stronger base for cross-module development.

ReactNext.jsNestJSTypeScriptREST APIsGraphQL
10+product modules
~30%faster feature delivery
02

Performance as architecture

Ciklum

Treat loading time as a graph, not a number.

Constraint

High-traffic screens were slowed by work happening across rendering, data fetching, caching and asynchronous UI flows rather than one obvious bottleneck.

Engineering move

Optimized the full request-to-render path: rendering behavior, caching, async orchestration and API request patterns, then backed the work with Core Web Vitals, Lighthouse, tests and Sentry monitoring.

Outcome

Average page load time moved from about 3.2 seconds to 2.1 seconds while the platform continued to evolve.

Core Web VitalsLighthouseVitestJestSentryCI/CD
3.2 → 2.1saverage page load
34%approx. reduction
03

Geospatial performance

KeyHorse

Half a million map objects should still feel interactive.

Constraint

Dense GIS interfaces had to render and manipulate datasets containing roughly 300K–500K geospatial objects without making the first interaction feel delayed.

Engineering move

Restructured layers and styles, introduced clustering and client-side filtering, and tightened the data path between the React state layer and Elasticsearch to eliminate repeated work.

Outcome

Initial Mapbox GL JS rendering dropped from about 800ms to 480ms, with a 30% improvement in geospatial search response time from separate algorithm work.

ReactMapbox GL JSReduxElasticsearchPerformance Profiling
800 → 480msinitial map render
300K–500Kgeospatial objects
04

Reusable delivery systems

KeyHorse

Build the next regional product by configuring, not copying.

Constraint

Dozens of regional GIS products shared recurring UI and data patterns, but repeated implementations made delivery slower and consistency expensive.

Engineering move

Created a centralized React architecture using Feature-Sliced Design, with 100+ reusable components documented in Storybook, then standardized TypeScript, theming, role-aware patterns, linting and test practices around it.

Outcome

Similar implementation work dropped by up to 50%; some launches that previously took about a month could be completed in roughly a week.

ReactTypeScriptFeature-Sliced DesignStorybookVitestPlaywright
100+reusable components
1 month → 1 weeksimilar implementations

Selected builds

A few products.
Not the whole archive.

These are here to give the engineering notebook a visual layer. They are not a second résumé and they are not meant to list every project I have shipped.

Stroymarket.kz

A nationwide B2B marketplace connecting construction material suppliers, contractors, and equipment rental across Kazakhstan — live catalog and supplier search across 39 cities, an AI-powered project assistant, and a cost-estimation calculator for common build types.

Solo-built, from supplier/catalog discovery to an AI construction assistant and cost estimator.

Vue.jsNuxt.js

Kostyum.kz

A responsive men’s and women’s fashion e-commerce frontend — reusable product-catalog UI covering apparel, footwear, and accessories, with a focus on a smooth desktop and mobile shopping experience.

Nuxt.jsVue.jsSSR

Midas Event

An event-agency site built as a browsable portfolio of past events rather than a static services list, with React-driven interactive detail throughout.

ReactJavaScriptCSS

UniStory

A digital product interface integrating crypto-wallet state and asynchronous backend data into reusable React product experiences.

ReactTypeScriptREST APIsWeb3

Systems I like working on

No client gallery.
Just the engineering terrain.

LinkedIn can list projects and employers. Here I would rather show the kinds of systems where my work becomes most valuable.

High-traffic product modules

Interfaces where architecture, caching, state and API behavior have to work as one product system.

Vue 3TypeScriptPiniaVite

Geospatial systems

Map-heavy products where data volume changes the frontend architecture, not just the rendering layer.

Mapbox GL JSElasticsearchGISData-intensive UI

Modernization programs

Legacy-to-modern migrations that keep product delivery moving while the technical foundation changes underneath.

Vue 2 → Vue 3Composition APITestingCI/CD

End-to-end product delivery

Frontend-first engineering with enough backend depth to own APIs, integration boundaries and production behavior.

Node.jsNestJSPostgreSQLREST APIs

Operating principles

The rules behind the code.

Tools change. These are the habits I expect to keep.

01

Measure before rewriting.

A performance change should begin with evidence and end with a user-visible outcome.

02

Architecture is a delivery tool.

The best abstraction is the one that makes the next feature cheaper, safer and easier to understand.

03

Frontend is part of the system.

Rendering, data shape, APIs, accessibility, observability and release pipelines are one engineering surface.

04

Senior means reducing uncertainty.

Technical leadership is making trade-offs visible so a team can move quickly without accumulating hidden risk.

Engineering path

A progression of scope,
not a chronology of job titles.

The chronology is deliberately compressed. The interesting part is how the work changed: UI → delivery → systems → technical ownership.

01Ciklum logo
Aug 2025 — Sep 2026

Senior Software Engineer

Frontend architecture · product modernization · performance · technical leadership · cross-platform

02KeyHorse logo
Jul 2021 — Aug 2025

Middle → Senior → Team Lead Software Engineer

GIS · digital twins · engineering leadership · reusable systems · backend APIs

03DAR logo
Jun 2020 — Jul 2021

Software Engineer

High-volume web delivery · e-commerce · mobile · performance

04EPAM Systems logo
Jan 2020 - Jun 2020

Software Engineer

React · TypeScript · reusable UI · engineering foundations

05Independent Contractor logo
2019 — 2025

Fullstack Software Engineer

Full-cycle SaaS & e-commerce delivery · multi-framework frontend · client management

Proof, not decoration

Things that can be checked.

Education, language evidence, competition recognition and a signed recommendation — kept separate from the engineering story.

View all certificates & recommendations
Education logoEducationInformation Systems

Suleyman Demirel University · 2018–2022 · GPA 3.72 / 4.0

EnglishIELTS 7.0

Academic IELTS · CEFR C1 result

Open proof
RecognitionSilver Medal

Infomatrix Asia-Pacific 2018 — International Computer Project Competition.

Open proof
ReferenceKeyHorse

Signed recommendation from company leadership

Open proof
Languages5 spoken

English — full working proficiency · Kazakh & Russian — native · Turkish — conversational · Chinese — basic

Next system

If the product is getting harder to change, I’m interested.

Senior Software Engineer · Senior Frontend Engineer · Team Lead
Open to international teams and relocation.

serikuly.zhassulan@gmail.com 
© 2026 Zhassulan SerikulyNuxt 3 · Vue 3 · TypeScript