← All companies

Scheduling Wizard

Active

Logistics infrastructure to modernize healthcare operations

W26·Winter 2026·Healthcare·Team of 3·Founded 2024

About

Scheduling Wizard is building the logistics infrastructure to modernize healthcare operations. Hospitals still rely on manual workflows to manage staffing, patient flow, and core operations, contributing to $760B in annual inefficiency. 20 departments across 16 hospitals already outsource their physician scheduling to us, powered by our internal Scheduling Programming Language and AI-driven workflows. We work with Mass General, Johns Hopkins, UT Southwestern, UCSF, and many others. We are actively onboarding new clients and expanding into patient triaging and provider management systems, working with partner departments at UCSF and other leading institutions. Scheduling Wizard aims to bring healthcare operations into the future by reducing administrative burden and improving clinical care coordination. Our goal is to create the AI-native administrative layer in healthcare operations.

Founders

  • Samuel Oberly· Founder

    Johns Hopkins and Cambridge trained Mathematician. Building the algorithms that will drive the future of healthcare administration and resource allocation. I am an award-winning and published mathematician, including a civilian service medal for my logistics algorithms built while working for the Department of Defense. I received four degrees in my four years at Johns Hopkins and have deep expertise in algorithm development.

  • Zachary Dermody· Founder

    Co-Founder and COO of Scheduling Wizard. Johns Hopkins University, 2024. B.A. in Economics with a minor in Computer Science. Former logistics roles at Amazon and McMaster-Carr. Interested in technology, philosophy, and building the future.

  • Abdelrahman Hamimi· Founder

    Co-Founder & CTO of Scheduling Wizard | MS, BS Computer science and BA Economics from Johns Hopkins University (2025) | AWS Cloud Solutions Architect Certified

Product launches · 1 launch

Change history · none recorded

No changes recorded yet. Subsequent syncs will populate this timeline as fields drift.