Muhammad Taaha - Full Stack Developer

Overview

Frontend developer (approx early-career, Middle level) focused on building React and Next.js applications with a pragmatic approach to pages and routing. The strongest proven skill is building routed React/Next pages and data flows using getStaticProps/getStaticPaths and client-side SWR fetching as shown in pages/events/[eventId].js and pages/events/[...slug].js. There is little evidence of automated testing, advanced state machines, request cancellation, measured performance work, or production-grade accessibility tooling in public code.

Phone

Timeline

Frontend Developer · Middle

Hysab Kytab · Full-Time

Oct 2023 to Present 3 Years 1 Month Karachi In office

Develops and maintains scalable web applications using React.js and Next.js. Implements Redux Thunk to manage state and handle API workflows efficiently. Designs reusable UI components and collaborates with backend teams to ensure reliable API integration. Optimizes application performance using clean coding practices.

React.js

Next.js

Redux

Full Stack Developer · Middle

Systems Limited · Full-Time

Aug 2021 to Sep 2023 2 Years 1 Month Karachi In office

Builds and maintains full-stack applications using ReactJS, Node.js, Express.js, and MongoDB. Integrates RESTful APIs to keep data flow consistent between client and server. Works with cross-functional teams to deliver features on schedule and improves user experience through reusable components and maintainable code.

React.js

Node JS

Rest API

Frontend Developer · Middle

Omega Soft · Full-Time

Jun 2019 to Jul 2021 2 Years 1 Month Karachi In office

Designs and develops responsive user interfaces with ReactJS. Integrates RESTful APIs to support dynamic content and ensure smooth client-side updates. Ensures cross-browser and cross-device compatibility and maintains clean, reusable code through version control and code review practices.

React.js

Rest API

Sir Syed University of Engineering and Technology

Bachelor's Degree · Computer Science

2018 Karachi, Pakistan

Projects

Hamad MS Teams Task Management with Chatbots

Built an internal task management tool integrated into Microsoft Teams for a client in Qatar. Developed chatbots using Microsoft Adaptive Cards to streamline task assignment and updates in Teams channels. Implemented the React front-end integration to provide a smooth user experience inside Teams.

STC API Management with Apigee

Worked on API management and gateway configuration for STC using Apigee on Google Cloud. Implemented API security policies, traffic management, and analytics. Supported secure, scalable integrations between multiple microservices and internal systems.

Digicel Backend Microservices

Designed and built backend microservices for a telecom operator web portal. Implemented scalable APIs for real-time customer account management and billing. Focused on reliability and efficient operations for high-traffic usage.

Technical skills

Languages

3

JavaScript

Node JS

TypeScript

Frontend

3

React.js

Next.js

Redux

Other

25

PostgreSQL

Rest API

Bootstrap

React Router

AWS

Express

Bcrypt

Mongoose

Nest.JS

Joi

SWR

MySQL

Redis

Amazon S3

GCP

React Bootstrap

Amazon EC2

API Gateway

Apache Kafka

GitHub

GitLab

Postman

Dotenv

CSS Modules

State Management

Middle Frontend Developer Confidence: Medium App Engineer

Frontend developer (approx early-career, Middle level) focused on building React and Next.js applications with a pragmatic approach to pages and routing. The strongest proven skill is building routed React/Next pages and data flows using getStaticProps/getStaticPaths and client-side SWR fetching as shown in pages/events/[eventId].js and pages/events/[...slug].js. There is little evidence of automated testing, advanced state machines, request cancellation, measured performance work, or production-grade accessibility tooling in public code.

UI Component Architecture

3/10

How interface parts are built

Basic component decomposition and CSS-module based components for pages and lists, but largely tutorial-level composition without a custom design system or advanced composition patterns.

Evidence

Mtaaha94/nextjs-chapter-4/components/events/event-item.js Mtaaha94/next-chapter-7/components/ui/button.js Mtaaha94/next-chapter-7/components/events/events-search.js

Responsive & Cross-browser

4/10

Works on all screens and browsers

Responsive CSS and feature-detection present via media queries, prefers-color-scheme and prefers-reduced-motion rules, showing attention to cross-device and accessibility-reduction cases.

Evidence

Mtaaha94/next-chapter-7/styles/Home.module.css Mtaaha94/next-chapter-7/styles/globals.css Mtaaha94/nextjs-chapter-4/components/events/event-item.module.css

Performance Optimization

3/10

Speed of the interface

Uses Next.js SSG/ISR (getStaticProps/getStaticPaths) and client-side SWR fetch for data, indicating awareness of server/client rendering tradeoffs but lacks measured optimizations or advanced bundling work.

Evidence

Mtaaha94/next-chapter-7/pages/events/[eventId].js Mtaaha94/next-chapter-7/pages/events/[...slug].js

Accessibility & Semantics

3/10

Usable for everyone

Some semantic elements and basic a11y patterns are used (labels, time/address tags, alt attributes), but no automated accessibility testing or advanced focus management on custom widgets is present.

Evidence

Mtaaha94/next-chapter-7/components/events/events-search.js Mtaaha94/nextjs-chapter-4/components/events/event-item.js

State Management & Data Flow

3/10

Managing data in the app

Typical React state and data flow with useState/useEffect, router-driven params, SWR client fetching and Next.js data fetching; no evidence of request cancellation, optimistic updates or state machines.

Evidence

Mtaaha94/next-chapter-7/pages/events/[...slug].js Mtaaha94/next-chapter-7/pages/events/[eventId].js Mtaaha94/react-training-1-tasl/src/components/Signup.js

UX & Visual Polish

3/10

Look and feel quality

Visual polish and UX details (animations, loading states, toast validation) exist, but deeper UX patterns like skeletons, undo, or measured perceived-performance improvements are not present.

Evidence

Mtaaha94/next-chapter-7/styles/Home.module.css Mtaaha94/react-training-1-tasl/src/components/Signup.js

Expertise

React· Middle

Modern Web Frameworks· Middle

Technologies

TypeScript

Node JS· since 2021 · Middle

Redux· since 2023

Nest.JS

GCP

Next.js· since 2023

Bootstrap

AWS

React.js· since 2019

SWR

CSS Modules

Amazon EC2

React Router

React Bootstrap

GitHub

GitLab

Amazon S3

API Gateway

Recommendations

Build dynamic Next.js features and SSR/ISR flows that rely on getStaticProps/getStaticPaths and SWR for incremental-fetch patterns.
Implement form-driven UI and auth flows with React Router and React Bootstrap, improving validation and secure storage patterns.
Refactor reusable UI into a small component library with documented props, a11y behaviors, and unit/visual tests.
Add instrumentation and performance measurement (LCP/INP, bundle analysis) and implement targeted optimizations with before/after metrics.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

next-chapter-7 nextjs-chapter-4 react-training-1-tasl

Junior Blockchain Developer Confidence: Medium Generalist

Junior front-end developer focusing on Next.js-driven event listing and detail UIs. The strongest proven skill is building Next.js pages and data-fetching flows using getStaticProps/getStaticPaths and client-side data with SWR as shown in pages/events/[eventId].js, pages/events/index.js and pages/events/[...slug].js. There is no evidence of backend systems, testing/CI, TypeScript, or any Web3/smart-contract work in the public code.

Smart Contract Development

Writing smart contracts

Not evidenced in public code

Security & Audit

Checking contracts for flaws

Not evidenced in public code

Blockchain Protocol Understanding

Knowing how blockchains work

Not evidenced in public code

DApp & Web3 Integration

Connecting apps to blockchain

Not evidenced in public code

Tokenomics & DeFi Logic

Token and finance logic

Not evidenced in public code

Decentralization & Trust Model

Designing trust without middlemen

Not evidenced in public code

Industries

Events & Ticketing· Junior

Recommendations

Develop event-focused frontends and public-facing pages using Next.js SSG/SSR and incremental static regeneration patterns (extend getStaticProps/getStaticPaths for real APIs).
Add automated tests and CI (unit tests for components and integration tests for page flows) to demonstrate robustness and production readiness.
Adopt TypeScript and stronger typing across components to reduce runtime errors and to signal readiness for larger codebases.
Integrate with a real backend API (authentication and paginated event endpoints) and add error/retry handling for network failures.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

next-chapter-7 nextjs-chapter-4 nextjs-chapter-6

Intern Backend Developer Confidence: Low Generalist

Frontend-focused web developer (Junior) with a strength in building modular Next.js/React UI for event-listing experiences. The strongest proven skill is composing modular Next.js pages and components and using ISR and client-side data fetching as shown in next-chapter-7/pages/events/[eventId].js and components/events/event-item.js. There is little to no evidence of production backend architecture, database migrations, concurrency handling, or robust API design in the human-authored code.

API Design

1/10

How well APIs are designed

Minimal API design decisions; the code consumes a REST endpoint with basic client-side fetch/SWR and does not demonstrate versioning, idempotency, or a stable error contract.

Evidence

next-chapter-7/pages/events/[...slug].js: useSWR fetch('https://nextjs-course-c81cc-default-rtdb.firebaseio.com/events.json') and basic error handling

next-chapter-7/components/events/events-search.js: form submitHandler that triggers router navigation (client-driven API query pattern)

Data Layer & Database

1/10

Working with databases

No real database or migration history in the human-authored files; data is provided via an in-memory dummy data module and simple helper calls.

Evidence

nextjs-chapter-4/dummy-data.js: getAllEvents, getFilteredEvents, getEventById - in-memory data structures

next-chapter-7/pages/events/[eventId].js: imports getEventById and getFeaturedEvents (usage of simple helper-based data retrieval rather than DB transactions)

Scalability & Performance

2/10

Handling load and speed

Basic scalability choices visible (static generation with revalidate and fallback, client-side SWR fetching), but no caching strategy, queueing, connection pooling, or measured performance tuning.

Evidence

next-chapter-7/pages/events/index.js: getStaticProps with revalidate: 60 (ISR usage)

next-chapter-7/pages/events/[eventId].js: getStaticProps and getStaticPaths with fallback: 'blocking', and next-chapter-7/pages/events/[...slug].js: useSWR client fetch

System Architecture

2/10

Overall system structure

Clear, conventional component/module separation for UI concerns (components, event-detail, events) but overall architecture is a small tutorial-style Next.js app without non-trivial service decomposition or config/secret management patterns in human-authored files.

Evidence

next-chapter-7/components/events/event-item.js: isolated presentational component

next-chapter-7/components/event-detail/* and next-chapter-7/components/ui/*: consistent folder/component structure

Security & Auth

1/10

Protecting data and access

Very limited security evidence: simple input validation for numeric filters and error UI, but no authentication/authorization, token lifecycle, or secrets hygiene in the human-authored frontend code.

Evidence

next-chapter-7/pages/events/[...slug].js: numeric validation of URL filter params and ErrorAlert usage

Reliability & Observability

2/10

Stability and monitoring

Basic reliability patterns such as loading states, error UI and ISR fallback are present, but no timeouts, retries with backoff, structured logging, or observability/metrics instrumentation.

Evidence

next-chapter-7/pages/events/[...slug].js: loading state with early return and ErrorAlert for invalid filters

next-chapter-7/pages/events/[eventId].js: fallback handling with loading state and getStaticProps revalidate

Technologies

Rest API· since 2019

Express

Bcrypt

Joi

Apache Kafka

Mongoose

Dotenv

Recommendations

Develop static and server-rendered Next.js sites and feature pages (ISR/SSG/SSR) and UI component libraries for small-to-medium web projects.
Take on frontend roles focused on client-side data fetching patterns (SWR/fetch), routing and UX around loading/error states.
If expanding to fullstack work, implement a small Express + Mongoose API (with dotenv, Joi validation and token-based auth) and add explicit tests and migration history.
Add observability and resilience: timeouts, retries with jitter for network calls, and simple structured logging to prepare code for production environments.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

next-chapter-7 nextjs-chapter-4 blog-

Job preferences

Work permits: Pakistan
Citizenship: Pakistan
Salary: from $80k per year
Employment type: Full-Time
Locations: Karachi
Company size: 1-10