Senior Backend Engineer

Qualifications

• REQUIRED QUALIFICATIONS
• 5–7 years of professional backend engineering experience delivering production services at meaningful scale
• TypeScript — rigorous typing discipline in a Node.js backend context; you think in types and leverage the type of system rather than work around it
• NestJS or equivalent Node.js backend framework (Express, Fastify) — experience designing feature modules, middleware, guards, interceptors, and RESTful API architecture
• Python — comfortable authoring production-grade services with Pydantic data models and async/await patterns; you write clean Python and know when something is good enough versus when it needs to be better
• Azure ecosystem — practical experience with managed identity (DefaultAzureCredential), Key Vault, Cosmos DB, Blob Storage, and Application Insights; secrets are never hardcoded
• Testing discipline — writes unit, integration, and e2e tests as an intrinsic part of delivery, not a post-hoc checkbox; knows the difference between a test that proves correctness and one that just passes
• Observability fundamentals — structured logging, distributed tracing, and error tracking in a cloud-hosted service; you know what to instrument and why
• Git workflow fluency — feature branching, pull request workflows, code review participation, and CI/CD integration; you leave the codebase in a better state than you found it
• Proven delivery track record — demonstrable history of shipping features into production environments on schedule, sprint over sprint
• NICE TO HAVE
• Azure AI Search, Azure OpenAI, or RAG architecture — hands-on experience with vector search, embedding pipelines, or LLM integrations in production
• OpenTelemetry instrumentation — distributed tracing across polyglot service boundaries, especially Python and Node.js in the same trace
• Agentic coding assistants — Claude Code, GitHub Copilot, or equivalent tools used as a genuine workflow accelerant; you know how to direct an agent, review its output critically, and integrate it into a disciplined engineering process
• Document processing pipelines — OCR, PDF/DOCX parsing, text chunking strategies, or file ingestion workflows at scale
• Regulated industry exposure — insurance, financial services, or healthcare environments where data privacy, auditability, and compliance shape engineering decisions
• Angular or React familiarity — enough to read frontend code, understand API consumption patterns, and collaborate on contract design without handholding from the UI team
• Open-source contributions — anything that demonstrates 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.
• REQUIRED QUALIFICATIONS • 5–7 years of professional backend engineering experience delivering production services at meaningful scale • TypeScript — rigorous typing discipline in a Node.js backend context; you think in types and leverage the type of system rather than work around it • NestJS or equivalent Node.js backend framework (Express, Fastify) — experience designing feature modules, middleware, guards, interceptors, and RESTful API architecture • Python — comfortable authoring production-grade services with Pydantic data models and async/await patterns; you write clean Python and know when something is good enough versus when it needs to be better • Azure ecosystem — practical experience with managed identity (DefaultAzureCredential), Key Vault, Cosmos DB, Blob Storage, and Application Insights; secrets are never hardcoded • Testing discipline — writes unit, integration, and e2e tests as an intrinsic part of delivery, not a post-hoc checkbox; knows the difference between a test that proves correctness and one that just passes • Observability fundamentals — structured logging, distributed tracing, and error tracking in a cloud-hosted service; you know what to instrument and why • Git workflow fluency — feature branching, pull request workflows, code review participation, and CI/CD integration; you leave the codebase in a better state than you found it • Proven delivery track record — demonstrable history of shipping features into production environments on schedule, sprint over sprint NICE TO HAVE • Azure AI Search, Azure OpenAI, or RAG architecture — hands-on experience with vector search, embedding pipelines, or LLM integrations in production • OpenTelemetry instrumentation — distributed tracing across polyglot service boundaries, especially Python and Node.js in the same trace • Agentic coding assistants — Claude Code, GitHub Copilot, or equivalent tools used as a genuine workflow accelerant; you know how to direct an agent, review its output critically, and integrate it into a disciplined engineering process • Document processing pipelines — OCR, PDF/DOCX parsing, text chunking strategies, or file ingestion workflows at scale • Regulated industry exposure — insurance, financial services, or healthcare environments where data privacy, auditability, and compliance shape engineering decisions • Angular or React familiarity — enough to read frontend code, understand API consumption patterns, and collaborate on contract design without handholding from the UI team • Open-source contributions — anything that demonstrates 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.