Skip to content

Technical skills

The tools I build with

Four years of production work across travel tech, fintech, food delivery, and CRM platforms: grouped by where each piece sits, from interface to database to deployment.

Highlighted chips are the stack I work in daily. Hover or tap any skill for more context.

  • Languages

    4 technologies

    • The language underneath every project here, in the browser and on Node.
    • Static typing across the stack; the default for all new work.
    • Semantic markup and accessible document structure.
    • Modern layout: grid, flexbox, custom properties and container queries.
  • Frameworks & Libraries

    9 technologies

    • Component model behind the OTA, CRM and ERP interfaces I've built.
    • App Router, SSR and static rendering; the framework for most production work.
    • Predictable state for large dashboards with heavy cross-screen data.
    • Lightweight state sharing where a full store would be overkill.
    • Server-state caching, refetching and pagination for data-heavy screens.
    • Node-graph canvas; used to build MaherChat's chatbot flow builder.
    • High-volume data grids with sorting, filtering and virtualised rows.
    • HTTP client with interceptors for auth, retries and error handling.
    • Real time messaging and live chat, used throughout MaherChat.
  • Styling

    4 technologies

    • Utility-first styling; the design system layer on every recent project.
    • Accessible Radix-based components copied into the codebase, so they stay editable rather than locked behind a dependency.
    • Material Design component system for React, with theming and a broad prebuilt component set.
    • Component framework for fast, responsive layouts.
  • Backend

    4 technologies

    • Server runtime for APIs, tooling and production deployments.
    • HTTP routing, middleware and REST endpoints on Node.
    • Document database for flexible, fast-moving product schemas.
    • Relational database for structured, transactional data and complex queries.
  • APIs & Data

    3 technologies

    • The integration style behind the booking, payment and CRM APIs.
    • Typed queries driving PocketX's sales, purchase and order modules.
    • Stateless auth with role-based access control across admin panels.
  • Rendering & Performance

    4 technologies

    • Server rendering for fast first paint and indexable pages.
    • Client rendering where interactivity matters more than first paint.
    • Route and component level chunks to keep bundles small.
    • HTTP, query and CDN caching to cut repeat load times.
  • DevOps & Tools

    5 technologies

    • Version control, branching and history on every project.
    • Pull requests, reviews and CI for team workflows.
    • Droplets provisioned and maintained for production deployments.
    • Reverse proxy, TLS termination and static serving in front of Node.
    • Process management and zero downtime restarts for Node services.
  • Practices

    4 technologies

    • Readable, intention-revealing code the next engineer can pick up.
    • Module boundaries that keep large codebases testable.
    • Sprint planning, estimation and iterative delivery in cross-functional teams.
    • Reviewing teammates' work and giving feedback to hold quality.