Available for new workI build the Software behind the website. and fix it when things get complicated.
Full-stack developer working across frontend, backend, APIs, databases and deployment. I mostly work on eCommerce, SaaS and existing systems that need to be fixed, extended or properly understood.
Currently — FULL-STACK DEVELOPER · FREELANCER
- Years Building
- 6+
- Client Projects
- 20+
- YEARS CLIENT WORK
- 3+
- ACTIVE PROJECTS
- 6
Selected work
Systems I've actually built
eCommerce platforms, SaaS products and custom software from the interface people see to the backend they never do.
About
I build full-stack products from the database and APIs to the web interface, admin systems and deployment.
I'm a full-stack developer based in Mumbai. Most of my work has been around software that has to actually run a business eCommerce platforms, HR SaaS, restaurant ordering and POS systems, matrimonial platforms, admin panels and the APIs behind them.
I usually work across the whole stack rather than stopping at the frontend or backend boundary. That means designing database structures, building APIs and business logic, connecting them to web or mobile clients, handling authentication and permissions, and getting the application deployed and running properly. I've worked with Laravel and PHP, Django and Python, and more recently Next.js, Node.js, MySQL, Drizzle and Redis.
What I enjoy most is taking an existing system or a messy requirement and turning it into something that is easier to use, easier to manage and easier to keep developing. Sometimes that means rebuilding a limited application instead of patching it. Sometimes it means working inside an existing codebase and adding features without breaking the things that already work.
How I work
- 01
Understand the system first
Before changing code, I want to understand how the application actually works the data model, APIs, business rules, dependencies and the parts people already rely on. A clean-looking change that breaks an existing workflow isn't really a clean change.
- 02
Business logic belongs somewhere intentional
Controllers, API routes and UI components shouldn't become dumping grounds for every rule the product has. I prefer clear boundaries between the request layer, business logic and data access, while staying pragmatic when an existing system doesn't justify a complete rewrite.
- 03
Build for the people operating it
A product isn't finished when the customer-facing screen works. Admin workflows, permissions, inventory, reports, content management, integrations and the small operational details are often what determine whether a business can actually use the software.
- 04
Don't add complexity just to sound senior
I don't believe every project needs microservices, five abstraction layers and a Kubernetes cluster. The architecture should fit the product, the team and the budget. Sometimes the right answer is a simple monolith that is well understood and easy to deploy.
What I do
I build the product, not just one layer of it.
From customer-facing interfaces to APIs, databases and the admin systems behind them, I work across the parts that make a product actually usable.
01
Web applications
Customer-facing products, dashboards and admin interfaces built around real business workflows not just pages that look good in a screenshot.
- Next.js and React applications
- eCommerce storefronts and customer flows
- Admin dashboards and data-heavy interfaces
- Responsive UI, SEO and performance
02
Backend & APIs
The part behind the interface: database design, business logic, authentication, permissions, integrations and APIs that connect the whole product together.
- Laravel, PHP, Django and Node.js
- REST APIs and third-party integrations
- MySQL and PostgreSQL database design
- Authentication, roles and permissions
03
Business systems
I build the operational side of products too the admin tools, workflows and integrations businesses need to actually run the software after it goes live.
- eCommerce, CMS and inventory systems
- SaaS and multi-company workflows
- POS, orders, payments and reporting
- Deployment, maintenance and existing codebases
Toolkit
What I reach for
Chosen for what they let me ship and maintain, not for what's new this quarter.
Languages
- TypeScript
- JavaScript
- Python
- PHP
- SQL
Frontend
- React
- Next.js
- Tailwind CSS
- TanStack Query
- Framer Motion
Backend
- Node.js
- Laravel
- Django
- Django REST Framework
- REST APIs
- Drizzle ORM
Databases
- MySQL
- PostgreSQL
- Redis
Mobile
- Flutter
- React Native
Infrastructure & Tools
- Git
- Docker
- Cloudflare
- Railway
- Vercel
- Hostinger
Experience
Where I've worked
Client work, product teams and independent development building across frontend, backend, mobile, databases and deployment.
Work
Sep 2024 — Present
CurrentFull-Stack Engineer
Upwork
Working directly with clients on production web applications, eCommerce platforms, APIs, admin systems, integrations, debugging and deployment.
Aug 2023 — Present
CurrentFull-Stack Engineer
Shahstore
Long-term eCommerce development across storefronts, backend, APIs, databases, admin systems, integrations, debugging and deployment.
Oct 2024 — Dec 2025
Full-Stack Engineer
Mehram Match
Worked across Flutter, Django, React and PostgreSQL, building APIs, authentication, matching, admin functionality, notifications and deployments within a seven-person startup team.
Apr 2025 — Jun 2025
Python Tutor & Mentor
MGM's College of CS and IT
Taught Python programming, debugging and practical problem-solving with a focus on understanding how the code works.
Sep 2022 — Nov 2022
Python Tutor & Mentor
Bloomzen Infosolutions Pvt Ltd
Taught Python fundamentals through practical examples, debugging and problem-solving.
Jul 2022 — Aug 2022
Python Developer
Bloomzen Infosolutions Pvt Ltd
Built Python scripts for automation and data processing using Tkinter, Pandas, NumPy and Matplotlib.
Education
Oct 2024 — Aug 2026
Bachelor of Technology, Computer Science
Chhatrapati Shivaji Maharaj University, Panvel
Jun 2020 — Sep 2023
High School Diploma, Computer Engineering
Maharashtra State Board of Technical Education
References
What people I've worked with say
Abdullah is an exceptional developer whose dedication and attention to detail ensure our products look stunning and function flawlessly. His professionalism and commitment to high-quality work make him a valuable asset to any team.
Tobi C.
Data Analyst
Abdullah was diligent and proactive in his work with me on a project. Learning a new technology wasn't a problem for him, and he is a community driver.
Favourite Jome
Customer Success Engineer, Hashnode
Questions
Before you reach out
What kind of projects do you take on?
I mainly work on custom web applications, eCommerce platforms, SaaS products, admin systems and APIs. I can build a product from scratch or take responsibility for a specific part of an existing system.
Can you work on an existing application?
Yes. A lot of my work involves existing codebases. I first understand how the frontend, backend, database and integrations are connected, then make the required changes without unnecessarily rebuilding parts that already work.
Do you only work on the frontend?
No. I work across the stack frontend, backend, APIs, databases, authentication, admin systems and deployment. Depending on the project, that has included Next.js and React, Laravel and PHP, Django and Python, MySQL and PostgreSQL.
Can you build something from scratch?
Yes. I can take a product from the initial requirements through database design, backend and API development, frontend implementation, admin workflows and deployment. The exact approach depends on what the product actually needs.
How do you approach a project?
I prefer to understand the requirement and the existing system first, then break the work into smaller pieces. I usually work feature by feature so there is visible progress instead of disappearing for weeks and returning with a mysterious 'it's done'.
Can you take over a project built by another developer?
Yes. I've worked with existing applications where the first job was understanding the current architecture and tracing how the frontend, APIs, backend and database fit together. If the existing system can be improved, I prefer improving it over rewriting it just for the sake of rewriting.
What happens after the project is launched?
I can continue with maintenance, bug fixes, new features, integrations, deployment issues and ongoing development. For longer-running projects, I can stay involved as the application grows instead of treating launch as the end of the relationship.
Have something you need built?
Whether you're starting something new or need help with an existing application, tell me what you're trying to build and where things currently stand.