Full-stack developer in Afghanistan

I’m Ziauddin Khaliqyar, a full-stack developer whose strongest focus is backend engineering. I work with Python, Django and FastAPI, build REST APIs and connect application logic to databases. I am familiar with React and responsive frontend technologies, and I make the limits and responsibilities of each layer explicit during project planning.

How full-stack work fits together

A full-stack project is not simply a list of technologies. It is a coordinated path from what a user sees to the rules, APIs and data that make a feature work.

Frontend and responsive use

Plan page structure, forms and user flows so that the interface communicates clearly across relevant screen sizes. React is a listed area of familiarity; the expected frontend implementation should be agreed against the actual design and scope.

Backend and application logic

Develop server-side behavior, authentication and workflows using Python frameworks already present in my portfolio. The project’s existing stack and requirements guide the implementation choices.

REST APIs and integration

Define endpoints around the information and actions that a user or connected service needs. Consider validation, authentication and system boundaries when extending an API.

Database structure

Connect application behavior to appropriate data relationships and queries. My listed database technologies include PostgreSQL, MySQL, SQL and Redis, with hands-on database design and optimization experience.

A backend-led full-stack skill set

My portfolio lists Python, Django, FastAPI, PHP, Java, RESTful APIs, PostgreSQL, MySQL, SQL, Redis, authentication, API integration and system architecture. It also notes familiarity with React and modern frontend technologies. Backend engineering is my stronger focus, so I describe frontend experience accurately rather than implying equal depth across every technology.

When defining work, I map the user task to interface, API and data responsibilities, then identify where an existing product or integration affects the scope. This is useful whether the project is a new application or a targeted extension to an existing one.

See the full skills list and work history.

Full-stack context from real projects

Amu Saraf: financial services

Django, Python, REST API, MySQL and Redis appear in the portfolio project details. The example connects backend functionality with data handling in a fintech platform.

Review Amu Saraf

KabulCargo: logistics application

The listed stack includes FastAPI, Python, PostgreSQL and Redis; the product context includes shipment tracking, route management and operational updates.

Review KabulCargo

EtihadAmu: product and backend work

My contribution included backend development and product work alongside business responsibilities. Django and web development appear in the project’s listed technologies and areas.

Review EtihadAmu

Questions about full-stack projects

Does full-stack mean frontend and backend are equal strengths?

No. The term describes work across connected application layers, but depth varies by developer. My strongest focus is backend engineering; my portfolio describes familiarity with React and responsive frontend technologies.

Can you take over an existing Python application?

We can discuss an existing application after reviewing its framework, data model, integrations and the requested changes. That review helps identify dependencies and decide whether the scope is backend-only or spans the interface as well.

Which Python frameworks do you use?

Python, Django and FastAPI are listed in my portfolio. Django is shown in Amu Saraf and EtihadAmu project contexts, while FastAPI is listed for KabulCargo. The existing stack and use case should guide framework decisions.