Adella is hiring a Design Engineer for a 12-week project: build the React and TypeScript component library behind 46 B2B SaaS apps, built once and imported everywhere. This is for engineers who have built and owned a component library, not website or template builders.

About Adella

Adella is a US software company. Our product is business intelligence that acts: 46 marketing and business apps in five families, on one platform with one login. Our users are businesses and agencies that spend on Google, Meta, Amazon and Shopify, and each morning Adella tells them what is costing money and what to change. Our apps are built in parallel by AI coding agents, one lane per app, with every change reviewed by our CTO.

Why this project matters

If shared components exist only in Figma, every AI-built lane builds its own version and 46 apps drift apart. One component library, published as a package every lane imports, keeps all 46 consistent, accessible and quick. You build that library, and you make it hard for any lane to do anything else.

The project

Phase 1 (about 12 weeks, fixed fee paid by milestone):

- Publish a versioned React and TypeScript component library that every app lane imports.
- Build a tokens pipeline from the designer's Figma variables to CSS custom properties.
- Build the shared components: finding card, evidence panel, approval control with tiers, revert control, state strip, connection health strip, data table, chart wrappers, form controls, and every empty, error and stale state.
- Build the suite shell: navigation across 46 apps, account switcher and client scope for agencies, settings and notifications, running beside our existing React app.
- Make Storybook the single reference, with every component in every state,



documented for both people and AI coding agents.
- Add guardrails: lint rules, types that block misuse (a dollar value that cannot render without its state), visual regression tests and accessibility checks in CI.
- Render the same finding to email and Slack.

Phase 2, offered if Phase 1 meets the bar: support the first six app lanes, review their UI pull requests with our CTO, and extend the library as they need it. After either phase, we may offer a full-time role owning the library for all 46 apps.

What you bring

- 5 to 9 years of front-end engineering, with 2+ years building or owning a shared component library used by several teams or products.
- Expert React and TypeScript: strict typing, generics, discriminated unions, typed component APIs. You can show code.
- A library you published as a versioned package, documented in Storybook or similar, with breaking changes handled through deprecation and migration. Using MUI, Chakra or Ant Design alone does not count.
- Strong CSS: grid, flexbox, container queries, theming with custom properties, and a tokens pipeline such as Style Dictionary or Tokens Studio.
- Accessibility in code: semantic HTML, correct ARIA, focus management, keyboard operation, testing with axe and a screen reader, and WCAG 2.2 criteria you have met.
- Testing: Vitest or Jest with Testing Library, visual regression (Chromatic, Playwright or Percy),



and accessibility checks in CI.
- Data-dense interfaces: large virtualized tables, charts, and number and currency formatting with Intl.
- Fluent with Figma, and willing to push back on designs that cannot be built well.
- Daily use of AI coding tools such as Claude Code, Cursor or Copilot, and an understanding of how to make a codebase easy for an agent to use correctly.
- Clear written English for documentation and pull requests.

Nice to have

- Shipped B2B SaaS front ends in analytics, ad tech, martech or fintech.
- Monorepo tooling (pnpm workspaces, Turborepo or Nx).
- React Email, MJML or Slack Block Kit.
- A new shell embedded beside a legacy React app, or microfrontends.
- Performance budgets and Core Web Vitals.
- Open-source contributions to component or accessibility projects.

Our stack

React, TypeScript, Storybook, Vitest, Testing Library, Playwright, Node 22, Figma and Claude Code, with a PHP back end for the existing product.

How we work

Remote from anywhere in India, full time effort for the project, with at least three hours a day of overlap with US Central time (about 7:30 PM to 10:30 PM IST). A small senior team: you work directly with the CTO and our Lead Product Designer. Shared contracts change on a weekly cadence. A competitive fixed project fee, paid as each of four milestones is approved.

The process

1. Technical screen (45 minutes).
2. Paid take-home (6 to 8 hours).
3. Code review and pairing with the CTO (75 minutes).
4. Final conversation with the founder.

How to apply

Apply on LinkedIn with your GitHub profile or code samples, plus a link to any component library or Storybook you built or owned. Applications without code are not reviewed.

📌 Design Engineer, React and Design SystemsB SaaS, Project) (India)
🏢 Adella
📍 India