Senior UI Engineer
About the Role
We're looking for a Senior UI Engineer who wants to own the frontend end-to-end. You'll be the primary engineer on an Angular 17 application in production today, and the architect of React applications being scoped for tomorrow. This is a hands-on role — you write code every day, you ship features, and you hold the quality bar without needing to be asked.
Key Objectives
Own the frontend. You are accountable for the Angular codebase today and the React applications coming next. You make the architectural calls, you unblock the team, and you care about what ships.
Be hands-on. No abstraction from delivery. You write production code, review PRs, and debug issues in the wild. Senior here means depth of craft, not distance from it.
Deliver with urgency. Working software over completed designs. You have a bias for shipping and a tolerance for iteration. You know how to make pragmatic tradeoffs without cutting the wrong corners. Grow deliberately. The stack will evolve. The AI tooling will evolve. You embrace that — adopting agentic coding tools, learning new frameworks, and pushing the team forward technically.
Major Responsibilities
- Build and maintain production features in the Angular 17 application — standalone components, reactive forms, RxJS, Angular Material, and MSAL/Azure AD authentication
- Architect and deliver React applications as new products are scoped, from initial setup through to production deployment
- Integrate with FastAPI and NestJS backends — REST APIs, server-sent event (SSE) streaming for AI response delivery, and file upload pipelines
- Implement performant, accessible, and responsive UIs that surface AI outputs: streaming chat interfaces, RAG responses, document processing status, and structured data visualization
- Write and maintain unit, component, and integration tests (Karma/Jasmine today; Jest or Vitest in React contexts) — without being asked
- Participate actively in code reviews; articulate the reasoning behind your feedback and hold the team to a high standard
- Instrument UIs with Azure Application Insights; own frontend observability, error tracking, and performance monitoring
- Leverage agentic coding tools — Claude Code, GitHub Copilot, and their successors — as a genuine productivity multiplier, not a novelty
- Collaborate closely with backend engineers, AI/ML platform engineers, designers, and product managers to translate complex AI capabilities into intuitive, trustworthy user experiences
- Contribute to frontend architecture decisions: state management patterns, component design systems, CI/CD pipeline configuration, and dependency management
Qualifications
Qualifications
Required
- 5–7 years of frontend engineering experience in production environments at meaningful scale
- React proficiency — hooks, context, state management libraries (Redux, Zustand, Jotai, or equivalent); comfortable owning a React codebase from first commit to production
- TypeScript — strong typing discipline across both Angular and React contexts; you think in types, not around them
- Async data patterns — REST API integration, SSE streaming, and observable/promise-based data flow; you understand the browser's event model and use it correctly
- Testing discipline — you write unit tests, component tests, and integration tests as part of the work, not after; you know the difference between a test that proves correctness and one that just passes
- HTML, CSS, SCSS fundamentals — semantic markup, responsive layouts, accessible design (WCAG) by default, not as an afterthought
- Git workflow fluency — feature branching, pull request workflows, code review, CI/CD integration; you leave the branch in a better state than you found it
- A track record of shipping — you can point to features running in production, not just repos on GitHub; you know what it takes to get from working locally to working for users
Nice to Have
- Angular 17+ — standalone components, RxJS, Angular Material, router guards — or genuine eagerness to learn it fast; we care more about the quality of your Angular questions than whether you already know the answers
- Azure AD / MSAL — frontend authentication patterns in Azure AD environments, token handling, and silent refresh
- Application Insights — frontend telemetry, custom event tracking, and dependency correlation; knowing what to instrument and why
- AI-adjacent UI experience — consuming LLM APIs, rendering streaming responses, building chat interfaces, markdown rendering, or file upload pipelines that feed into document processing workflows
- Agentic coding assistants — using Claude Code, GitHub Copilot, or similar tools as a daily workflow accelerant; you know how to direct an agent, review its output critically, and integrate it into a disciplined engineering process
- Regulated industry exposure — insurance, finance, or healthcare contexts where data privacy, auditability, and compliance shape engineering decisions
- Open-source contributions — anything that shows you care about the craft beyond the job
Chubb Canada does not use artificial intelligence (AI) tools to assess, screen, or select applicants.
At Chubb we are committed to providing equal employment opportunities to all employees and applicants. It is our policy to provide equal employment opportunities to employees and applicants based on job-related qualifications and ability to perform a job. If you require an accommodation during the hiring process or upon hire, please inform Human Resources. If a selected applicant requests accommodation during the recruitment process, Chubb will consult with the applicant in order to provide suitable accommodation that takes into account the applicant’s accessibility needs.
