M
Director, Frontend Engineering
M
Director, Frontend Engineering
magnet hr tech digital15-17 Years
- Posted 15 hours ago
- Be among the first 10 applicants
Job Description
We are seeking a Director of Front-End Engineering to lead one of the Experience domain groups — the federated, module-federation architecture behind bell.ca (the shell, its micro-frontends, and the shared design system and tooling that support them). This is not a staffing or execution role: we are looking for a true engineering partner who takes complete, end-to-end ownership of a business outcome and is accountable for how it is delivered, not just that it is delivered. You will own one or two Experience domains (for example Checkout or Solution Builder) across the program's West, Atlantic, and Central phases, build and run a self-sufficient pod, set the hiring bar for your organization, and represent India as a full partner to the Canada-based Experience leadership with the standing and judgment to disagree, be heard, and then commit.
Leadership & Management Skills
Leadership & Management Skills
- Outcome Ownership: Proven ability to take complete ownership of a business outcome end-to-end — understanding the target, debating the technical approach and trade-offs, and once a decision is made, committing to it and being accountable for its delivery, quality, and long-term shelf life in production.
- Hiring Accountability: Full accountability for interviewing, vetting, and hiring top engineering talent for your pod(s) — you are personally responsible for the quality of the team you build and the delivery that results from it.
- Pod & Delivery Leadership: Ability to stand up and run a pod (or pod of pods) that owns a domain end-to-end: onboarding engineers, running delivery governance that is lightweight rather than bureaucratic, and escalating only the blockers that genuinely need to be bubbled up.
- Cross-Geo Partnership: Comfort operating as an extension of the Canada-based team rather than a downstream vendor — attending daily stand-ups, building direct working relationships with Salesforce, integration, and SRE counterparts, and knowing who to call when something crosses a domain boundary.
- Architectural Voice: A mandate to bring architectural authority to the table: thought leaders on this team work with delivery so that what is proposed is what actually ships and holds up in production, rather than designs that drift once handed off.
- Culture Building: A servant-leader who protects a culture of innovation, delivery, and fun, and who actively resists unnecessary process — the goal is a lean, fast, and simple way of working, not adding heavyweight reporting because that's how it's always been done.
- Talent Magnetism: Ability to attract and retain talent that can compete with Bangalore's startup market — engineers who bring modern technical curiosity and creative problem-solving, not only integration/operations profiles.
- Module Federation / Micro-Frontend Architecture: Deep working knowledge of federated front-end architecture: a shared shell (navigation, session, layout, analytics) plus independently owned and deployed micro-frontends (MFEs), each mapped to a single business domain (e.g., Qualification, Product Catalog, Checkout, Billing, Customer Profile).
- Stack Fluency: Comfort overseeing modern front-end stacks — React 19, TanStack Router/Query, a shared design system (Brand UI and Product UI), and standardized build/test tooling (Rspack, Vitest browser-mode testing, visual regression) — even without writing the code personally day to day.
- Engineering Standards & CI/CD: Understanding of how Guardrails-over-gatekeeping pipelines work (linting, TypeScript, security scanning, live review environments) so standards are enforced by tooling, not by adding process.
- Integration & Systems Thinking: Awareness of how the front end integrates with Salesforce, MuleSoft, and other backend/API layers — enough to debate translation and integration approaches with an architectural and cost lens, and to know when a workaround belongs in the API layer rather than the front end.
- AI-Assisted Delivery: Experience championing AI-assisted SDLC — planning agents, delivery agents, and AI-assisted testing — to help developers ship faster and with fewer defects.
- Observability & Production Readiness: Familiarity with observability and AIOps practices (proactive/reactive tiering, telemetry pipelines, tools such as New Relic and Dynatrace) so your domain's production health is visible and defensible.
- Systems Thinking: Ability to look across your domain(s) and adjacent ones to spot reuse opportunities, reduce tech debt, and avoid rebuilding what already exists in the shared platform.
- 15+ years of software engineering experience, including 5+ years in a senior leadership role (Director or equivalent) owning delivery for teams of 50+ engineers.
- Demonstrated success building and scaling teams in a GCC, global capability center, or global delivery model — ideally one that has moved from staff augmentation to outcome ownership.
- Hands-on or recent front-end engineering background (React or comparable modern framework); experience with micro-frontend or federated architectures is a strong plus.
- Experience in telecommunications or large-scale digital/retail platforms is a strong plus.
- A track record of building trust with distributed stakeholders and operating with autonomy rather than waiting to be told what to do.
More Info
Key Skills
CI CD
Rspack
AI-Assisted Delivery
React 19
Module Federation Micro-Frontend Architecture
TanStack Router Query
Vitest





