Front-end systems
React · TypeScript · components · responsive design · accessibility · performance
ENGINEERING PROFILE · ALIASKAR MALABAEV
I build web products end to end: front-end systems, domain logic, data, integrations and production delivery. 7 years of experience, several of them leading other developers technically.
AN END-TO-END PERSPECTIVE
Components, navigation and accessibility. A clear experience for the user.
Rules, permissions and validation. The right behaviour in every situation.
Models, consistency and processing. Information you can trust and use.
Testing, deployment and handover. A product ready to run and evolve.
01 — CAPABILITIES
Technology comes after the problem. My role is to choose a legible architecture, protect business rules and deliver an interface that stays simple for the user.
React · TypeScript · components · responsive design · accessibility · performance
PHP · Laravel · Node.js · APIs · permissions · validation · business rules
MySQL · Redis · job queues · data modelling · integrations
Testing · Docker · Git · CI/CD · observability · static or application deployment
Assisted generation · document extraction · PDF to structured data · workflows
Discovery · prototypes · functional breakdown · trade-offs · progressive delivery
02 — CAREER
I have not only written code: I have scoped projects with clients and reviewed other people's work. That is what shapes how I design today.
2023 → today
Planning and management applications: availability rules, permissions, validation, front-end and back-end architecture.
2020 → 2023
Product development, reviewing colleagues' code, technical coordination and mentoring developers.
2019 → 2020
Scoping, client relationships, team coordination and project delivery.
2019
Responsive integration, JavaScript, first professional web projects.
EDUCATIONM.Sc. Computer Science — Université Pierre et Marie Curie / Sorbonne, ParisBefore specialising in the web: Python, machine learning, networking and mobile development.
03 — COMPLEX PROBLEMS
Combining fast interactions, operational constraints, user permissions and validation without exposing that complexity on screen.
Turning files into useful data, orchestrating long-running jobs and making their progress understandable.
Building coherent, accessible and fast component systems that remain easy to evolve.
04 — HOW I WORK
Good abstractions begin with a precise understanding of users and their constraints.
Architecture, debt and trade-offs are explained clearly so decisions remain controlled.
Short, testable and demonstrable steps reduce risk and make learning faster.
Code should help the next evolution, not just pass today’s demo.
A TECHNICAL OR PRODUCT NEED?
I can contribute to a redesign, a business product, an integration or a longer full-stack engagement.