Skip to main content
Mohamed Noor
Available for workTaking on new projects, with capacity for one build at a time.

Mohamed Noor Figma files in. Production Next.js out.

Front ends that match the design file, hold their performance budget, and pass a keyboard test before handover. And React, Node, and Postgres platforms for teams in healthcare and fintech.

Start a projectSee case studies

Working with

  • React
  • Next.js
  • TypeScript
  • JavaScript
  • Tailwind CSS
  • shadcn/ui
  • React Hook Form
  • Node.js
  • Express.js
  • Zod
  • PostgreSQL
  • MongoDB
  • Supabase
  • Neon
  • Prisma
  • Drizzle
  • Git
  • Docker
  • GitHub Actions
  • Vitest
  • Vercel

  • 95+

    Lighthouse performance

    Measured on this site's own routes with the mobile preset, re-run before each release.

  • WCAG 2.1 AA

    Accessibility target

    Every route passes an automated axe check plus a manual keyboard pass, in both themes.

  • 100%

    Statically generated routes

    Visible in the Next.js build output route table; the only server work is the contact form.

About

How I work

I build web products end to end, and I care most about the part clients usually cannot see: whether the thing is fast on a mid-range phone, whether it works with a keyboard, and whether the next developer can read it.

Availability
Available for work
Read how I work

Services

Two ways to work with me

Both tracks run the same way: small reviewable pieces, a staging URL you can open at any point, and a handover that leaves you able to change things without me.

  • Figma to production Next.js

    Founders, designers, and small agencies with a finished design file and no front-end capacity.

    A finished design file becomes a responsive, accessible Next.js site that matches the design, loads fast on a mid-range phone, and is straightforward to edit afterwards.

    Typical timeline
    One to three weeks for a typical marketing site

  • Healthcare and fintech platforms

    Technical founders and product leads building a regulated product on React, Node, and Postgres.

    Front end and API work for products handling sensitive data, where access control, auditability, and a real testing story are requirements rather than nice-to-haves.

    Typical timeline
    Four to twelve weeks, depending on scope
See what each track includes

Work

What I have built, and what it changed

Outcome first, with the measurement each number came from. Both tracks are represented.

Projects marked Example project are seeded examples rather than client work, and are replaced before this site goes live.

  • Figma to production Next.jsExample project

    Design file to production marketing site

    A finished Figma file for a six-page marketing site, built as a responsive Next.js application with a typed content layer the client edits without touching code.

    Role
    Sole developer
    Period
    2025

    Measured

    • 98

      Lighthouse performance

      Mobile preset, run against the deployed home page

    • 1.4s

      Largest Contentful Paint

      Mobile throttled, measured on the deployed site

    • Every screen and state

      Design fidelity

      Side-by-side review against the source file before handover

    • Next.js
    • TypeScript
    • Tailwind CSS
    • Vercel
  • Healthcare and fintech platformsExample project

    Clinician-facing records platform

    Role-aware interfaces for a patient records product, where what a user can see depends on their relationship to the record and every read is auditable.

    Role
    Front end and API
    Period
    2024 to 2025

    Measured

    • Enforced server-side

      Access rules

      Every query scoped in the repository layer, not in the view

    • Every record read

      Audit coverage

      Append-only log written in the same transaction as the read

    • All authorization logic

      Test coverage

      Unit tests on the permission resolver, run in CI

    • React
    • Next.js
    • Node.js
    • PostgreSQL
    • TypeScript
  • Healthcare and fintech platformsExample project

    Reconciliation dashboard

    A dashboard for spotting and resolving mismatches between two ledgers, built so an operator can see the discrepancy and the evidence for it on one screen.

    Role
    Sole developer
    Period
    2024

    Measured

    • Under 30 seconds

      Reconciliation run

      Measured on a day of production-scale transaction volume

    • Integer minor units

      Money handling

      No floating point anywhere in the calculation path

    • Idempotent

      Repeat runs

      Re-running a completed day produces no duplicate entries

    • React
    • Next.js
    • Node.js
    • PostgreSQL
View all projects

Stack

What I build with, and where I have used it

Grouped by where each one sits in a build. No self-assigned percentages: a score I award myself would not be evidence.

Front end
  • React
  • Next.js
  • TypeScript
  • JavaScript
  • Tailwind CSS
  • shadcn/ui
  • React Hook Form
  • Accessibility
Back end
  • Node.js
  • Express.js
  • REST APIs
  • Server Actions
  • Zod
  • Authentication
Data
  • PostgreSQL
  • MongoDB
  • Supabase
  • Neon
  • Prisma
  • Drizzle
  • Audit logging
Tooling
  • Git
  • Docker
  • GitHub Actions
  • Vitest
  • Playwright
  • Vercel
Practices
  • Performance budgets
  • Design fidelity
  • Written handover
See where I have used each one

Experience

Where I have worked

Reverse chronological, with what changed because I was there rather than a list of duties.

  1. - Present

    Freelance web developer at Independent

    Design-to-code builds and platform work for founders and small teams, working directly with the people who own the product.

  2. -

    Front-end developer at Example Health

    Built clinician-facing views for a patient records product, working alongside a backend team on a shared Postgres domain.

  3. -

    Web developer at Example Studio

    Turned agency design files into production marketing sites across a range of client brands.

See the full history