Case study · 2025
ClarityTx
Defining the first front-end and interaction model for a clinical monograph search product while its requirements were still taking shape.

- Role
- Founding Front-end Engineer
- Status
- Initial foundation delivered
- Year
- 2025
Problem
The product started with evolving stakeholder ideas rather than a fixed specification. The challenge was to turn those requests into a clear clinical search experience, with defined workflows, screen states, and an information structure that could present dense medical content in a usable way.
Primary audience
Healthcare practitioners searching structured monographs for clinical reference information
Constraints
The project had no dedicated business analyst, requirements continued to evolve, and some supporting assets were still in progress. This meant product decisions often had to be clarified and structured alongside implementation. My involvement covered the initial product phase before development transitioned to another agency team.
Validation
Proposed workflows and interface decisions were reviewed directly with stakeholders throughout the initial build and refined based on their feedback. There was no formal end-user research phase during my involvement, so I avoid presenting the work as user-validated beyond stakeholder review.
Outcome
The work turned an ambiguous concept into an implemented front-end foundation and documented interaction model that a subsequent agency team could continue.
My contribution
I helped shape the product from early requirements through working UI. I established the Angular front-end architecture, selected the foundational libraries and design system, designed key workflows and reusable components in Figma, and implemented the initial production interface. I also worked directly with stakeholders to clarify changing requirements, define expected product behavior, and translate ideas into practical flows the development team could build against. The senior back-end engineer owned the API, Algolia integration, and search-data behavior, while I focused on the product experience and front-end implementation.
Scope
- Website
- Web Application
- Product Design
Stack
- Angular
- TypeScript
- Tailwind CSS
- Node.js
- Figma
- Adobe Photoshop
- Adobe Illustrator