Loading search…
Loading search…
Looking for a specific skill, platform, or kind of project? Search covers every section: skills, case studies, roles, the project register, writing, the about pages, principles, education, and credentials. Abbreviations like JS or TS work, and so do typos. Faster than reading everything, though I'd be flattered if you did.
18 results for “Team”.
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.
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 engagement began with consultation and expanded into scanner tooling, return-sync middleware, subscription advice, and warehouse planning.
… recurring service, fulfillment, and returns crossed several systems, with different teams responsible for different parts. I built the scanner extension and return-sync …
I investigated a wholesale checkout, built a custom application, and helped deliver a replacement after the custom approach was blocked by the platform immediately before launch.
… change The custom checkout was completed but did not become the launched solution. The team changed approach following a platform restriction. My work also covered backend …
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.
Senior developer and acting lead on a two-developer team. Built checkout functionality and adapted the approach after platform restrictions blocked the planned release.
Lead an eight-person team: two theme engineers, a migration engineer, two senior integration engineers, and three QA engineers. Designed the configurator data model. The migration is pre-launch.
Lead a seven-person team: four theme engineers, two QA engineers, and a migration engineer. Built store-credit automation and an accounting export application. The application is developer-complete; deployment was pending at the last update.
What to build, what to defer, and which consequences a team can maintain.
Why ownership, rollback paths, and useful logs matter after the launch announcement.
… run it without you. Operational maintainability is the gap between “it works” and “the team can deploy, monitor, and fix this at 2 a.m. without an archaeology session.” Ecommerce …
Making tradeoffs explicit without pretending to predict every future requirement.
… tax every future feature. What's flexible on paper might be expensive to run. Strong teams don't chase perfect architecture. They make tradeoffs explicit: what we're optimizing …
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.
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.
Shopify apps, B2B portals, headless storefronts, and the integrations connecting them. I also lead a software engineering team, which means more code review and fewer solo heroics.
Senior and lead engineering roles where I can stay hands-on, help a team grow, and stay responsible for the system after the launch post goes up.
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'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.
… Based in Dhaka, Bangladesh (GMT+6) Working North American hours for a Toronto team: ET / CT The time difference is my problem to solve, not yours. Messages go straight to …