Sergei Nazarov
TypeScript
Node JS
State Management & Data Flow: 6/10
Performance Optimization: 5/10
Active 3 days ago
Invite to interview
Message
Download CVCV
Overview
Technical skills
Career analytics
Roles
Overview
Fullstack Senior (≈5.0) focused on resilient data pipelines and internal analytics tooling with strong evidence of deliberate ETL architecture and operational safeguards.
Technical skills
TypeScript• Senior
Node JS• Senior
Node JS
Axios
Frontend
React.js
Tailwind CSS
Vite
Next.js
Career analytics
Verified work history and code activity in one view - open-source impact, work rhythm, trust signals and a forecast of when this candidate is likely to move.
1
Years active
64
Commits analyzed
Work rhythm
UTC+0
12 AM6 AM12 PM6 PM12 AM
Code activity
Low
Peak
Last activity
Aug 2026 · 0 Days
Active days (90d)
23
Typical work hours
10 AM - 6 PM
Open source & impact
30
Stars earned
4
Forks
1
Merged pull requests
Collaboration Quality
Co-authored commits
10
Senior Frontend Developer
Confidence: Medium Fullstack
Fullstack Senior (≈5.0) focused on resilient data pipelines and internal analytics tooling with strong evidence of deliberate ETL architecture and operational safeguards.
UI Component Architecture
2/10
How interface parts are built
Minimal original UI component architecture visible; frontends exist but most human-authored artifacts in the sample are pipeline/backend. There is a tokenized CSS/design surface and dependency choices (Radix, Tailwind) but no clear in-repo custom component system or substantial custom primitives in the analyzed files.
Responsive & Cross-browser
3/10
Works on all screens and browsers
Responsive tooling and logical CSS tokens are present (Tailwind + CSS variables) but no advanced cross-browser feature-detection or internationalization scaffolding visible in human-authored files.
Performance Optimization
5/10
Speed of the interface
Clear, repeated performance work in the pipeline layer: WAL, transactional bulk writes, careful paging, throttling/backoff, and deterministic data generation for benchmarking; frontend build uses modern bundlers but no measured frontend budgets were submitted.
Evidence
anymasoft/meridian-pipeline/src/db.js: PRAGMA journal_mode = WAL, tx() wrapper and attention to bulk-insert performance
anymasoft/meridian-pipeline/src/pipeline/connectors.js: request() with retry/backoff, throttled counters and page-level atomic writes to avoid partial commits
anymasoft/meridian-pipeline/src/upstream/generate.js: deterministic data generator and injected failure scenarios used for realistic performance testing
Accessibility & Semantics
2/10
Usable for everyone
Some accessibility-minded patterns appear indirectly (focus/aria utilities in CSS and a few focus/keyboard helpers in bundled code), but no reproducible, explicit a11y audits, CI checks, or custom accessible widgets were found in the human-authored sources.
State Management & Data Flow
6/10
Managing data in the app
Strong server-state discipline and data flow practices are present: idempotent landing layer, watermarking per source×country, contract versions, deferred rejects, transactional staging and clear cache/expiry handling. This shows thoughtful server-state and pipeline design (request cancellation and retry handling at connector level, optimistic recoveries via contract_version).
Evidence
anymasoft/meridian-pipeline/src/db.js: schema design (landing / staging / mart), tx() wrapper and watermarks table (stateful, per-source×country)
anymasoft/meridian-pipeline/src/pipeline/connectors.js: request() with retry/backoff, setWatermark/getWatermark and land() atomic page writes
anymasoft/meridian-pipeline/src/pipeline/normalize.js: raw_rejects with contract_version and deferred kinds, requireFields(), and retry semantics for previously rejected rows
UX & Visual Polish
3/10
Look and feel quality
Good engineering discipline on error and edge-state handling in the pipeline (loading/warning/failure states are tested). Frontend UX polish evidence is limited to CSS tokens and skeletons; bespoke UX patterns (keyboard focus after actions, skeleton-driven optimistic updates) are not clearly present in the analyzed human-authored files.
Evidence
anymasoft/meridian-pipeline/public/assets/index-cJofRDCN.css: skeleton classes and transitions (perceived performance helpers)
anymasoft/meridian-pipeline/test/pipeline.test.js: many checks for loading/error/edge states in API and pipeline (empty source, 429 handling, deferred rows)
anymasoft/meridian-pipeline/src/pipeline/connectors.js: explicit handling of 429 and retry semantics (preserves data and surface states)
Expertise
React• Middle
Industries
Commerce• Senior
Technologies
TypeScript• Senior
Node JS• Senior
Tailwind CSS
Next.js
React.js
Vite
Axios
Recommendations
- Develop fault-tolerant ETL and analytics features (idempotent connectors, contract-driven normalization and quality gates).
- Build and maintain internal dashboards and operational UIs that surface pipeline checks, drift and provenance (use the existing API and schema).
- Implement integration work for commerce platforms and connectors (CommerceML, marketplace adapters) and supervised AI moderation flows.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Backend Developer
Confidence: Medium API Engineer
Backend engineer (middle) focused on Python services and data pipelines with reliable modular APIs and domain adapters. Proven strength: building well-tested, modular FastAPI services and async pipelines with concrete artifacts in bedrock-yield-scanner (app/pipeline.py, app/llm) and gridlab-terminal (app/engine, backtest/optimizer.py). Public code does not show explicit migration chains, production deployment manifests, or advanced resilience patterns like configured circuit-breakers and rate-limit policies.
API Design
5/10
How well APIs are designed
API surface is consistent and modular (FastAPI routers, typed request/response patterns), with WebSocket and background lifecycles used. Versioning and explicit idempotency keys are not visible in the public handlers, but there are clear router separations and typed contracts.
Evidence
bedrock-yield-scanner/app/api/routes_billing.py
bedrock-yield-scanner/app/api/routes_opps.py
gridlab-terminal/app/main.py
Data Layer & Database
5/10
Working with databases
Multiple durable storage patterns (SQLite metadata, DuckDB mentioned for archive storage) and explicit DB modules are present; code uses sqlite3 with attention to locking and upsert flows. No extensive migration history was visible in the analyzed files.
Evidence
bedrock-yield-scanner/app/db.py
anymasoft/1c-optimyzer (storage mention in sprint PR and README — DuckDB per-archive storage described)
Scalability & Performance
5/10
Handling load and speed
Concurrency and throughput considerations are present: async HTTP clients, background loops, ProcessPoolExecutor for CPU-bound optimizer runs, and streaming/archival patterns. No evidence of measured load tests, but clear decoupling and executor usage for scaling work.
Evidence
gridlab-terminal/app/backtest/optimizer.py (ProcessPoolExecutor usage)
bedrock-yield-scanner/app/pipeline.py (background_loop, async collectors)
gridlab-terminal/app/engine/realtime.py (asyncio streaming / live)
System Architecture
5/10
Overall system structure
Deliberate modular boundaries (collectors, pipeline, emulator, LLM provider abstraction) and a multi-component structure (FastAPI services, background workers, sidecars). Service decomposition is pragmatic rather than microservices-for-show.
Evidence
bedrock-yield-scanner/app/llm/base.py (LLMProvider abstraction)
bedrock-yield-scanner/app/pipeline.py (pipeline + collectors separation)
gridlab-terminal/app/engine (engine, replay, realtime modules)
Security & Auth
4/10
Protecting data and access
Security-aware code appears in payment integration (HMAC verification) and use of pydantic for settings; some attention to input validation. No full token lifecycle or auth-service implementation was present in the analyzed files.
Evidence
bedrock-yield-scanner/app/payments/nowpayments.py (HMAC / verify_ipn patterns)
bedrock-yield-scanner/app/config.py (pydantic Settings usage)
Reliability & Observability
5/10
Stability and monitoring
Operational patterns exist: FastAPI lifespan, background tasks, structured logging usage and a number of tests exercising invariants. Some resilience (background loop, graceful lifespan) but limited evidence of jittered retries, circuit breakers or deployment SRE configs.
Evidence
bedrock-yield-scanner/app/main.py (lifespan/asynccontextmanager usage)
bedrock-yield-scanner/app/pipeline.py (background_loop)
gridlab-terminal/tests (many unit tests for invariants and behavior)
Expertise
Backend AI & LLM• Middle
Microservices & API Architecture• Middle
Python• Middle
Databases & Vector Storage• Middle
Industries
Commerce• Middle
Data & Analytics• Middle
Financial Services• Middle
Recommendations
- Implement and own FastAPI microservices that expose well-documented, versioned REST/WS APIs and LLM integrations (use bedrock-yield-scanner app/api as a starting point).
- Build data ingestion pipelines and connectors with robust retry/backoff and schema evolution tests (extend pipeline/collectors + db.py patterns).
- Develop backend components that require async concurrency and CPU offload (optimizer workers, realtime streams) — the backtest/optimizer and realtime modules are a direct fit.
- Integrate payment and webhook flows with secure verification and durable persistence (nowpayments.py patterns).
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Game Developer
Confidence: Low Generalist
Frontend / full‑stack engineer (Junior) focused on building React-based data and admin tools with practical UI shipping experience. The strongest proven skill is frontend engineering and large interactive UI assembly as evidenced by the bundled frontend runtime and UI code at anymasoft/meridian-pipeline/public/assets/index-BG3EaLVO.js. There is little public evidence of game-specific systems, native performance engineering, or custom engine/shader work in the analysed human-authored files.
Gameplay Systems & Mechanics
1/10
How game logic works
Minimal gameplay or mechanics evidence; repository contains web UI bundles and admin tooling rather than authored game systems.
Graphics & Rendering
1/10
Drawing game visuals
No authored rendering or shader systems; only a bundled React frontend artifact is present (no custom GPU/shader code).
Physics & Math
1/10
Game physics and math
No evidence of custom physics, deterministic integrators, spatial partitioning or deterministic simulation in the human-authored files.
Engine Proficiency
1/10
Skill with the game engine
Surface-level engine usage (React/Vite) visible in build artifacts, but no human-authored engine internals, tools or native engine extensions in the analysed human files.
Performance & Frame Budget
2/10
Keeping the game smooth
Some signs of performance awareness in the bundled frontend runtime (scheduling, non-blocking work), but these are mostly framework/runtime pieces rather than authored, measured optimizations.
Content Pipeline & Tooling
1/10
Tools for game content
Content pipeline and tooling (build outputs) are present, but no original asset importers, CI pipeline code or custom tooling is exposed in the human-authored file set.
Industries
Commerce• Middle
Data & Analytics• Middle
Recommendations
- Develop web dashboards, admin tools and internal analytics UIs (React/Vite/Tailwind) where they can own UI state, command palettes and data views.
- Implement and extend ETL/connectors and backend endpoints for data ingestion and archive handling (small-to-medium services).
- Build integration work for domain-specific tooling (CommerceML importers, archive parsers) and front-end consoles for ops teams.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
AI Workflow