Skip to main content

Available — Contract or Full-time

Tbilisi · GMT+4 · Timezone flexible

Senior
React Engineer
for Hire.

Senior Frontend Engineer specializing in React, Next.js, and TypeScript. 8+ years on hooks, state, tests, and UIs that get complicated fast.

Skeptical? Let an AI grade my GitHub & resume — free, no sign-up.

Don't take my word for it

Hand an AI agent a recruiter-style prompt and let it grade my GitHub profile and resume against the role. Start with a free, no-sign-up agent — or copy the prompt and run it in any AI you trust.

Free · no sign-up

ChatGPT
No sign-up · browses the web RepoMind
Free · reads my repos — paste the prompt
View & copy the prompt 
You are an experienced technical recruiter and engineering hiring manager with 10+ years of experience evaluating software engineers through their GitHub activity.

First, use web browsing to read this candidate's live GitHub profile and resume, then analyze them for a SENIOR TypeScript / React / Frontend (full-stack-capable) Software Engineer role.

GitHub profile: https://github.com/asmyshlyaev177
Resume: https://asmyshlyaev177.dev/Aleksandr_Smyshliaev_Resume.md

Job requirements: Strong React/TypeScript/Next.js depth, contributions to production and open-source systems, clean and maintainable code, solid testing practices.

Provide a structured analysis with these sections:

1. Overall Signal Strength (score out of 10) — how strong is this profile as evidence of professional software engineering experience?
2. Contribution History Analysis — consistency and volume over time, any long gaps, quality of recent activity.
3. Repository Quality Assessment — evaluate the pinned and most relevant repositories: README quality, code structure, documentation, real-world usefulness, and any stars, forks, or external traction.
4. Tech Stack & Relevance — how well does their activity align with the required skills?
5. Red Flags — any concerning patterns (hobby-only projects, very low activity, tutorial-style repos, etc.).
6. Green Flags — positive indicators of real engineering experience.
7. Final Recommendation — would you move this candidate forward for an interview? What specific questions would you ask about their GitHub work? Overall verdict: Strong / Moderate / Weak based on GitHub and resume.

Cross-check resume claims against the GitHub evidence. Be objective, specific, and cite concrete examples from the profile where possible.

Needs a free account

Hit Copy above, open one of these, and paste the prompt after you sign in.

Claude
Sign-in required Grok
Sign-in required

I'd rather do a few things really well than spread thin — and the things I do best are component libraries and the tests that keep them from rotting.

I usually end up on B2B and data-heavy products. TypeScript, Next.js or Remix, and code your team can still read in two years.

Work with me View projects
Scroll

My approach

The boring parts of a codebase — state, shared components, tests — are what decide whether a product is still pleasant to work on six months in. That's where I spend my time.

Featured Projects — React, Next.js, TypeScript

A few things I've built where the state, components, or tests had to hold up over time.

state-in-url

Shipped on npm · running in production teams I'll never meet

Stores nested, typed state directly in the URL via React hooks. I built it because I needed a fast, convenient way to preserve state on page reload and share page links.

Read the case study

Challenge

Sharing a page with its UI state (filters, multi-step forms, expanded panels) usually means stashing it in localStorage or losing it on refresh. URL params work — but typing them by hand gets ugly fast, and you lose types the moment you parse a string.

My role

Sole author and maintainer. Designed the React hooks API, wrote the TypeScript core, built the docs site, and handle every issue and release.

Result

In production at teams I'll never meet. Stable across Next.js, Remix, and react-router; survived multiple React majors without a breaking change.

React TypeScript Tailwind Next.js Remix.js react-router npm
Live Demo
Code
410
react-horizontal-scrolling-menu

74k/wk npm installs · maintained through multiple React majors

A reusable horizontal scroll component. TypeScript, well tested, and used in production dashboards I never get to see. Maintained for years across multiple React majors and refactored along the way.

Read the case study

Challenge

Most horizontal-scroll components in React either force a styling system on you or fall apart on resize. The opportunity was a small primitive — you pass it items and arrows, it handles the scroll math.

My role

Inherited the library, rewrote the core in TypeScript, added tests + Storybook, and kept the public API stable through React 17, 18, and 19.

Result

Powers dashboards I'll never see; bug reports come from teams I've never heard of.

React.js CI/CD storybook npm
Live Demo
Code
789
Screenshot of channels.careers
channels.careers

Production B2B platform · Playwright suite the team relies on

A B2B hiring platform startup. Built the UI to match the design closely, refactored code, adapted it to mobile, and wrote Playwright tests the team actually relies on.

Read the case study

Challenge

Early-stage B2B startup: the team needed someone who could ship Figma 1:1, untangle messy component state from earlier sprints, and leave behind tests the rest of the team would actually keep running.

My role

Front-end engineer. Implemented the UI close to the design, refactored shared state, adapted everything to mobile, and built the Playwright suite from scratch.

Result

Production hiring platform for B2B customers. The Playwright suite is now the team's release gate.

React.js Next.js TypeScript Playwright B2B
Live Demo
Website
Code
test-proxy-recorder

Deterministic e2e on CI with the backend turned off

VCR for Playwright — records real API responses once, then replays them deterministically on CI. Covers Next.js SSR, browser, and WebSocket traffic with no backend and no hand-written mocks. I built it because every flaky e2e run traces back to the network.

Read the case study

Challenge

Every flaky e2e run has the same root cause: the network. Existing tools each leave a gap — record real traffic, or cover SSR, or handle WebSockets, but never all three without hand-writing the mocks.

My role

Sole author and maintainer. Designed the record/replay proxy, the SSR + browser + WebSocket capture, the CLI, the docs site, and every release.

Result

Records real traffic across SSR, browser, and WebSockets, then replays it byte-for-byte on CI — so tests pass with the backend off.

TypeScript Playwright Next.js WebSocket e2e npm
Live Demo
Code
75

What I'm good at

Turning gnarly business logic into a React UI you can actually test.

  • React (8+ years)

    Hooks, patterns, custom renderers, concurrent features

  • State Management

    Redux, context, URL-persisted state, and the usual libraries

  • System Design & Architecture

    Reusable component libraries and codebases that don't collapse under their own weight

  • Testing

    Unit, integration, and E2E (Jest, Vitest, Playwright, Cypress). The kind that catches real bugs, not the kind that pads coverage

  • CI/CD & Quality

    Pipelines that catch problems before they hit production

Proficient

Tailwind CSS, GraphQL, Git, Remix.js, Node.js.

Familiar

Figma, Docker, PostgreSQL.

How I Can Help

Mainly looking for long-term roles where I can own the frontend and grow with the product. Open to contract and consulting work too.

React Engineering

I do my best work when I'm part of the team, not just clearing a ticket queue. That means caring about how the code holds up six months later, not only what gets merged this sprint.

8+ years of React. Strong on component systems and the architecture that keeps a codebase coherent as the team and product grow.

  • React, Next.js, Remix.js
  • TypeScript & component architecture
  • Performance & Core Web Vitals
  • Unit, integration & E2E testing
  • CI/CD pipelines

Hiring Support

I help teams hire frontend engineers: resume screens and technical interviews.

  • Resume review
  • Technical interview participation

Technical Leadership

Code is the easy part. I also weigh in on architecture, run code reviews that aren't just nitpicks, and help newer devs get up to speed.

  • Architecture & tech stack decisions
  • Code reviews & quality standards
  • Mentoring & onboarding

Sound like a fit?

Tell me about the role or project — I usually reply within a day.

Let's talk

About Me — Senior Frontend Engineer (React / Next.js)

Senior Frontend Engineer (React, Next.js, TypeScript). From sysadmin to senior frontend developer — the longer story.

I started in tech as a system administrator, managing servers and networks. My direction changed when I wrote a script to parse a phone number database for a marketing campaign — that small thing showed me how satisfying it is to solve problems through code. I moved into web development, started with Vue.js and D3.js, then settled on React for its scalability on complex projects. I haven't looked back.

Since then I've worked across startups and larger companies — in-office and remote, including US-based teams. I care about TypeScript, testing, and CI/CD not as checkboxes but because they make complex codebases actually manageable. I focus on doing things right, not just fast.

My Philosophy

Pragmatic Approach

Select the best tool for the task while staying open to improvements and adaptability.

Quality Focus

Prioritize quality and maintainability in complex software, keeping complexity to a minimum.

DevOps Mindset

Automate repetitive tasks — CI/CD, linting, packaging, and testing — so the team ships faster.

Continuous Learning

Technology evolves rapidly, and so do I. Always exploring new tools and frameworks to stay sharp.

Aleksandr Smyshliaev photo
Aleksandr Smyshliaev

Quick Info

Experience 8+ years
GitHub stars 1177+
Remote experience Yes
Startup experience Yes
IQ 115-125
Legal entity Yes
English CEFR C1

Education

Krasnogorsk State College

BTech · 2004–2008

Location

Tbilisi, Georgia (GMT+4)

Remote worldwide · timezone flexible

Recommendations

What teammates and managers I've worked with have written — unedited apart from light trimming where marked. Full text on LinkedIn.

I had the pleasure of working with Aleksandr on a complex NextJS codebase that he inherited and ramped up on very quickly. He was able to understand the existing architecture, identify areas for improvement, and start making meaningful contributions without a long onboarding curve. […] I would gladly recommend Aleksandr to any team looking for a capable frontend developer who can quickly become productive, improve existing systems, and contribute reliably across implementation, debugging, and test strategy.

Vladimir Shcherbakov

Co-Founder / CTO · ex-Google, ex-Splunk

May 2026

Alex was great to work with. He understood requirements very quickly, and worked well with the backend engineer to complete the work very quickly. Aside from coding, he also helped design and build an SDK that could be reused.

Issavara (Kim) Polanun

Co-Founder & CPO · Kick Off

Nov 2023

Working with Aleksandr was a great experience. He is not only detail oriented, but extremely talented and capable of collaboration. Although we were only able to work on two projects together, I would highly recommend him and hope to have the chance to work with him again.

Kami Slattery

Senior Product Manager · Allegion

Oct 2023

See all recommendations on LinkedIn

Get In Touch — Hire a Senior Frontend Engineer

Open to freelance, full-time, and consulting work. Best reached by email or LinkedIn.

***********
linkedin.com/in/asmyshlyaev177
github.com/asmyshlyaev177

Loading calendar…