Skip to content
Noor Mohammad

Services

I take on a few builds at a time — usually a product surface plus the admin and API it needs.

01

Product engineering

4–12 weeks

Next.js and TypeScript for catalogs, roles, and dashboards that have to survive the second hire.

  • — A runnable app, not a prototype deck
  • — Auth, roles, and the admin the ops team will actually open
  • — Handover notes the next engineer can follow

Who it’s for. Founders and product teams who need a surface shipped, not staffed forever.

02

Mobile with React Native

6–14 weeks

Expo apps that share a catalog and API with the web — offline-tolerant when the work happens away from a desk.

  • — A shared model with the web, not a second backend
  • — EAS build and a release path
  • — The unglamorous parts: auth, empty states, bad networks

Who it’s for. Teams whose product is not only a browser tab.

03

Commerce systems

8–16 weeks

Storefront, admin, Stripe, and a merchandising CMS — the desk behind the shop, not only the shop.

  • — One catalog across storefront and ops
  • — Checkout that fails loudly, with webhooks you can read
  • — Merchandising that is not a plugin graveyard

Who it’s for. Retail and marketplace teams tired of stitching a theme to a spreadsheet.

04

Teaching & enablement

Days to a quarter

Workshops, recorded series, and pairing from production — the architecture I ship is the architecture I teach.

  • — A syllabus that can ship, or it does not belong
  • — Pairing on the actual repo
  • — Recorded lessons the team can replay

Who it’s for. Teams who want the next hire to inherit a system, not a mystery.

Fixed-scope, retained, or teaching. Remote from Dhaka (GMT+6), overlap EU and US mornings.

Before you write the brief.

Next

Need a product engineer who can also teach the team?

I take a small number of builds. If the work is a product surface plus the admin and API it needs, write me.

Start a conversation
noor.jsdivs@gmail.com