I build backend systems that hold up, and products clients actually use.
At Acksession, I built Shipping end to end, from the first client call to production. I guide AI agents, review their work, and make the key decisions.
At Luciq, I worked on the write path of a platform at 2M requests per minute, and built its statistics flow from scratch.
Me & why work with me
Led Shipping to production: 100+ carriers in one placeMoved live tenants to a new write flow with 0 writes lostIntern to Engineer II in 15 months
Three years across product startups and a large-scale platform. I refine vague needs into clear specs, write the design doc before the code, and own the work from the first client call to the on-call alert.
Ships end to end
Led Shipping from requirements to production: labels from 100+ carriers in one place.
Acksession · 2026
Built for scale, safe in production
Worked on a platform at 2M requests per minute. Moved tenants to a new write flow with 0 writes lost. On-call and SWAT.
Luciq · 2024–2026
Makes things faster
API endpoints up to 2.5× faster. Service cold start from 10 s to 4 s.
Acksession · AtenTEC
Works with AI agents
Guides AI agents, reviews their work, and makes the key decisions. Wrote the Claude skills and rules that keep the team's agents aligned.
Acksession · Agentii
Lifts the team
Mentored and onboarded 3 engineers. Led 2 engineers on Gold investment. Led 40+ organizers training 300+ students.
Luciq · Gold investment · ICPC
Solves hard problems
IEEEXtreme 86th worldwide and 5th in Egypt. ECPC bronze. ACPC regional finalist four times.
Built Shipping: one place to buy, print, track and void labels from 100+ carriers.
100+carriers in one place
2.5×faster API endpoints, up to
My part. I build Shipping end to end: backend, UI/UX and frontend. I work with the clients from the first call.
Worked with clients directly and turned their business needs into specs.
Made API endpoints up to 2.5× faster by caching dynamic permissions.
How Shipping handles 100+ carriers
Problem
4 carriers are direct integrations, the rest come through an aggregator. They don't all support the same things: label formats, papers like pick lists, batch buying, webhooks.
Decision
One flow for every carrier. Where a carrier's API is missing something, our code fills the gap, so operators follow the same steps for every carrier.
My work cycle at Acksession
requirement→refine→research→split on agents→review & test→release→feedback
PythonDjangoPostgreSQLGCPReactClaude
Scroll or press ↓ for the next one · 5 in total
Animation: Acksession: a client request through my cycle. Steps: requirement, refine, research, split on agents, review & test, release, feedback.
Shows the key ideas, not the exact flow.
Acksession: a client request through my cycle
Jul 2024 – Feb 2026 · Cairo, hybrid
Luciq
formerly Instabug
Intern · Jul 2024→Engineer I · Oct 2024→Engineer II · Oct 2025
Backend for a platform with 2M requests per minute and terabytes of data.
0writes lost in the migration
15 mointern to Engineer II
3engineers mentored
My part. Backend engineer in a team of FE, BE and QC. I worked on the write flow, built a new statistics flow, and took on-call and SWAT shifts.
Replaced the batching logic in the write flow.
Designed and built from scratch the flow that pulls statistics from the internal analytics team. My design docs aligned the stakeholders.
Mentored 3 new engineers and led their onboarding, so they shipped sooner.
How the tenant migration worked
Problem
Two write flows ran side by side for years. Their data drifted apart, the old flow caused production issues, and reads had to pick a store for each tenant.
Decision
Dashboards in an observability product don't need second-by-second data. So for each switch we paused the consumers, moved the traffic to the new flow, and resumed. Writes waited in the queue for up to 30 minutes. Nothing was lost.
Rollout
Non-tenant production traffic first, then a week of monitoring, then one tenant a day, about 5 in total. We watched throughput and metrics after each switch. The old flow stayed up until every tenant was stable, and rollback was moving the tenant back.
Result
The team spent about 6 months getting the code ready. I wrote most of the implementation. One write flow: no data mismatches, no per-tenant read logic.
GoRuby on RailsClickHouseMySQLGraphQLSidekiqKafkaKubernetesAWSCursor
Animation: Luciq: the write path and the sprints into it. Steps: pre-planning, planning, implement, review & test, release.
Shows the key ideas, not the exact flow.
Luciq: the write path and the sprints into it
Sep 2023 – Jun 2024 · El Tor, onsite
AtenTEC
Backend Engineer
ERP backend features on large datasets, built in Go.
2.5×faster cold start on Cloud Run: 10 s → 4 s
My part. Backend engineer. I designed services with the solution architect and built them in Go.
Rewrote NestJS services in Go. Cold start on Cloud Run went from ~10 s to ~4 s.
Built reusable microservices for image processing, cloud storage and statistics.
Built a background job that flags unsafe photos.
Moved shared reference data (companies, cities) used by several services to a new store: copied it, switched the readers, then dropped the old copy.
Built ERP features on large datasets with Go concurrency.
What I built at AtenTEC, in order
compress photos→moderate in background→rewrite NestJS → Go→stress test
GoGinGCPTypeScriptNestJSMongoDBMySQLDocker
Animation: AtenTEC: architect talks become services. Steps: compress photos, moderate in background, rewrite NestJS → Go, stress test.
Shows the key ideas, not the exact flow.
AtenTEC: architect talks become services
2022 – 2023
Internships
Two teams, two stacks
Infrastructure as code first, then full-stack product work.
5merged PRs in the Pulumi provider
My part. Intern on two teams. I shipped features in each stack through code review.
CodeScalers
Jul – Sep 2023 · Cairo
Started the Pulumi provider for ThreeFold Grid, then added its network, Kubernetes and name gateway resources.
Animation: Focal Point: booking a workspace. Steps: find a workspace, check availability, book & pay, chat with the owner.
Shows the key ideas, not the exact flow.
Team lead · team of 3 · private repo · 2025
Gold investment
2race conditions on money closed: double credit, overdraw
What it is. Buy gold by the milligram at the live price. Fund a wallet with InstaPay or Vodafone Cash, and withdraw back to it.
My role. Team lead of two engineers.
Researched big, vague features and refined them through discussions, then broke them into detailed tasks.
Reviewed the team's code in detail and mentored them.
Caught two money races in code review and designed both fixes. A database check (balance ≥ 0), so a buy can never overdraw the wallet. A conditional update inside one transaction (pending → approved, exactly one row), so a deposit is credited only once.
Opened tasks for gaps nobody had asked for, like error tracking and logs.
How it works
deposit with InstaPay→review · one approval wins→wallet credited→buy gold · no overdraw
Animation: Gold wallet: InstaPay deposit to a safe buy. Steps: deposit with InstaPay, review · one approval wins, wallet credited, buy gold · no overdraw.
Shows the key ideas, not the exact flow.
Team of 3 · private repo · 2026
Agentii in progress
What it is. An AI agent for your customers. It answers, sells, onboards, and gets things done in your chat.
My role. I plan the product and build the frontend. Two backend engineers build the API.
Plan the big features and write the list of upcoming ones.
Do the research, write detailed tasks, and mentor the team.
Design and build the UI/UX, and wire it to the API.
Wrote the Claude skills and rules that keep our agents' work aligned.
What it is. An e-learning platform. Instructors publish courses by week, with videos, readings and quizzes. Students buy courses, track progress and get certificates.
My role. I built the backend. A teammate built the frontend.
Built the REST API: Google sign-in, courses, quizzes, reviews, discounts, purchases and certificates.
Stored videos in S3 and streamed them through the API. Each video link expires after 60 s, to protect paid lessons.
Built the stats endpoint for instructors.
How it works
watch lessons→paid lesson locked→enroll→upload a lesson→stats