BabakRahimi
I build frontend systems that stay clear as products grow: component libraries, design systems, and the interaction details around them.
- Working on frontend architecture and design systems in Berlin, with a growing interest in AI-assisted interfaces and tools for development teams.
- Aug 2026
01
Approach
-
readable > clever
Most code is read more than it is written. I optimise for the next person who has to understand it.
-
composable, documented, tested
Reusable means easy to find, understand, test, and change. Documentation and tests are part of the component.
-
measured, not assumed
Profile first. Performance discussions get much more useful once there is data.
-
mentorship over gatekeeping
Knowing a codebase well should make it easier for other people to contribute to it.
02
Instruments
Tools change. These are the ones I reach for most often.
- Foundation
- React · Next.js · TypeScript
- Interface systems
- Tailwind · Radix · shadcn/ui · Storybook
- Application state
- TanStack Query · React Hook Form · Zod
- Delivery & quality
- Jest · React Testing Library · Cypress · GitHub Actions
03
Contact
Email is best. I'm usually interested in conversations about frontend architecture, design systems, interface quality, and tools for developers.