Loading introduction…
Loading practice metrics…
Loading about…
Loading selected work…
Loading longer projects…
Loading experience…
Loading skills…
Loading credentials…
Loading writing…
Loading working principles…
Loading availability…
Loading contact…
I'm Sakib, a software engineering team lead in Dhaka. I build Shopify and full-stack systems, connect the awkward bits, and help teams ship work they can maintain. The happy path is nice. I also read the error logs.
“I build commerce systemsthat make hard operationsboring. In the good way.”
I'm Sayed Ashraful Islam Sakib. That's a lot of name to say before a standup starts, so I shortened it for everyone's sake. Some people call me Ashraf; most call me Sakib, which saves everyone a few syllables. I answer to both, and reliably to "quick question?" I'm a self-taught software engineer and a team lead at Bevy Commerce, building Shopify applications, storefronts, and the integrations behind them. I'm based in Dhaka (GMT+6) and work North American hours (ET / CT) for a Toronto team, so your morning standup is also my standup. The origin story: I studied Physics, but a beginner C course, taken purely out of curiosity, turned out to be the first domino. I freelanced as a graphic designer next, on purpose: I wanted to understand how interfaces and visuals actually communicate before building them. Then came web development, front end first, then the server behind it, until I was working full stack. By late 2021 I was writing JavaScript for a living. Along the way I picked up testing, server configuration, and deployment, because code that only runs on my laptop is still a hobby. The design years never fully left, so yes, I will notice your button spacing.
I like tracing a requirement from the screen back to the data. Who owns the price? Which system knows the inventory? What happens when a customer signs in from a quotation link? Answering those early has saved more time than switching frameworks ever has.
I investigate the options, explain the tradeoffs, and build what the situation needs. Sometimes that's a custom application. Sometimes it's a setting in a tool the client already pays for. A new repository is not always the answer, even if naming it is the best part of the week.
I review code, help developers untangle unfamiliar requirements, and coordinate delivery. Right now that means two client teams of seven and eight people across theme, migration, integration, and QA. The goal is a team that understands a decision well enough to make the next one without pinging me first.
Launch day is a milestone, not a vanishing act. I care about useful errors, clear handovers, and a recovery path for when an integration develops opinions. Future me reads my notes and is grateful. So is whoever inherits the code.
I built a launched B2B portal connecting customer login, role-based access, quotations, account-specific prices, and inventory. It replaced quotations handled by phone and email, and it serves 100+ internal agents and admins and 1,000+ distributors. Supporting storefront work included native technical-document search.
Customers, agents, and administrators needed different records and actions, with a reliable path from storefront login to the correct portal page. Before the portal, quotations moved through phone calls and email threads.
I used Customer Account authentication with OIDC and PKCE, server-side role checks, and Shopify metafields for assignments. Commerce records stayed in Shopify; MongoDB held application records and Redis supported caching and background work.
Keeping commerce data in Shopify avoided duplicate records but required batching, caching, and careful handling of API limits.
I built a browser extension that checks device identifiers and accessory lots against order quantities before allowing label creation in the supported fulfillment workflow.
Warehouse staff needed to catch missing identifiers, duplicate device serials, and quantity mismatches without leaving their existing shipping interface.
The extension combines scanner input and native product verification with order-scoped state and shared serial claims. After explicit verification, it writes a Cloudflare record URL into ShipStation Custom Field 1.
Integrating with a third-party interface avoided replacing the warehouse workflow, but introduced DOM changes and network availability as ongoing maintenance concerns.
I lead an eight-person team (five engineers and three QA engineers) on a Magento-to-Shopify migration. I designed the sofa configurator's metaobject structure, guided product-data migration, and helped the integration team onboard its middleware and ERP connection.
The team needed a consistent product model for configurable furniture while replacing the storefront and preparing operational data flows.
I designed the configurator data structure and coordinated it with theme development and product migration. I supported integration onboarding rather than claiming ownership of every synchronization flow.
Storefront features and operational integrations had to develop together. A scope document described the intended result, but was not evidence that every feature had passed acceptance.
I lead an eight-person team of engineers and QA, designed the configurator data model, and supported product migration and integration onboarding.
The migration remains pre-launch; production outcomes are not yet claimed.
Scanner and return-sync development expanded the engagement beyond consultation. Recharge work remained advice; the warehouse replacement awaits approval.
Delivered tools, consulting work, and pending plans are recorded separately.
ENGINEERING · DESIGN · TEAM LEADERSHIP
Promoted from L5 on 23 June 2026 after an "Exceeds Expectations" 360° review. I lead commerce engineering work, help developers get unstuck, and coordinate delivery across storefronts, applications, and integrations. I still write code, mostly so my opinions in code review stay honest.
The role was aligned to formal engineering levels during a company restructure. I owned development across Shopify applications and full-stack systems, from requirements and architecture through testing and release. Same work, new label, better paperwork.
I built Shopify themes, headless storefront features, custom applications, and checkout extensions while helping other developers with implementation decisions. On two-developer app projects I was the senior developer and acting lead, before the title caught up.
I developed storefront features, application interfaces, APIs, and backend workflows, and worked through the bugs that came with them.
Built a location-based blood donor management platform for a charity, using PostgreSQL, Express.js, React.js, and Node.js. The pay covered internet and pocket money, so it worked more like an internship with real users.
Designed visual identities and web layouts for international clients, on Fiverr from June 2020 and directly before that. I learned to turn "can it pop a bit more?" into concrete changes. That skill transferred to engineering intact.
Ranked by how often they show up in my case studies, roles, and projects. Each one opens the work behind it.
Shopify Verified Skill badges and the courses that got me started. The certificates are real. So were the hours in the docs afterward.
Public Credly credential
View skill badge → (opens in a new tab)
Public Credly credential
View skill badge → (opens in a new tab)
Certificate inspected
View course certificate → (opens in a new tab)
Certificate inspected
View course certificate → (opens in a new tab)
A catalog can look simple while account-specific prices, approvals, and integrations do the difficult work.
Continue reading →I trace the business rule before choosing the implementation. A clean interface cannot fix the wrong model.
I write down the decisions that another developer or operator will need. Memory is not a deployment dependency.
Every choice costs something. I'd rather say the price out loud, and agree on when we check the receipt.
The successful request is the easy part. I test retries, missing data, role boundaries, interrupted workflows, and the user who double-clicks everything.
I use another service when it solves a real problem, not because the architecture diagram has an empty corner.
I turn useful discoveries into guides and technical writing, so the next developer can skip my debugging session and my sighing.
I'm looking for senior engineering and technical leadership roles where I can stay hands-on, work with thoughtful people, and leave the system easier to understand than I found it. Bonus points if your team writes things down.
Have a role, a project, or a stubborn commerce problem in mind? Tell me what you're trying to do. Plain English is welcome; a 40-page brief is optional.