CareCloud
This was my first UX role, right after five years as a graphic designer — and I was lucky to join at the start of something ambitious: a full rebuild of a legacy SaaS product from the ground up.
Analytics dashboards — one of the seven core sections of the rebuild.
I started by owning the guarantor center — essentially a patient record, but for the financial and administrative side of care. By the end of my time there, I'd grown into five of the seven core sections: claim remittance, front office, settings, patient portals, and the guarantor center, alongside working with our UI Engineering Lead on a shared component library.
Most days meant sitting with internal stakeholders and multi-million dollar clients to understand where our designs fell short of their actual workflows. At one point, we shadowed users working side by side in a competitor's product just to see the gap for ourselves.
I worked closely with our Head of Product, project managers, and engineering leads — and by the latter half of my time there, I was interviewing, onboarding, and managing timelines for two designers who joined the team.
It was a fast pace — our small team of two produced over 3,000 mocks in a single year — but it also gave me some of the most genuinely complex problems I've worked on.
The scheduler nobody thought could work
The one I'm proudest of is the scheduler, part of the front office workflow. Clinician schedules aren't simple — hard rules on overbooking, custom logic for which visit types could happen at which hours, multiple locations to track, and front office staff who needed to find availability fast, often mid-call with a patient who needed more than one clinician in the room.
There were so many intersecting rules that a lot of people doubted we could make it feel calm instead of chaotic. We did. I still remember the high of watching something that complicated finally click into place for the people using it every day.
if you have one