Baatr Utnasunov
Designer
Dart
JavaScript
TypeScript
Active 16 days ago
+7 (909) 3961095 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
A frontend-focused UI engineer at a junior level who produces design-driven prototypes and small React utilities. The strongest proven skill is implementing simple React state boundaries and project scaffolding (evidence: tirsistris/flux-prototype/lib/store.ts - BuyProvider / useBuy and Next.js + Tailwind project config). There is almost no evidence of production-grade engineering practices in public code - e.g., automated tests, measurable performance optimization, accessibility engineering, or non-trivial server-state flows are not present.
Technical skills
Dart
JavaScript
TypeScript• Junior
Frontend
React.js
PostCSS
autoprefixer
Next.js
Tailwind CSS
DevOps
Vercel
Design
Adobe Illustrator
Adobe Photoshop
Figma• 4y+
AI/ML
ChatGPT
Claude
Midjourney
Claude Code
Mobile
Flutter
Timeline
Co-founder, Product Designer
•
Executive
FitNow
•
Cofounder
Worked as co-founder and owned the end-to-end product and design cycle in a small team with a backend developer. Conducted research and competitive analysis to define product architecture and user scenarios. Designed key flows including onboarding, program selection, training, and progress tracking. Built a design system in code and created interactive prototypes using Flutter.
Figma
Next.js
TypeScript
Tailwind CSS
Flutter
Claude Code
Lead Product Designer
•
Lead
Elistory
•
Full-Time
Led product design for a travel offering covering iOS, Android, and web platforms. Took the product from early stage through delivery to development, including market research, competitive analysis, prototyping, and usability testing. Ran ongoing interviews with tourists and locals while also coordinating recruitment through a product manager. Built a large design system and supported handoff with design reviews during implementation.
Figma
Product Designer
•
Middle
Freelance
•
Freelance
Delivered multiple parallel mobile-first and B2B-focused product design engagements across different domains. Designed and specified web admin interfaces for call operations, including filtering, request states, audio playback, and a custom UI kit. Created user and admin flows for corporate mobile apps with people management, shipments, defect handling, and push notifications. Produced fintech wallet flows covering registration, token operations, wallets, and transaction history.
UX/UI Product Designer
•
Middle
Uprock
•
Full-Time
Performed end-to-end digital product design for B2B and mobile-first contexts, including interactive prototyping and design-system work. Conducted audience and competitor research, tested hypotheses, and prepared pixel-perfect specifications for developer implementation. Produced documentation and supported development through detailed guidance on UI architecture and behavior.
Figmasince 2022
Kalmyk State University
Bachelor's Degree •
Marketing
Intern Backend Developer
Confidence: Low Generalist
A practical, documentation-focused developer operating at a junior level with stronger emphasis on product design and agent orchestration concepts than on backend engineering. The strongest proven skill is designing an agent-driven product pipeline and explicit stage contracts, evidenced by the CLAUDE.md pipeline and the agents/ test-companion directives. There is little to no public evidence of core backend work - no DB migrations, transactional logic, production-grade APIs, auth token management, or observability code are present.
API Design
2/10
How well APIs are designed
Lightweight API/orchestration thinking is documented (agent contracts and orchestrator responsibilities) but there is no concrete API implementation, versioning, or idempotency logic in code.
Data Layer & Database
1/10
Working with databases
Almost no data-layer engineering is present - no migrations, no tuned SQL, and no transaction/isolation handling; only configuration for external MCP servers and event-tracking notes appear.
Scalability & Performance
1/10
Handling load and speed
Very little evidence of scalability work - a few deployment references and external service configs exist but no caching, queuing, connection tuning, or load-testing artifacts.
System Architecture
2/10
Overall system structure
There is a documented orchestration architecture (agent pipeline and explicit contracts between stages) which demonstrates conscious separation of concerns, but it remains conceptual and mostly documentation-driven rather than implemented as services with contracts and operational controls.
Security & Auth
1/10
Protecting data and access
Minimal security/auth evidence - a few high-level notes about integrations and constraints exist, but no concrete auth flows, token lifecycle management, input validation code, or secrets handling are implemented.
Reliability & Observability
1/10
Stability and monitoring
Some architectural notes mention catching failures and drift in the orchestrator, but there is no implementation of retries/backoff, structured logging, metrics, or graceful shutdown in code.
Expertise
Backend AI & LLM• Intern
Microservices & API Architecture• Intern
Industries
Software• Intern
Technologies
Vercel
Recommendations
- Work on small SaaS feature teams building user-facing flows and LLM/agent orchestration layers - implement the orchestrator as a service with clear API contracts.
- Contribute to integrations and deployment pipelines (Figma / MCP / Vercel) and add concrete backend pieces such as webhook handlers, request validation, and simple persistence.
- Focus on one backend topic to deepen: add a migration history, simple transactional flows, and unit/integration tests around data changes to demonstrate backend engineering rigor.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Intern Frontend Developer
Confidence: Medium UI Engineer
A frontend-focused UI engineer at a junior level who produces design-driven prototypes and small React utilities. The strongest proven skill is implementing simple React state boundaries and project scaffolding (evidence: tirsistris/flux-prototype/lib/store.ts - BuyProvider / useBuy and Next.js + Tailwind project config). There is almost no evidence of production-grade engineering practices in public code - e.g., automated tests, measurable performance optimization, accessibility engineering, or non-trivial server-state flows are not present.
UI Component Architecture
2/10
How interface parts are built
Minimal, component-level work is present (React context/provider + design directives) but there is no clear, original component library, systematic composition strategy, or evidence of a custom tokens/theme system implemented in code.
Responsive & Cross-browser
1/10
Works on all screens and browsers
Very light evidence of responsive/layout work (tooling present) but no concrete responsive implementation or cross-browser feature-detection code in human-authored sources.
Performance Optimization
1/10
Speed of the interface
No measured or documented performance work, only basic server/orchestration helpers; no bundle-analysis, code-splitting decisions, virtualization, or before/after metrics in human-authored code.
Accessibility & Semantics
1/10
Usable for everyone
No concrete accessibility implementation in human-authored code - only documentation/directives referencing heuristics; no a11y testing, aria-managed widgets, or CI axe configs found.
State Management & Data Flow
2/10
Managing data in the app
Small, focused state-management artifacts (React provider hooks / simple store) exist but there is no evidence of advanced server-state discipline (cancellation, optimistic updates, machines) in human-authored code.
UX & Visual Polish
1/10
Look and feel quality
UX and polish are central to the project narrative, but the human-authored code contains little of the visual/UX implementations (those live in AI-generated design exports); only minimal UX-supporting artifacts are present.
Verified artifacts
Expertise
React• Intern
Modern Web Frameworks• Intern
HTML & CSS• Intern
Technologies
JavaScript
TypeScript• Junior
Dart
Adobe Photoshop
Tailwind CSS
Next.js
Adobe Illustrator
Figma• 4y+
React.js
PostCSS
autoprefixer
Recommendations
- Use for design-driven UI prototypes and feature-level component work (implementing components, small providers/hooks) - focus on shipping visual polish.
- Implement and own UI wiring for MVPs built on Next.js + Tailwind (pages, simple context state, design tokens integration).
- Contribute to design-to-code pipelines and documentation (artifact / directive maintenance, token & props contracts).
- Pair with a senior engineer for production hardening tasks: a11y, security review, test coverage and API edge-state handling.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Intern Game Developer
Confidence: Low Generalist
This developer currently has little to no human-authored engineering artifacts available for evaluation and therefore profiles as early-career (Intern level). There are no proven technical strengths in human-authored game-dev code to cite as evidence. Public materials do not demonstrate authored gameplay systems, rendering/ shader work, netcode, or performance engineering in source files available for review.
Gameplay Systems & Mechanics
How game logic works
Not evidenced in public code
Graphics & Rendering
Drawing game visuals
Not evidenced in public code
Physics & Math
Game physics and math
Not evidenced in public code
Engine Proficiency
Skill with the game engine
Not evidenced in public code
Performance & Frame Budget
Keeping the game smooth
Not evidenced in public code
Content Pipeline & Tooling
Tools for game content
Not evidenced in public code
Recommendations
- Publish clear human-authored source files implementing a single, complete game subsystem (for example, a small gameplay state machine or a deterministic fixed-timestep simulation) with tests and README explaining intent.
- Add unit tests and a canonical test fixture (with assertions) for core logic so reviewers can verify correctness without relying on generated or third-party artifacts.
- Separate and label AI-assisted or template-generated files, and provide provenance notes plus at least one non-AI-authored implementation to demonstrate original engineering decisions.
- Include measurable performance or design evidence where relevant - e.g., a short profiler capture, before/after bench for an optimization, or notes on deterministic simulation with timestep handling.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: