I'm Sakib, a software engineering team lead in Dhaka. I build Shopify apps, storefronts, and the integrations holding them together. Physics studies, design freelancing, then code took over in 2021. I like the happy path fine. I also read the error logs, voluntarily.
44Projects and Engagements33 engagements completed
6Career RolesEngineering and design practice
8Active WorkstreamsCurrent projects and products
§ 002 · about
“I build commerce systemsthat make hard operationsboring. In the good way.”
I'm Sayed Ashraful Islam Sakib. Most people call me Sakib, which saves everyone a few syllables. I'm a software engineering team lead at Bevy Commerce, building Shopify applications, storefronts, and the integrations behind them. I'm based in Dhaka and open to worldwide remote roles. The origin story: I studied Physics, freelanced as a graphic designer, and a beginner C course turned out to be the first domino. By late 2021 I was writing JavaScript for a living. The design years never fully left, so yes, I will notice your button spacing.
§ A.1
On designing systems
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.
§ A.2
On making decisions
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.
§ A.3
On leading a team
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.
§ A.4
On life after launch
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.
Enterprise B2B distribution client · 2025–2026 · v1.0
§ 001.1 · executive summary
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.
§ 001.2 · problem statement
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.
§ 001.3 · architecture decision
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.
01Customer login
02Portal permissions
03Shopify records
Simplified architecture drawn from this case study; not a deployment diagram.
§ 001.4 · tradeoffs accepted
Keeping commerce data in Shopify avoided duplicate records but required batching, caching, and careful handling of API limits.
Hardware and subscription brand · 2026–present · v1.0
§ 002.1 · executive summary
I built a browser extension that checks device identifiers and accessory lots against order quantities before allowing label creation in the supported fulfillment workflow.
§ 002.2 · problem statement
Warehouse staff needed to catch missing identifiers, duplicate device serials, and quantity mismatches without leaving their existing shipping interface.
§ 002.3 · architecture decision
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.
01Scanner input
02Verify and commit
03Record URL
Simplified architecture drawn from this case study; not a deployment diagram.
§ 002.4 · tradeoffs accepted
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.
§ 003.2 · problem statement
The team needed a consistent product model for configurable furniture while replacing the storefront and preparing operational data flows.
§ 003.3 · architecture decision
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.
01Product model
02Configurator
03Shopify cart
Simplified architecture drawn from this case study. Dashed lines mark planned, advisory, or unlaunched work; not a deployment diagram.
§ 003.4 · tradeoffs accepted
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.
§ 004 · featured case studies
Longer arcs.
ArchitectureMigrationLeadership
Pre-launch
Coordinating a configurator and commerce migration
I lead an eight-person team of engineers and QA, designed the configurator data model, and supported product migration and integration onboarding.
OUTCOME
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.
OUTCOME
Delivered tools, consulting work, and pending plans are recorded separately.
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.
→Lead two active client teams: seven people on one, eight on the other, across theme, migration, integration, and QA engineers
→Set technical direction for architecture, scalability, reliability, and security
→Manage risks, dependencies, and scope with stakeholders before they turn into surprises
→Delegate, unblock, and mentor engineers; contribute to hiring and onboarding
→Establish engineering standards, processes, and quality practices
v4.0.0L5
2026-04 → 2026-06
Bevy Commerce · Toronto, remote from Dhaka
Senior Software Engineer
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.
→Rated "Exceeds Expectations" in the April 2025 → April 2026 360° review
→Translated ambiguous requirements into production-ready systems
→Owned planning, development, testing, deployment, and optimization
→Collaborated with stakeholders and mentored engineers through delivery
v3.0.0SENIOR
2023-09 → 2026-04
Bevy Commerce · Toronto, remote from Dhaka
Full Stack Web Developer · Senior Shopify Developer
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.
→Developed and customized Shopify themes, apps, theme app extensions, and checkout extensions
→Built and maintained backend systems and APIs
→Translated client requirements into performant technical solutions
→Rated "Great" in the company's first 360° review cycle, in 2025
v2.0.0FULL-STACK
2021-11 → 2023-09
Bevy Commerce · Toronto, remote from Dhaka
Full Stack Developer
I developed storefront features, application interfaces, APIs, and backend workflows, and worked through the bugs that came with them.
→Designed and built custom applications following scalable architecture practices
→Developed and tested APIs supporting frontend functionality
→Diagnosed and resolved application issues to maintain reliability
v1.0.0CHARITY
2021-06 → 2021-11
National Blood Caravan · Chattogram
Full Stack Web Application Developer
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.
→Implemented secure JWT authentication and scalable REST APIs
→Improved backend reliability, application performance, and overall user experience
→Built responsive interfaces and backend services for public-facing usage
v0.1.0FREELANCE
2020-04 → 2021-10
Independent · Fiverr
Freelance Graphic & Web Designer
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.
→Designed logos, business cards, flyers, brochures, and business-identity materials
→Worked with Adobe Photoshop, Illustrator, and InDesign
§ 005.B · skills
Most-used skills.
Ranked by how often they show up in my case studies, roles, and projects. Each one opens the work behind it.
I trace the business rule before choosing the implementation. A clean interface cannot fix the wrong model.
P-002
Make the handover easy
I write down the decisions that another developer or operator will need. Memory is not a deployment dependency.
P-003
Name the tradeoff
Every choice costs something. I'd rather say the price out loud, and agree on when we check the receipt.
P-004
Test the awkward path
The successful request is the easy part. I test retries, missing data, role boundaries, interrupted workflows, and the user who double-clicks everything.
P-005
Keep the stack understandable
I use another service when it solves a real problem, not because the architecture diagram has an empty corner.
P-006
Share what worked
I turn useful discoveries into guides and technical writing, so the next developer can skip my debugging session and my sighing.
AVAILABILITY
Open to senior engineering opportunities.
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.