Material, Kendo, PrimeNG, Storybook, and reusable front-end standards · 2018-present
Design Systems and UI Platform Work
Several roles centered on one thing: turning repeated UI choices into reusable standards. That meant style guides, component rules, Storybook surfaces, review habits, and real design-system work.
Turned repeated UI decisions into reusable standards. That made Angular approachable for back-end-leaning full-stack developers.
Business problem
What needed to be solved
UI consistency rarely fails because a team does not care. It usually fails because every project creates small local answers to the same questions: spacing, states, component boundaries, responsive behavior, styling conventions, and what counts as acceptable front-end code.
Role
My part in the work
UI architect and front-end lead responsible for style guide direction, reusable UI patterns, architectural documentation, component standards, and mentoring developers through front-end best practices.
Approach
How the work moved
I try to make UI standards useful at the moment developers actually need them. That means pairing component libraries with documentation, review habits, code examples, and enough flexibility that the system supports real product work instead of becoming another artifact nobody wants to maintain.
Outcome
What changed afterward
Created more consistent UI development surfaces by pairing design-system tooling with code quality, documentation, review standards, and component-level ownership.
The strongest design-system work made the interface easier to reason about and baked accessibility (WCAG AA) and responsive behavior into the defaults, so teams inherited good practice instead of rediscovering it per project. They had shared language for components, fewer one-off styling decisions, and clearer implementation expectations heading into future Angular upgrades.
Work story
What happened along the way
The Eastdil Secured role stands out because it made the design-system problem explicit. I architected, evangelized, built, and documented a style guide based on Material and Kendo. The goal was front-end work that felt less improvised. More than that, it helped full-stack and back-end developers who were new to Angular.
That same thread shows up elsewhere in the resume through Storybook, Material, PrimeNG, Bootstrap, Tailwind, SASS, responsive design, code reviews, and coding standards. Different tools. Same underlying need.
Supporting details
Places, tools, and repeated patterns.
Where this work happened
Highlights
style guide implementation · component standards · responsive UI systems · front-end best practices
Environment
Angular Material · Kendo UI · PrimeNG · Bootstrap · Tailwind · Storybook · SASS · responsive design
Tools and materials
Angular · Material · Kendo UI · PrimeNG · Storybook · SASS · Bootstrap · Tailwind