Senior iOS Engineer · Cairo, Egypt
_{I build modular SDKs and consumer features that ship to millions of people.}

I'm a Senior iOS Engineer at Yassir, on Financial Services.

I lead the Wallet SDK — a modular Swift SDK inside a monorepo, consumed by four host apps (SuperApp, Driver, Cash Agent, Sales Rep) across Algeria, Tunisia, Morocco and South Africa, serving millions of monthly active users. Balances, transactions and payment processing, in several markets and several languages.

• Architecture — Clean Architecture, MVVM, SOLID, modularization in a monorepo, dependency injection. Boundaries enforced by the build, not by convention.
• Concurrency — async/await and structured concurrency; actors where the concurrency is real, main-thread simplicity where it isn't.
• Performance — cold-launch and UI-hang work driven by Instruments, not guesswork.
• Security — secrets out of the binary with Arkana, biometric auth, and automated scanning via Gitleaks, MobSF and TruffleHog.
• Shipping safely — LaunchDarkly and Firebase Remote Config for staged rollouts and A/B tests; Sentry and Crashlytics to know what actually happened.
• Quality gates — Bitrise, SwiftFormat, SwiftLint, Danger Swift and SonarQube, so review is about substance.

I treat AI as part of the toolchain, with the same rigour as the rest of it.

• One model writes, a different one reviews. Claude Code implements; Cursor reads the diff cold. A model reviewing its own work brings the assumptions that produced the bug.
• Instructions live in the repo — CLAUDE.md for conventions and architectural rules, AGENTS.md pointing at it so any vendor's agent reads the same guidance. Not in a chat window.
• Nothing is accepted because it compiled. Tests for logic, snapshots for layout, and profiling for performance decide what survives.

I also spent a year at Turing training and reviewing LLM output on Swift and iOS — authoring reference solutions and rubrics across UIKit, SwiftUI, Combine and concurrency, which is a useful perspective on where these tools are reliable and where they are not.

Most of my production work lives in private repositories. What's public is smaller by nature:

• modular-coordinator-di — the module graph, coordinator navigation and DI conventions I reuse as a starting point.
• Appetizers-App · Netflix-Clone · Tourist-Attractions — smaller SwiftUI and UIKit builds.

_{Also: Arabic (native), English (fluent), German (learning). Cairo University, Faculty of Engineering.
Open to talking about iOS architecture, modularization, or anything shipped at scale.}