Ilyas Mardaliev

Backend • Middle • 19 years • Saratov, Russia • UTC+04:00 • Fully remote • Work permits: Russia • Available in 2 weeks • from $20k per year

AI Engineer

TypeScript

SQL

PHP

Active 17 days ago

Invite to interview

Download CVCV

Overview

Technical skills

Timeline

Roles

Overview

Backend Go developer (Middle-level) focused on building small REST APIs with clear package separation. The strongest proven skill is implementing end-to-end REST handlers and a simple data access layer, as shown by RestApi/internal/handlers/handlers.go, RestApi/internal/db/tasks.go and RestApi/api/main.go. Missing from public code are production-grade features such as tests and migration history, authentication and secrets management, structured observability, and graceful shutdown behavior.

Phone

Technical skills

Languages

TypeScript

SQL

PHP

AI/ML

LLM

GigaChat

OpenRouter

Databases

PostgreSQL

MySQL

MS SQL

Other

React Native

React.js

Rest API

SolidJS

Docker

Git

Expo

Cursor

Docker Compose

Nginx

RAG

Containers

Timeline

AI Architect • Lead

Travel Hub • Full-Time

Mar 2025 to Present 1 Year 7 Months Samara Partially remote

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

Middle Backend Developer Confidence: High API Engineer

API Design

3/10

How well APIs are designed

Basic, consistent REST API design with a standardized JSON error payload and simple query-filtering; lacks versioning, pagination, idempotency, or API contract/version strategy.

Evidence

RestApi/internal/handlers/handlers.go: respondWithJSON and respondWithError provide consistent JSON error responses; GetAllTasks implements 'completed' query filtering

RestApi/api/main.go: tasksHandler and taskIDHandler implement routing and method dispatch

Data Layer & Database

3/10

Working with databases

Reasonable data-layer separation and safe parameterized SQL using sqlx and RETURNING; no migration history, transactions, or explicit isolation-level handling shown.

Evidence

RestApi/internal/db/tasks.go: parameterized queries, RETURNING usage, sql.ErrNoRows handling in GetByID

RestApi/internal/db/database.go: Connect sets up sqlx DB and configures connection pool

Scalability & Performance

2/10

Handling load and speed

Some attention to DB connection pooling but no caching, no queueing, no client timeouts, and no measured performance tuning or load strategies.

Evidence

RestApi/internal/db/database.go: db.SetMaxOpenConns and db.SetMaxIdleConns

restapi-proxy/handler/handlers.go: proxy handlers use http.DefaultClient without timeouts

System Architecture

3/10

Overall system structure

Clear package boundaries (api, internal/handlers, internal/db, internal/models) and a separate proxy component show deliberate separation; overall architecture is simple and monolithic in scope.

Evidence

RestApi/api/main.go and folder layout: separation into api, internal/handlers, internal/db, internal/models

restapi-proxy/proxy/main.go and restapi-proxy/handler/handlers.go: separate proxy service layer

Security & Auth

2/10

Protecting data and access

Basic input validation and parameterized SQL reduce common injection risks, but there is no authentication/authorization, secrets handling, token lifecycle, or systematic error-sanitization strategy.

Evidence

RestApi/internal/handlers/handlers.go: CreateTask and UpdateTask perform JSON decoding and title validation

RestApi/internal/db/tasks.go: parameterized queries prevent SQL concatenation

Reliability & Observability

2/10

Stability and monitoring

Minimal observability and reliability features: basic request logging and DB connection error handling exist, but no timeouts, retries with backoff, graceful shutdown, structured logs, or metrics/alerts.

Evidence

RestApi/api/main.go: loggingMiddleware logs requests and database connection errors are returned on startup

RestApi/internal/db/database.go: Connect returns errors and configures connection pool but no graceful shutdown or timeouts

Expertise

Go Development• Middle

Microservices & API Architecture• Middle

Databases & Vector Storage• Middle

Technologies

PHP

Rest API

Recommendations

Build small-to-medium REST services and API proxies in Go where clear package separation matters (handlers, models, storage).
Add production readiness: database migrations, unit and integration tests, and graceful shutdown with request timeouts.
Harden services by adding authn/authz, input sanitization, and avoid returning raw error messages to clients.
Improve reliability and observability: set HTTP client timeouts, implement retries with backoff where appropriate, add structured logging and basic metrics.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

s1kata RestApi restapi-proxy

Junior Frontend Developer Confidence: Medium UI Engineer

Frontend-focused developer (Junior) who builds small, polished interactive UIs with clear end-to-end client behavior. The strongest proven skill is a production-ready document upload and analysis UI with drag-and-drop, form submission, loading/error handling and result rendering implemented in s1kata/ai-parser/index.html. There is no evidence of component architecture, automated tests, advanced state management (cancellation/race handling) or accessibility tooling in the public code.

UI Component Architecture

2/10

How interface parts are built

Single-file, hand-rolled UI with clear DOM manipulation functions but no component boundaries or reusable component library.

Evidence

s1kata/ai-parser/index.html: functions setStatus, renderResult, resetUI implementing UI logic inlined in the page

Responsive & Cross-browser

3/10

Works on all screens and browsers

Responsive CSS and viewport/meta present with a mobile media query and layout adjustments, but no RTL/i18n or advanced feature detection.

Evidence

s1kata/ai-parser/index.html: <meta name="viewport"> and @media (max-width: 600px) responsive rules s1kata/ai-parser/index.html: input accept attribute and flexible grid that adapts to single-column on small screens

Performance Optimization

1/10

Speed of the interface

No measurable performance work, bundle-splitting or virtualization; a straightforward static page without performance instrumentation.

Evidence

s1kata/ai-parser/index.html: single-page script using fetch without code-splitting or performance metrics

Accessibility & Semantics

2/10

Usable for everyone

Uses semantic controls (input, button) but lacks ARIA, focus management for the custom drop zone, and automated a11y checks.

Evidence

s1kata/ai-parser/index.html: file input is hidden and drop zone relies on click/drag handlers without ARIA roles or keyboard focus handling

State Management & Data Flow

3/10

Managing data in the app

Clear client-side request handling with explicit loading, success and error states and button disabling, but no request cancellation, optimistic updates or state machine.

Evidence

s1kata/ai-parser/index.html: uploadBtn click handler using FormData + fetch with try/catch/finally and setStatus calls s1kata/ai-parser/index.html: resetUI function and status state transitions (idle/loading/success/error)

UX & Visual Polish

4/10

Look and feel quality

Polished visual design for a small feature: animations, status dot with pulse, result card transitions and considered spacing and typography.

Evidence

s1kata/ai-parser/index.html: .status-dot.loading with pulse animation and .result-card.visible with fadeUp animation s1kata/ai-parser/index.html: extensive CSS for rounded card, badges, and responsive spacing

Expertise

Frontend AI Integration• Junior

HTML & CSS• Junior

PWA & Web APIs• Junior

Technologies

React.js

SolidJS

Recommendations

Implement the same UI as React/Vue components to demonstrate reusable component boundaries and props/composition patterns.
Add request cancellation and simple state machines (XState or similar) for the upload/analysis flow to show robust async discipline.
Introduce basic accessibility improvements: ARIA for the drop zone, keyboard focus handling, and run axe/eslint-plugin-jsx-a11y in CI.
Add unit/integration tests for the upload flow and a small performance checklist (Lighthouse or simple bundle analysis) for measurable improvements.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

s1kata portfolio ai-parser

Junior DevOps Engineer Confidence: Medium Generalist

Go backend developer at a middle level specializing in small end-to-end REST APIs and HTTP proxies. The strongest proven skill is clean separation of HTTP handlers and a SQL data access layer, demonstrated in internal/handlers/handlers.go and internal/db/tasks.go. Public code lacks CI/CD automation, formal observability, automated tests, and production deployment automation.

CI/CD Pipelines

Automated build and deploy

Not evidenced in public code

Infrastructure as Code

1/10

Managing servers with code

Minimal local IaC: a docker-compose file for local development is present but there is no remote state, versioned modules, environment separation, or Terraform/Pulumi automation.

Evidence

s1kata/RestApi/docker-compose.yml

Containerization & Orchestration

2/10

Working with containers

Basic container usage via docker-compose with a healthcheck; no multi-stage production build discipline in human-owned files, no Kubernetes manifests, probes, PDBs, or resource sizing for orchestrators.

Evidence

s1kata/RestApi/docker-compose.yml

Observability & Monitoring

1/10

Watching system health

Only minimal observability: simple request logging middleware exists but there are no metrics, dashboards-as-code, tracing, SLOs, or alerting config.

Evidence

s1kata/RestApi/api/main.go:loggingMiddleware

Reliability & Incident Response

2/10

Keeping systems up

Some reliability thinking is present (DB connection pool tuning and container healthcheck); however there are no formal runbooks, deploy strategies (canary/blue-green), graceful shutdown code, or incident artifacts.

Evidence

s1kata/RestApi/internal/db/database.go:Connect s1kata/RestApi/docker-compose.yml:postgres healthcheck

Cloud & Cost Optimization

Smart use of the cloud

Not evidenced in public code

Industries

Travel & Tourism• Junior

Technologies

Containers

Go• Middle

Docker Compose

Nginx

Recommendations

Add unit and integration tests for handlers and the DB layer (use go test with sql mocking or a disposable test DB) and run them in CI.
Introduce a simple CI workflow (GitHub Actions or similar) with build, test, and a gated deploy stage using reusable steps and caching.
Improve production readiness: add graceful shutdown handling, readiness and liveness endpoints, structured logs, and Prometheus metrics instrumentation.
Harden deployments: remove plaintext credentials from checked-in compose files and adopt secrets (environment or secret manager), and provide a multi-stage Dockerfile plus a deployment manifest (k8s or simple GitOps) for production.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

RestApi restapi-proxy microservice