Maxim Fadeyev

Middle Backend Developer | Python | FastAPI | Async | PostgreSQL | Docker | Building scalable APIs

Salary / Daily rate

Stavropol, Stavropol Krai, Russia

Freelance, open to permanent contract

Can come onsite

Skills

PythonFastAPIPostgreSQLDockerCC++MicroservicesRedisLinuxNetwork Engineer

Languages

Russian (Native)English

About me

Intro

Python Backend Developer with hands-on experience building scalable REST APIs and asynchronous systems.I focus on performance optimization, reliability, and clean architecture. Improved API response time by ~25% and reduced production incidents by enhancing async logic and observability.Tech stack:Languages: Python, C, C++Backend: FastAPI, REST API design, asyncio, background jobs, microservices basicsDatabases: PostgreSQL (query optimization, indexing), Redis (caching, queues) Infrastructure: Docker, Docker Compose, Linux, basic networkingDevOps: CI/CD (GitHub Actions, GitLab CI), logging, monitoring Testing: Pytest, unit & integration testingArchitecture: SOLID, OOP, idempotency, fault tolerance, retry patternsCurrently looking for backend opportunities (remote or relocation in Europe / Asia).

Links

Work experience

Middle Backend Developer

Esscale Group

Nov 2024 - Dec 2025

1 year 2 months

Russia, Moscow Oblast, Russia

– Developed and maintained backend services for a Telegram bot using aiogram and asyncio – Designed and optimized database structure (PostgreSQL): schemas, indexes, and queries – Designed and maintained REST APIs (validation, error handling, endpoint structure) – Implemented asynchronous background tasks and job processing pipelines – Integrated external APIs with timeout handling, retry logic, and edge-case coverage – Wrote unit and integration tests (pytest) and maintained technical documentation – Set up logging and monitoring to improve system observability – Worked with Docker and Docker Compose for service containerization – Debugged production issues and improved system stability and reliability – Participated in code reviews and architectural discussions – Collected and analyzed service metrics and runtime statistics – Reduced incident response time from 15-20 min to 10-15 min through structured logging and improved debugging processes – Reduced production incidents by improving async logic and exception handling – Optimized PostgreSQL performance: reduced execution time of key queries from 250-300 ms to 180-250 ms via indexing and query optimization – Reduced average API response time from 300-350 ms to 220-280 ms by moving heavy operations to background jobs – Improved stability of external integrations using retry logic, timeout handling, and edge-case protection – Improved system observability and simplified production debugging

The best place to find your next move

© 2026. All Rights Reserved.