Ilyas Mardaliev
AI Engineer
Python
SQL
JavaScript
Go
PHP
Node JS
TypeScript
Security & Auth: 5/10
API Design: 4/10
Scalability & Performance: 4/10
Active 22 days ago
+7 (967) 5042596 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
A backend-focused API engineer at a junior level with working experience integrating mobile clients, payment flows and CRM syncs. The strongest proven skill is building pragmatic API integrations (JWT auth endpoints, payment webhook handlers and CRM/booking submit flows) as seen in auth-mobile.php and the server/api handlers. What is not evidenced is deep system-design work - no migration chain/history, no load-testing artifacts, and only limited evidence of production-grade multi-service orchestration or formal operational runbooks.
Technical skills
Python
SQL
JavaScript
Go
PHP
Node JS
TypeScript• Junior
Python
FastAPI
Node JS
Express
Databases
MS SQL
MySQL
PostgreSQL
Firestore
Frontend
React.js
Frontend
DevOps
Docker
Git
Rest API
Design
Design
AI/ML
Cursor
RAG
GigaChat
LLM
OpenRouter
Mobile
Expo
React Native
Timeline
AI Architect
•
Lead
Travel Hub
•
Full-Time
Built products from scratch to production, including system architecture and API integration. Developed and shipped a full-stack travel platform with a mobile app, handling backend logic and production deployment. Also created AI-driven lead generation and B2B chatbots, automating incoming message processing and improving development speed using LLM-based assistance.
React Native
TypeScript
FastAPI
GigaChat
OpenRouter
LLM
Junior Backend Developer
Confidence: Medium API Engineer
A backend-focused API engineer at a junior level with working experience integrating mobile clients, payment flows and CRM syncs. The strongest proven skill is building pragmatic API integrations (JWT auth endpoints, payment webhook handlers and CRM/booking submit flows) as seen in auth-mobile.php and the server/api handlers. What is not evidenced is deep system-design work - no migration chain/history, no load-testing artifacts, and only limited evidence of production-grade multi-service orchestration or formal operational runbooks.
API Design
4/10
How well APIs are designed
API design is service-oriented with explicit auth endpoints (JWT, refresh/revoke), payment webhooks and separate server API handlers, but there is little evidence of formal versioning, API contract evolution, or advanced practices like standardized error envelope or idempotency keys across all endpoints.
Data Layer & Database
3/10
Working with databases
Multiple data integrations are present (Firestore sync code and server-side booking/CRM handlers), but there is no visible migration history, explicit transaction/isolation handling, or hand-tuned SQL/migration chains in the provided human-authored artifacts.
Scalability & Performance
4/10
Handling load and speed
There are practical scalability patterns - a RateLimiter, cache services and an outbound CRM queue - showing awareness of throttling and decoupling, but no evidence of measured performance tuning, load-test artifacts, or a system-wide caching invalidation strategy with metrics.
System Architecture
4/10
Overall system structure
Code is organized into clear module boundaries (server API handlers, client services, sync layers) and uses a small server component alongside the mobile client; the decomposition looks pragmatic but there is no evidence of formal service contracts, multi-service orchestration, or explicit config/secret management beyond environment usage.
Security & Auth
5/10
Protecting data and access
Authentication and session handling are explicitly implemented (JWT encode/refresh/revoke, password upgrade/validation, secure-session handling patterns), showing conscious security design at the API boundary; however there is limited evidence of a full token lifecycle management (revocation lists, refresh-rotation policies) or an automated dependency/security audit in the repo.
Reliability & Observability
4/10
Stability and monitoring
Observability and reliability primitives exist: structured logging utilities, Sentry init, dev logging and retry-aware handlers in server endpoints; but there is no visible alerts/metrics dashboards, incident postmortems, or full graceful-shutdown/circuit-breaker patterns for service processes in the human-authored files.
Expertise
Node.js• Intern
System Architecture• All Tiers
Go Development• All Tiers
Python• All Tiers
Industries
Travel & Tourism• Intern
Technologies
Go
PHP
Node JS
Firestore
Express
Recommendations
- Own backend endpoints and integration work - implement and harden payment webhook handling, idempotency and retry semantics for external services.
- Build and maintain server-side sync/queue consumers (CRM outbound queue) and caching with clear invalidation rules and metrics.
- Work on auth/session lifecycle improvements - add refresh token rotation, revocation lists, and automated tests for auth flows.
- Implement simple migration history and schema evolution practices for any SQL or persisted schema and add basic load-testing scripts for critical endpoints.
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 developer at a junior level who builds small, polished web UIs. The strongest proven skill is building an end-to-end browser file-upload and result-display UI as shown by the single-file upload/analysis interface (s1kata/ai-parser/index.html). The public code lacks evidence of component architecture, accessibility engineering, complex state management, testing, or production-grade networking safeguards.
UI Component Architecture
2/10
How interface parts are built
Single-file UI with inline CSS and DOM-manipulation script; no componentization, hooks, or modular component architecture.
Responsive & Cross-browser
3/10
Works on all screens and browsers
Basic responsive rules via a media query and fluid layout using flexbox/grid; no advanced cross-browser feature detection or RTL/i18n readiness beyond text content.
Performance Optimization
1/10
Speed of the interface
No measurable performance work, bundling or code-splitting; only small UI animations and minimal runtime optimizations.
Accessibility & Semantics
1/10
Usable for everyone
Minimal accessibility considerations - visual affordances exist but there are no ARIA attributes, keyboard/focus handling for the custom drop zone, or semantic landmarks.
State Management & Data Flow
1/10
Managing data in the app
Very small, local state management - file selection, fetch request and basic error handling; no request cancellation, optimistic updates, caching or state machines.
UX & Visual Polish
4/10
Look and feel quality
Good visual polish for a small demo - clear status bar states, meaningful feedback for loading/success/error, drag-and-drop and result rendering are implemented.
Expertise
Frontend AI Integration• Intern
Technologies
Frontend
Design
JavaScript
React.js
Recommendations
- Assign to small-to-medium web UI tasks: file-upload flows, result rendering cards, and iterative UX improvements where a single HTML/JS artifact is acceptable.
- Implement interactive front-end prototypes and landing pages that need visual polish, responsive behavior and clear user feedback (status bar, success/error states).
- Pair with a more senior engineer to refactor the single-file app into componentized code (React/Vue) and to add accessibility and request cancellation patterns.