🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
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 interfacesDefine 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 UIEstablish contribution standards - how squads propose new components, how variants are reviewed, and how the component library evolves without becoming inconsistentBuild 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 outImplement 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 CSSDefine 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 featureBuild 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 standardsEstablish 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 shipsOwn the frontend Guild - fortnightly sessions on React patterns, accessibility, performance optimisation, and AI-assisted frontend development for all Frontend Engineers across the organisationReview frontend architecture decisions across squadsMentor Frontend Engineers at Intermediate level - structured development toward ownership of component domains and cross-squad frontend confidence RequirementsProfessional Experience 5 to 8 years in frontend engineering with ownership of a design system or component library in production - not just consuming one, but building and maintaining itHas built UI for mobile-first, low-bandwidth environments - understands performance budgets, lazy loading, and the difference between a UI that works in Pune and one that works in a village with 3GHas made design decisions in the absence of a dedicated designer - comfortable with design tools, AI design systems, and the judgment to know when something looks rightActive AI tool user - uses Claude or equivalent for UI generation and design exploration today; Cursor is standard development tooling Mindset & Soft Skills Design ownership means the Senior FE takes responsibility for design quality - you fill the gap with AI tools and design judgment, not with lowered standardsLibrary steward: Component library steward: a component library is a product - it needs documentation, contribution guidelines, and a maintainer who cares about developer experienceRural UX empathy: SarvaGram's Custom .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.