Ahmed Mostafa · Product Owner & Product Manager · PSPO™ II write requirements that survive an audit.
Product Owner at Areeb Technology, unifying 2 legal and financial investment systems into one regulated fintech platform across 6 delivery squads. Engineer first: Electronics and Communications, then hands-on software testing. That is why feasibility arguments don't get past me. Open to Product Owner / Product Manager roles.
What I'm focused on
- BuildingOwning fintech and enterprise SaaS products end to end as Product Owner at Areeb Technology: approval flows, transaction logic, and operational dashboards.
- ExploringHow AI-native workflows change the way products get specced and built. I'm prototyping my own concept, Productology, a workspace for PMs.
- LearningGoing deeper on multi-tenant SaaS architecture and pricing design: tenant isolation, access control, and modular packaging.
- Open toFull-time Product Owner / Product Manager roles and select freelance PRD engagements. Cairo-based, remote-friendly, willing to relocate.
The Backlog Contract
A backlog item is not a task. It's an agreement, and every agreement has counterparties. Rework is what happens when one of them never signed.
Compliance
Signs off on: can this be audited after it ships? Their signature lives in the acceptance criteria, not in a meeting.
Engineering
Signs off on: is this buildable exactly as written, with no "TBD in design"? A spec that hides the edge cases produces an estimate that is fiction.
The business
Signs off on: is this worth the sprint it costs? A story nobody will defend at review was never worth writing.
Silence isn't a signature. A story with no objection from compliance is not an approved story. It's an unread one. Nearly every change request I've received traced back to a counterparty who was never asked.
Read the full argument →Strategy meets compliance
My Journey
I started in Electronics & Communications Engineering, building things like FleetX, a Smart Fleet Management System supported by ITIDA and ASRT. Agile training, hands-on software testing, and a Scrum Product Owner certification followed, and that's the foundation I brought into product, where I now turn fintech and investment workflows into shippable features for a live enterprise SaaS platform. Alongside that, I founded and led CIC's Google Developer Student Club (Top 50 globally, Top 20 MENA at the Google Solution Challenge) and coordinated IEEE and Google Developer Group programs, community leadership that's run in parallel with the delivery work the whole time.
How I work
I write specs to be handed to an engineer with no meeting attached. That means the failure paths get more pages than the happy path, acceptance criteria name the API version they were written against, and every "handle this gracefully" gets replaced with the actual behaviour before the document leaves my hands. The point isn't documentation. It's that nobody has to guess.
Requirements & Compliance
I translate legal and financial complexity into user stories and acceptance criteria that hold up under regulatory review.
Cross-Functional Alignment
I keep legal, compliance, delivery, and operations moving together through BRDs, PRDs, and disciplined Agile ceremonies.
End-to-End Delivery
From requirements definition through UAT and rollout, running Scrum and Nexus in practice to keep delivery predictable.
Engineer's Depth
An Electronics & Communications Engineering background plus hands-on software testing means I can pressure-test feasibility early.