Mohannad ElMetwaly

About

I started on the operational side of pharmacy before moving into product. I have worked inside many of the workflows I now specify as software.

As a lead pharmacy technician at CVS (January 2021 – January 2025) I ran intake, processing, verification support, dispensing, fulfillment, insurance, and compliance-sensitive work. That is the domain I now build for.

I joined Epiq Scripts in February 2025 in pharmacy operations, became Product Owner in September 2025, and Associate Product Manager in April 2026. I own product on a healthcare platform for prescriber ordering, client tracking, communication, and pharmacy fulfillment — including APIs that let telehealth organizations integrate instead of working through a manual queue. I lead delivery with approximately 12 full-stack and QA engineers and work directly with COO, CTO, VP of Product, VP of Engineering, and pharmacy operations leadership.

Progression

  1. Lead Pharmacy Technician

    CVS Pharmacy

    January 2021 – January 2025

  2. Pharmacy Operations

    Epiq Scripts LLC

    February 2025 – September 2025

  3. Product Owner

    Epiq Scripts LLC

    September 2025 – April 2026

  4. Associate Product Manager

    Epiq Scripts LLC

    April 2026 – Present

How I decide

  • Start with the workflow, not the feature.

    If the operational path is wrong, the product encodes the wrong work.

  • Automate complexity, not accountability.

    Remove friction around licensed work. Do not replace pharmacist judgment.

  • The exception path is the product.

    Insurance failures, controlled substances, fulfillment errors, and API faults are not edge cases in pharmacy.

  • AI has to earn the workflow.

    I use AI in daily PM work. Production AI in pharmacy requires auditability, human approval, and a reason rules cannot do the job.