React JS JD
Exp : 6+
Location : Bengaluru
What You'll Work On
- Micro-frontend platform infrastructure — The host shell, runtime service injection, Web Component integration, cross-app messaging, and navigation orchestration
- Design component library — A dual-delivery component system (React + Lit Web Components) implementing an enterprise design system with WCAG AA compliance
- Platform services — Logging, personalization, RBAC, internationalization, context sharing, and configuration management
- Developer tooling — CLI scaffolding, local sandbox environments, build tooling, and SDK packages that other teams across the org consume
- Backend services — Spring Boot microservices handling personalization, layout, entitlements, and platform configuration (Java/PostgreSQL/Redis/DynamoDB)
What We're Looking For
Technical Foundation
- Strong TypeScript/JavaScript — You'll work across React 19, Lit 3, Vite, Webpack, and Node.js. Understanding the runtime is more important than framework-specific muscle memory.
- React expertise — The platform shell and primary component library are React-first. Hooks, context, portals, concurrent features, and the React 19 event model should feel natural.
- Web Components / Custom Elements — Our integration boundary. You should understand Shadow DOM, custom element lifecycle, attribute/property bridging, and the challenges of embedding frameworks inside custom elements.
- Web platform fundamentals — CSS architecture (tokens, SCSS, Tailwind), accessibility (WCAG AA, aria patterns, keyboard navigation), browser APIs, and performance optimization.
- Backend comfort — Not required to be a backend specialist, but comfort reading and modifying Spring Boot services, understanding REST APIs, JWT auth flows, and database schemas makes you far more effective.
The Mindset We Value More Than Specific Skills
- Systems thinking over feature thinking — You see the ripple effects of a change across a platform used by dozens of teams. You think about the developer consuming your API, not just the end user.
- Willingness to own the full picture — You don't stop at "my component works." You understand how it gets built, deployed, registered, loaded at runtime, and how it behaves in production across different clients.
- AI fluency as a force multiplier — You actively use AI tools (coding assistants, knowledge retrieval, automated testing) not as autocomplete, but as genuine collaborators. You know how to provide context, structure prompts, and validate outputs. You see AI as the mechanism that lets a single engineer operate at an architectural scope.
- Comfort with complexity and ambiguity — Our platform has 16+ repos, dual-owner governance, multiple identity systems in transition, and a component library undergoing incremental migration. You're energized, not paralyzed, by that.
- Bias toward understanding before acting — Read before you write. Understand the existing pattern before introducing a new one. Ask why something is the way it is before assuming it's wrong.
Bonus Points
- Experience with micro-frontend architectures (Module Federation, Web Components as integration boundary, runtime composition)
- Experience building or maintaining shared component libraries consumed by multiple teams
- Familiarity with enterprise concerns: RBAC, SSO integration (SiteMinder, ForgeRock, OIDC), API gateways (Layer 7)
- Infrastructure awareness: Docker, ECS, CloudFront/S3, Terraform, Jenkins pipelines
- Accessibility expertise (axe, NVDA/VoiceOver testing, ARIA authoring practices)
- Experience with Playwright for E2E or component testing
- Background in financial services or regulated industries
How You'll Work
- Feature ownership — You'll regularly pick up entire features, from requirements through deployment. Not just the frontend slice, not just the backend slice — the whole thing.
- AI-augmented workflow — We maintain a structured knowledge base (wf-brain) that gives AI assistants deep platform context. You'll use and contribute to this system. Our development skills include AI-assisted code review, automated ticket triage, evidence-based accessibility reproduction, and AI-driven component porting.
- Collaborative architecture — Weekly design discussions. Everyone contributes to architectural decisions. Seniority determines the scope of what you own, not whether you get a voice.
- Continuous deployment — Merges to develop auto-deploy to internal environments. Multi-phase promotion through QA/UAT/PROD with change records and verification gates.
- Cross-team platform stewardship — You'll support other Broadridge teams building on the platform. Your decisions affect their developer experience.
What You Won't Find Here
- Ticket factories where someone else decided what to build and you just implement it
- Rigid specialization — "I only do frontend" or "I only do backend"
- A codebase where you can ignore the parts you didn't write
- A team that's skeptical of AI or treats it as a novelty
Pay: ₹1,700,000.00 - ₹1,800,000.00 per year
Work Location: In person
