We're looking for a React Native developer to join our team building a shared component library that powers multiple products built on top of a design system. The work is the opposite of typical app development: instead of shipping features for end users, you'll be designing and maintaining components that other developers consume to build their applications.
The project is API-design heavy and quality-sensitive. Every prop you add, every default you choose, and every breaking change you introduce affects multiple downstream teams. You'll work closely with designers (who own the design system) and consumer teams (who build products with your components), and you'll be expected to translate design intent into stable, well-documented, accessible components that work consistently across iOS and Android.
Our future colleague should care more about getting the API right than getting it shipped fast. We value engineers who can argue confidently for less code, who treat documentation as a deliverable, and who understand that a library's job is to make the right thing easy and the wrong thing hard.
If you've ever maintained internal tooling, contributed to a UI library, or simply enjoy the discipline of designing interfaces other people depend on, we'd love to talk to you.
Responsibilities
- Design, build, and maintain reusable React Native components in TypeScript that follow our design system specifications.
- Translate design tokens (color, spacing, typography, motion) into a typed, themeable component API.
- Define and review component APIs with a consumer-first mindset: minimal props, sensible defaults, predictable composition.
- Ensure cross-platform consistency on iOS and Android, including accessibility (screen readers, dynamic type, RTL) and theming (light/dark, brand variants).
- Write and maintain Storybook entries, usage examples, and migration guides for every component.
- Manage versioning and breaking changes responsibly: semver discipline, deprecation paths, codemods when needed.
- Collaborate with designers when a design conflicts with the system, and propose alternatives that preserve consistency.
- Support consumer teams by triaging issues, answering API questions, and improving DX based on real usage patterns.
Knowledge and skills
- Strong, hands-on experience with React Native and TypeScript on production codebases.
- Solid understanding of component API design: compound components, controlled vs. uncontrolled patterns, ref forwarding, polymorphic components.
- Experience working with or building a design system (tokens, theming, variants), not just consuming UI kits.
- Ability to distinguish "what the design shows" from "what the system requires" and push back constructively when they conflict.
- Comfortable with cross-platform constraints on iOS and Android: SafeArea, gesture handling, platform-specific styling, native module quirks.
- Performance awareness for component-level concerns: memoization, list virtualization (FlatList/FlashList), image caching, re-render minimization.
- Accessibility experience beyond
accessibilityLabel: roles, focus management, dynamic type, RTL, screen reader testing.
- Familiarity with Storybook for React Native or equivalent component documentation tools.
- Understanding of semver and the discipline of breaking changes: when to deprecate, when to break, how to communicate.
- Strong communication skills for working with designers, reviewing PRs from consumer teams, and writing documentation that doesn't get ignored.
- Comfortable working in a code-review-heavy environment where API decisions are negotiated, not declared.
- Great English level (B2+).
Nice to Have
- Prior experience contributing to or maintaining a public or internal component library.
- Familiarity with React Native New Architecture (Fabric, TurboModules) and modern animation tools (Reanimated, Gesture Handler).
- Experience writing codemods or migration scripts for breaking changes in shared code.
