Technical foundation
PHP, JavaScript, TypeScript, and SQL at the core, with Magento, Laravel, and modern frontend stacks in daily use.
About
I work best where a project needs more than code. Storefronts, serious systems, security-minded builds, and search-aware sites all benefit from someone thinking across design, implementation, and daily use at the same time.
Who I am
I'm a developer focused on ecommerce storefronts, CMS platforms, ERP systems, and custom web applications. Magento and Shopify are the specialisation; WordPress, Laravel, Vue, and React are all part of the daily mix. I aim for builds that are technically sound, visually considered, search-conscious, and still maintainable years after launch.
PHP, JavaScript, TypeScript, and SQL at the core, with Magento, Laravel, and modern frontend stacks in daily use.
Clarity, usability, interaction quality, and visual hierarchy. Sites and systems should feel intentional rather than accidental.
Performance, search, security, and maintainability are part of the delivery promise, not extras added afterwards.
Depth
Self-assessed, and deliberately conservative. The top of this list is where I'd stake a deadline.
How I work
Every decision traces back to a business goal, a user need, or an operational reality. Cosmetic work without a purpose is not the point.
Patching, updates, access control, and production safety are core responsibilities rather than optional line items.
Fast loads, crawlability, and search structure are built in from day one, because retrofitting them costs more than doing them.
Questions
No. They are the strongest current specialisations, but I also work across CMS platforms, custom sites, ERP-style systems, internal tools, and broader frontend and backend stacks.
Yes. I work comfortably where brand presentation, UX decisions, frontend interaction, and implementation detail all have to stay aligned.
Yes. Technical SEO and platform safety are part of build quality here, not afterthought add-ons.
Storefront and theme delivery across Hyva, Luma, Breeze, and Liquid; custom extensions, app logic, and workflow rules; checkout and conversion path work; GraphQL and REST integrations, including payment and shipping providers; and the unglamorous side — patching, performance tuning, and debugging production incidents on stores that are already trading.
Yes. CI/CD pipelines in GitHub Actions, GitLab CI, or Jenkins; containerisation with Docker and orchestration on Kubernetes; infrastructure as code with Terraform, CloudFormation, or Pulumi; monitoring and log aggregation; and provisioning on AWS, GCP, or Azure. Delivery that cannot be repeated reliably is not finished delivery.
As a contributor rather than a parallel track. That means reading the codebase before proposing to replace it, matching existing conventions where they are sound, arguing for changes where they are not, and writing documentation and handover material as part of the work instead of at the end of it.
Ahmedabad, India, working in English with clients worldwide. Engagements run as freelance projects, contract builds, retained support, or collaboration inside an existing team.
Best next step