Fintech B2B SaaS — Shared UI, Testing, and Async Frontend Delivery
Frontend work on a core fintech SaaS product, covering UI components, shared UI improvements, Storybook-based design consistency, and test implementation within an async international setup.
Period: Apr 2022 – Mar 2023
Overview
Frontend work on a core fintech SaaS product within a large distributed team, covering UI implementation, shared component improvements, UI testing, and async collaboration. The value of the work was not only in shipping features, but also in helping maintain consistency and implementation quality across ongoing product development.
Context
This was part of an established B2B SaaS product where frontend work happened inside a large Romania-based team with more than 20 frontend engineers. The work sat within ongoing product delivery rather than a one-off redesign, so consistency, maintainability, and review quality mattered alongside feature implementation.
Challenge
The key challenge was to support ongoing delivery while keeping shared UI patterns, implementation quality, and team coordination stable across a distributed async setup.
- Keep UI patterns more consistent across multiple product areas
- Support shared component usage and frontend maintainability over time
- Add testing and review practices that reduce implementation risk
- Work effectively in a distributed async environment across regions
Contribution
Ongoing UI Delivery
- Implemented and maintained frontend components within the core product
- Worked inside an existing codebase where delivery had to stay practical and consistent over time
Shared UI Improvement
- Supported improvements to a Storybook-based shared component library
- Helped strengthen reusable frontend patterns across product surfaces
Testing & Review
- Added UI tests using Jest, RTL, and Cypress
- Participated in code review and spec confirmation to reduce ambiguity and implementation drift
Async Team Collaboration
- Worked with a large distributed frontend team across regions
- Contributed in an async workflow where clarity and consistency were important to delivery quality
What This Case Shows
- Experience supporting an established SaaS product through shared UI work, testing, and ongoing frontend delivery
- Ability to contribute not only through implementation, but through maintainability, consistency, and review quality
- Comfort working in distributed async teams where frontend work depends on coordination as much as code
Notes
- This case is less about a single visible launch and more about the kind of frontend support that helps a team keep moving without losing consistency
- It is particularly relevant to ongoing product support, shared UI improvement, and implementation-aware frontend partnering