Backend Engineering
Production services in Python and FastAPI. REST APIs designed around the domain, JWT/OAuth2 authentication with token caching, task queues for anything that shouldn't block a request.
Three years of shipping real systems, not demos. I own the full lifecycle: schema design, API architecture, containerised deploy, and the mobile client that consumes it.
Currently focused on Python and FastAPI services with PostgreSQL behind them, and Flutter on the client side. Clean, maintainable code — and a bias toward automating whatever repeats.
Production services in Python and FastAPI. REST APIs designed around the domain, JWT/OAuth2 authentication with token caching, task queues for anything that shouldn't block a request.
PostgreSQL and MySQL from schema design through query optimisation and migrations. Containerised with Docker and Docker Compose, deployed behind Nginx on Ubuntu with SSL.
Applications in Flutter and Dart, taken all the way to an Android release on Google Play. Firebase, local persistence, and clients wired directly to the APIs I build.
Telegram bots that replace manual business process, plus third-party and AI service integrations — payments, SMS gateways and assistants wired into production systems.
A consumer review platform built on FastAPI and PostgreSQL, with categories, ratings and threaded comments.
A constructor that spawns and supervises child Telegram bots, each with its own command set and storage.
A shoe store app built in Flutter — from sign-up through to paying for an order. Published on Google Play.
Ordering bot for construction toys: catalogue, cart and checkout.
AiogramOrder intake bot for the 1688 and TaoBao marketplaces.
AiogramBooking bot for shoe and furniture dry-cleaning services.
AiogramBooking bot for IELTS mock exams: slots, sign-up and reminders.
AiogramIELTS preparation bot — materials and practice gathered in one place.
AiogramPizza ordering bot with menu, cart and delivery flow.
TelebotClear stages, a fixed scope and a timeline you can plan around. You always know which step the project is on and what comes next.
Order intake, catalogues, payments and business automation.
Landing pages, company sites and web apps running on their own API.
Flutter applications, built and published to Google Play.
We talk the task through and turn it into a written spec: what goes into the work, what stays out, and what counts as finished.
Cost and deadlines broken down stage by stage. The figure we agree at the start is the figure at the end.
Screens and user flow, agreed before the first line of code is written — changes are cheap at this stage and expensive later.
Built in stages, with working progress shown along the way rather than one reveal at the very end.
Checked against real scenarios. Anything that turns out not to match the spec is fixed at no extra charge.
Deployed to your server, with all operational accesses handed over to you. Rights to the source code are agreed separately and written into the contract. I stay reachable after launch.
Work begins with a prepayment. It reserves your place in the schedule and lets me give the project proper attention instead of spreading myself across parallel work. The remainder is paid on acceptance.
With a contract or without — whichever suits you. A contract complicates nothing: it simply puts on paper what we have already agreed, so both sides have something to refer back to.