Courtney Hoskins

The problem: Engineering was provisioning and tracking internal cloud and on-prem resources through disconnected tools and spreadsheets — nobody had a clear read on spend.

My role: Senior React engineer and UX lead, owning both the research and the product.

Process: Interviewed 20+ teams company-wide, prototyped in Figma, built a "one-stop-shop" React tool that adapted to developers, managers, and finance stakeholders alike.

Outcome: $100K+ in annual savings, plus a component library later adopted by 1,000+ engineers across other internal tools.

The problem: An expensive, slow-to-change vendor tool stood between the team and their own survey data.

My role: Led both UX and front-end rebuild — wireframes, prototypes, and production code, without the usual design-to-dev handoff.

Process: Built visualizations in D3.js against a Shiny/R backend, iterating same-day against real data, focused on making dense statistics legible to non-technical stakeholders.

Outcome: Full replacement of the vendor tool and full internal control over the roadmap.

The problem: AI-assisted features were being bolted onto interfaces designed for a pre-AI world, creating confusion about what the system was doing versus what the user needed to do.

My role: Led UX direction for the redesign — designing for trust, transparency, and control when a system is making suggestions or acting on a user's behalf.

Outcome: A redesigned system built around AI-assisted workflows from the ground up, and a hands-on, practical read on where AI adoption genuinely helps a team — and where it's premature.