About the role

The Senior Frontend Engineer owns the component library and design system that every customer -facing and internal interface is built from. You define the frontend engineering standards. You make design decisions - using Claude Design and AI tools as your primary design instrument - that keep SarvaGram's product coherent without requiring a dedicated designer on every squad.

This is a rare combination: strong technical engineering depth (React, performance, accessibility, testing) and the design sensibility to maintain a system that non -designers can use confidently. If you have spent your career building products where UI quality mattered and you understand what a well -maintained component library does for an engineering organisation, this role was designed for you.

Key Responsibilities

Component Library & Design System

• Own and evolve SarvaGram's component library - the React components, design tokens, and UI patterns that every squad uses to build consistent, accessible interfaces

• Define and maintain the design system - colour tokens, typography scales, spacing standards, icon library, and the documentation that allows engineers to use the system without design review for standard UI

• Establish contribution standards - how squads propose current components, how variants are reviewed, and how the component library evolves without becoming inconsistent

• Build and maintain Storybook - the component documentation site that engineers use to discover components, understand their props, and see their states without building the UI to find out

• Implement design token infrastructure - CSS variables or a token system that allows theming, brand updates, and white -labelling without rewriting component styles

Business Platforms - React / Flutter Web

• Own the technical architecture of the Business Platforms frontend - routing, state management, API integration patterns, performance budgets.

• Implement performance -first frontend engineering - lazy loading, code splitting, image optimisation, and offline -first patterns that make the mobile -native web apps usable on 2G/3G connections

AI -Native Design & Tooling

• Use Claude Design as the primary design tool - generate UI component designs, layout options, and visual specifications using AI tools; iterate with Claude before writing a line of CSS

• Define the AI -assisted UI workflow - how product engineers use Claude to generate UI that conforms to the design system without requiring Senior FE review for every small feature

• Build the internal UI tooling layer in AppSmith - working with Automation Team to create self -service dashboards for Operations and Support that match SarvaGram's UI standards

• Establish frontend AI tooling standards - how Cursor is configured for React development, what Claude prompts generate reliable component code, and the quality bar for AI -generated UI

Frontend Standards & Cross -Squad Authority

• Define and enforce frontend engineering standards across all squads - the technology choices, code patterns, and quality gates that apply to every frontend surface SarvaGram ships

• Own the frontend Guild - fortnightly sessions on React patterns, accessibility, performance optimisation, and AI -assisted frontend development for all Frontend Engineers across the organisation

• Review frontend architecture decisions across squads

• Mentor Frontend Engineers at Intermediate level - structured development toward ownership of component domains and cross -squad frontend confidence