Ahmed Farid — Senior Software Engineer, portrait
Profile

I'm Ahmed Farid — a senior engineer who ships systems end to end.

Dubai-based. For over six years I've built multi-tenant SaaS platforms, real-time auction and booking systems, AI-assisted tools, and a fleet of mobile apps shipped to production across the Gulf, the US, and the UK.

I work the whole stack — Laravel, Next.js, FastAPI, Flutter, AWS — and I'm comfortable owning a product from the first schema decision to the App Store submission and the on-call rotation after launch. I pick the stack the problem needs and own the consequences.

6+ yrs
Shipping production software
27+
Products built or shipped
17+
Countries served
B.Sc.
CS & AI · Helwan University
Engineering depth

The stack I use.

What I use, and why. Mostly proven tools that hold up in production.

Backend

Laravel · PHP · Node.js · Express · NestJS

Domain modeling, Eloquent + raw SQL where it earns its keep, queues (Horizon), Octane, Reverb, REST + auth (Sanctum, Passport, JWT).

Python

FastAPI · Django · DRF · Celery

Async APIs, SQLAlchemy + Alembic, Celery task queues, pgvector/RAG pipelines — the backbone of Qoralia and the RevealSite platform.

Web

React · Next.js · TypeScript · Vue

App router, server components, edge caching, Tailwind + shadcn/ui, Material UI, Vite, TanStack Query, Zustand, Redux.

Mobile

Flutter · Dart

BLoC, Riverpod, flutter_modular, Hive local-first state, Firebase wiring, Apple PassKit, iOS + Android store submission handled.

Data

MySQL · Postgres · Mongo · Redis

Schema design first, indexes second. MariaDB, Supabase, pgvector, InfluxDB. Redis for cache, queues, and the occasional rate limiter.

Cloud

AWS · GCP · Docker

EC2, Lightsail, RDS, S3, SES. GCP Compute/Cloud SQL. Cloudflare, Nginx, Apache, Vercel, Hetzner, Hostinger. CI/CD on GitHub Actions.

AI

OpenAI · Claude · OpenRouter

GPT-4o, ElevenLabs TTS, DALL·E, multi-provider gateways, RAG with eval gates. Shipped into Qoralia, KhebraOS, and Phonic Maps.

Reference architecture · multi-tenant SaaS
Clients
Next.js web
Flutter mobile
Admin ops
Edge
CDN cache
Auth jwt
Tenant resolver middleware
API
Laravel core
Node workers
Data
MySQL primary
Redis cache · queue
S3 media
Infra
AWS EC2 / RDS
Docker compose
SES mail
Full toolbelt

Everything I've shipped with — straight from the languages, frameworks, and platforms I work in daily.

Core Stack
LaravelNext.jsTypeScriptReactFlutterPostgreSQLRedisAWSDocker
Languages
PHPJavaScriptTypeScriptDartPythonGoHTMLCSS
Backend
LaravelNode.jsExpressNestJSFastAPIDjango
Frontend & Mobile
ReactNext.jsVueTailwindBootstrapMaterial UIViteSassshadcn/uiFlutterReact Native
Data & Storage
MySQLPostgreSQLMongoDBRedisSupabaseMariaDBInfluxDBpgvector
DevOps & Cloud
DockerKubernetesAWSGCPFirebaseCloudflareNginxLinuxUbuntuGitHub ActionsGrafanaSentryVercelApacheAuth0HostingerGoDaddyHetznerApp StoreGoogle Play
Engineering Tools
GitGitHubpnpmPostmanFigmaNotionReplitSwaggerJiraNx
Collaboration
DiscordSlackGoogle ChatClickUpAsana
AI & AI Engineering
OpenAIClaudeAnthropicCodexCursorGeminiGrokKimiOpenRouter
Architecture thinking

How I make technical decisions.

Five principles I apply on every project, and drop when the evidence says otherwise.

/ i

Boundaries before features

I draw the seams in the system before writing the screens. Tenant, role, and billing live as first-class concepts — not afterthoughts.

/ ii

Optimize for the team that ships v2

Clean read paths, audited writes, and migrations someone else can run at 2am without paging me. Code is for humans.

/ iii

Cache where it earns its keep

Premature caching is just a bug with a delay. Profile, find the read path that hurts, then cache it — and invalidate it on purpose.

/ iv

Boring choices, sharp edges

Laravel and Postgres aren't exciting. They're predictable, which is the only excitement a production system should give you.

/ v

Agents execute specs, not intentions

A vague instruction gets a plausible answer, and plausible is the expensive failure. So the spec names the constraint that rules out the obvious approach, every change is written to fail loudly rather than silently do nothing, and I verify against the deployed site — not against the agent's summary of it.

In the open

Open-source code.

My public side at github.com/ahmedfarid2 — 7 public repos. Most of my client work is private, under NDA.

Experience

Experience.

Full-time and freelance roles, on-site and remote.

Jul 2025 — NowSenior Software EngineerFull-timeRecovery AdvisersDubai, UAE · Remote
Jan 2022 — NowSenior Software EngineerFreelanceCompass MedPhonic MapsQoraliaProven ManagementKhebraEzhalAlnaimi StudiosIbdaa CourseApplyniDubai, UAE · Remote
Jun 2024 — Aug 2025Senior Software EngineerFull-timeYelo SaleSaudi Arabia · Remote
Jun — Dec 2024Software EngineerFreelanceInteractive FutureSaudi Arabia · Remote
Jun — Nov 2024Software Programming InstructorFreelancealmentorCairo · Remote
Mar — May 2024Software EngineerFull-timeArab BankCairo · On-site
May 2023 — Mar 2024Software EngineerFull-timeRevealSiteUnited States · Remote
Aug 2021 — Dec 2023Software Engineer & Art Production DirectorPart-timeCompass MedCairo · Hybrid
Why me

Why clients work with me directly.

What you can expect when we work together.

Most engineers
Ships features.
→ With me
Ships systems that survive their second year.
Most engineers
Generalist or specialist — pick one.
→ With me
Backend, web, mobile and infra, with one person accountable for all of it.
Most engineers
Disappears at handoff.
→ With me
Writes the runbook your next hire will actually read.
Most engineers
Quotes lines of code.
→ With me
Talks in business outcomes, and the trade-offs behind them.
Most engineers
Speaks in jargon.
→ With me
Translates between founders, ops, and engineers without losing precision.
Most engineers
Optimizes for v1.
→ With me
Designs v1 so v2 isn't a rewrite.
FAQ

Common questions.

If yours isn't here, ask me directly at the bottom of the page.

Both. I'm full-time at Recovery Advisers (remote), and I take on client projects of any size alongside it: larger builds run with a vetted team of engineers I work with, and you deal with me throughout. Packages and prices are on the services page.
Yes — that's where I'm strongest. Architecture, schema, deploy, the first slice in production. I can stay through scale or hand it off cleanly.
Yes — I've shipped 12+ Flutter apps to App Store and Play Store. But I usually work better when I own both ends of the API contract.

Tell me what you're building.

Need a system built, or hiring a senior engineer? Thirty minutes is usually enough to tell whether I'm the right fit. Bring the problem you have not been able to hand to anyone yet.