Muhammad Raheel is a Flutter Tech Lead based in Pakistan, currently leading the mobile team at Codergize. He has published twenty apps across fourteen domains for seven different companies in five countries, and led teams of five to twelve developers along the way.
The start was native Android in Java. REST integrations, SQLite, and the unglamorous work of making an app behave on hardware you cannot control. That period is the reason platform problems still feel legible today: signing, permissions, background execution and memory pressure are not abstractions when you have debugged them without a framework smoothing things over.
Flutter came next, and with it a training role at Microprogrammer in Layyah. Teaching Flutter to developers who had never written Dart forces a particular kind of clarity, because you cannot explain a state management choice to a room of beginners if you only half understand why you made it. That role expanded into team lead, then into client communication, requirement analysis and architecture design end to end.
A short senior stint at Fleact Tec followed, focused on reusable component libraries and performance work on builds already in production. Then in March 2024, the current role: Flutter Tech Lead at Codergize, a Lebanon-based agency operating through a UK entity, working remotely with an international team.
That job is where most of the published portfolio comes from. Not one product built repeatedly, but apps across genuinely unrelated domains, which is a specific kind of training. A dental booking network and a fuel station telemetry dashboard share almost no product logic, but the second one is faster to build because of the first. Patterns transfer even when features do not.
The work that matters most is the part users never see. Tamam and DocDoc are each two apps on two platforms sharing one backend and one live order state, which means every availability change has to stay consistent across four binaries. Rewardee takes the opposite approach and holds both roles inside a single binary behind role-based access and offline sync. Those are architecture decisions with consequences that only show up in year two.
Alongside that: payment gateways most developers have never touched, including MyFatoorah for the Gulf and Whish Money for Lebanon, plus mobile money and cash on delivery for a grocery app in Liberia. AI shipped into real products rather than demos, classifying Arabic economic news by market impact in Tradium and running an audio-to-transcription pipeline in Reppic for a Dutch sales platform, in six languages.
Currently open to contract work and full-time roles, remote.
Codergize · Lebanon
Leads the Flutter development team and owns mobile application architecture. Mentors junior and senior developers, runs code review, and collaborates with backend and UI/UX teams on scalable mobile solutions. Ships Android and iOS releases and integrates Firebase, GraphQL, Shopify APIs, AI services and payment gateways. Maintains and optimises applications already in production.
Fleact Tec · Islamabad
Built Flutter applications and reusable component libraries, handled API and Firebase integration, and led performance optimisation and bug resolution on existing production builds.
Microprogrammer · Layyah
Delivered Flutter training from scratch and led the mobile team. Owned architecture design, requirement analysis and client communication, ran code reviews, and mentored junior developers through their first production releases.
Freelance · Approx. 6 Months
Native Android development in Java. Android UI, REST API integration, SQLite databases, and the debugging and maintenance work that still informs how the Flutter builds are structured today.
Highlighted items are the ones carrying the most shipped weight. Everything listed has been used in an app that reached a store listing, not just a tutorial.
Same information in a one-page CV, formatted for applicant tracking systems and hiring managers who prefer a file to a browser tab.