Ahmed Ghazy, Full-stack developer. I take over web apps that are stuck and ship the next release.

Selected work

• AI marketing platform · Client work through caisy

  ScriptBee

  Built the chat experience, agent tools and background tasks that let users return to long-running work, plus Google Ads connections and onboarding.

  Technologies used: Next.js, Trigger.dev, TypeScript, Google Ads API

  Read the case studyVisit site (opens in a new tab)

• Kitchen brand site · Through caisy

  LEICHT

  Built the multi-language leicht.com site in Qwik with CMS content and GraphQL, plus an internal kitchen configurator.

  Technologies used: GraphQL, Headless CMS, i18n, Qwik

  Read the case studyVisit site (opens in a new tab)

Clients and colleagues

• “Ahmed is a great engineer who was conscious of my team’s deadlines to deliver even when we had given him last minute tasks. He was reliable and available to us at any time we needed to introduce something new or make a change.”

• “He’s met my expectations and even went beyond. I would definitely hire him again.”

• “Ahmed was great! Highly attentive and will do what it takes to get the job done. I will definitely rehire Ahmed whenever I have another project.”

• “Ahmed is the kind of senior engineer who makes everyone around him better without making a big deal of it. … he hands over challenging work instead of holding onto it, and he makes sure people have the support to grow through it.”

1. 2025 — to Present

   Smart Bricks (opens in a new tab)

   Senior Full-Stack Engineer

   AI platform for real-estate investing, backed by a16z speedrun.

   What I built, Smart Bricks

   • Lead the frontend team: I own the architecture and build it hands-on, review the team’s pull requests and mentor newer engineers.
   • Moved data fetching to the server with the Next.js App Router and split the property pages into server-rendered sections.
   • Rebuilt the valuation and score modals so investors can see why a property got its price and score.
   • On the backend, built Next.js API routes such as the Clerk sign-up webhook and the health check, and cut the API’s Docker image from about 9 GB to about 2 GB.
   • Set up observability with OpenTelemetry, Prometheus, Loki, Tempo and Grafana, plus PostHog feature flags, and built the Storybook component library.

   Technologies used: Next.js, TypeScript, React, TanStack Query, Tailwind CSS, Storybook, PostHog, Grafana

2. 2022 — to 2025

   caisy (opens in a new tab)

   Frontend Engineer

   Headless CMS.

   What I built, caisy

   • Rebuilt the blog category and article pages of caisy’s marketing site from styled-components to Tailwind CSS, and rewrote a class-based photo-gallery slider as a hooks component.
   • Built features on Next.js, tRPC and Drizzle codebases: schema and migrations for Stripe billing and subscriptions, users, workspaces and chat.
   • Added AI translation of content fields to the editor.

   Technologies used: React, Next.js, TypeScript, tRPC, Drizzle, Tailwind CSS, styled-components

3. 2022 — to 2024Part-time

   Stake (opens in a new tab)

   Frontend Engineer

   Fractional real-estate investment platform.

   What I built, Stake

   • Built features and shared components for the investor-facing web app. The product details are confidential.
   • Built the marketing team’s emails in Arabic and English, with right-to-left layouts that held up across email apps.

   Technologies used: React, TypeScript, Sass, HTML email, Arabic RTL

4. 2022 — to 2023Freelance on Upwork

   Independent

   Frontend Engineer

   This is where I started as an engineer.

   What I built, Independent

   • Built React apps and marketing sites for e-commerce and SaaS clients.
   • Built component libraries with styled-components and BEM.
   • Fixed cross-browser bugs and turned designs into HTML and CSS.

   Technologies used: React, JavaScript, styled-components, HTML & CSS, BEM

About

Working in quality taught me to look at software from the customer’s side.

• 5 November 2026

  What an app audit should tell you before you pay for fixes

  What a short audit of a stuck web app should give you. One page in plain words, the risks to your customers, keep, fix or rebuild, and the fixes in order.

• 14 October 2026

  What to build before you add AI to your product

  A checklist for adding an LLM feature or an agent to a real product, from the narrow job to limits, logging and a person in the loop.

• 13 October 2026

  Fix or rebuild? How to decide on an inherited web app

  A way to decide whether an inherited web app should be repaired or rewritten, with the signs that point each way and a safer middle path.