ZUN UL NOOR

Frontend Engineer / Full-Stack Developer — Karachi, Pakistan

ZUN UL NOORFrontend Engineer / Full-Stack Developer — Karachi, Pakistan

FIG.01 — Self portrait73 lines / 100 glyphs wide
ASCII-art portrait of Zun Ul Noor
73 lines — hover to decodeZUN UL NOOR

I'm Zun Ul Noor — a frontend engineer and full-stack developer based in Karachi, Pakistan, working on production SaaS dashboards, responsive interfaces, and API-driven web applications across React, Next.js, Node.js, WordPress, and Python. Day to day that means maintaining live dashboards, turning Figma designs into responsive product screens, and sweating the operational details — pagination, filtering, tracking states — where interfaces succeed or fail.

  • BaseKarachi, Pakistan
  • FocusMERN Stack · WordPress · Webflow

Capabilities

What I work with.

  • Frontend

    React.js · Next.js · JavaScript · HTML5 · CSS · MUI · Tailwind CSS · Bootstrap

  • Data & APIs

    REST APIs · React Query · Pagination · Search · Filtering

  • Maps & Geo

    Google Maps · Mapbox · Geolocation interfaces

  • CMS & Plugins

    WordPress · Gutenberg · Custom plugins · Shortcodes · REST API

  • Backend

    Node.js · Express · MySQL · MongoDB · Firebase

  • Applied AI & Python

    Python · Streamlit · XGBoost · AI integration

How I work →

What I do

Where I spend my days.

Most of my work sits in one place: interfaces that real businesses run on. I maintain production SaaS dashboards where one broken filter can stall a dispatch team, build new product screens from design files, and extend sites and plugins on WordPress. The stack around that work is React, Next.js, and TypeScript on the frontend, Node.js and REST APIs behind it, and — increasingly — Python and Streamlit when a product needs a model in the loop. What stays constant is the way I work: read the existing system first, change it surgically, and verify it against real workflows.

  • SaaS dashboards

    Ongoing maintenance and feature work on live dashboards — order, dispatch, driver, and reporting views — including production bug fixes and client-driven functionality shipped without breaking existing business workflows.

  • Product interfaces

    Figma-to-production implementation for booking flows, maps, and operational tools. Responsive by default: the design has to hold on every viewport, not just the artboard.

  • WordPress & plugins

    Custom plugin engineering — content architecture, Gutenberg blocks, shortcodes, REST endpoints, and security hardening. My own plugin, Zipped Docs, is published on the WordPress Plugin Directory.

  • Python & ML products

    Applied machine learning on the web: Streamlit applications wired to trained models, interactive prediction workflows, and recommendation output framed as guidance — shipped as working products, not notebooks.

Approach

How the work gets done.

Working on production software teaches you restraint. New features land inside systems other people depend on, so my first job is always to understand what exists — the data flows, the edge cases, the business rules hiding in the UI — before changing anything.

  • Maintain before you rebuild

    Read the existing system first. Extend it where it is strong, replace only what genuinely fails the user, and keep the change surgical.

  • Operational clarity is design

    Pagination, search, filtering, loading states — the unglamorous interface work is where products succeed or fail. I treat clarity as a design requirement, not a nice-to-have.

  • Ship the whole thing

    From architecture through release, including the security and deployment details — a WordPress plugin on the public directory and a deployed ML app are the proof.

Briefly, about me

Engineer first.

I maintain production SaaS, build interfaces from Figma to deployment, and ship independent products — a published WordPress plugin and a deployed ML app. Business workflows first, technology in service of them. Most projects start the same way: a short conversation about what is actually broken or missing, then a scoped first step.