Hi, I'm
Halie.
For most of my career, I've lived in the messy space between a problem and its solution — understanding users, untangling systems, and turning ambiguity into experiences that feel simple. Engineering was always part of that process, but I understood it the way you understand rain through a window — I could see it, respect it, design around it. But I'd never actually stepped outside and felt it.
AI is changing that. So I'm stepping out into the rain — back into IC work, learning to build alongside designing. Not because I want to leave design behind, but because I want fewer boundaries between an idea and what I can make real.
I started in graphic design, drawn to making beautiful imagery. But I couldn't shake the feeling that the work was fleeting.
Once it was seen, it was done. Beauty and trends came and went, and each piece served its purpose once and disappeared.
Then I was hired as a UX designer at CareCloud, and I had no idea what I was doing. I'd been thrown into the deep end of something far more complex than I'd ever touched. Turns out, I was a good swimmer. Healthcare product design didn't feel fleeting — it felt like something I could actually build on, and I fell for it fast.
From there: RBI, Optimize Health, and eventually Medbridge, where I stepped into management — not because I sought it out, but because someone believed I was ready before I did. Three and a half years later, I've got a small, mighty team. And for the last nine months, we've been figuring out what "design engineer" even means — building our own component library, shipping front-end code alongside engineering, closing the gap handoff usually creates.
Which is what brought me back here. Ready to be an IC again, right as this shift is happening.