Posted last month
Technical Lead - Full Stack
@ CGI
Toronto, Ontario
SIGNALS
Overview
CGI is hiring a Technical Lead to raise engineering quality across five Agile pods delivering for a major banking client. The role is hands-on technical leadership covering code quality, architecture, mentorship, and cross-pod reuse, alongside Scrum Masters who own delivery process. The posting requires hybrid work with at least 2 days per week in the downtown Toronto or client office.
Responsibilities:
- Set code quality and design standards across five Agile pods
- Mentor Dev Leads and developers, onshore and offshore
- Own architecture decisions and reference patterns
- Resolve design conflicts, integration issues and tooling gaps
- Champion GitHub Copilot and other AI-assisted development tools
Requirements summary:
- Hands-on full-stack experience with Angular, Node.js, Spring Boot and AWS Lambda
- Experience leading technical decisions across multiple teams
- Strong code review and software craftsmanship practice
- Experience with Agile delivery environments
Tools & skills
Source and dates
Source type not verified · njoyn
- Employer posting date
- 2026-09-26
- First seen by our source
- 2026-10-17
- Source record updated
- 2026-10-17
These dates describe the source record, not a live verification that the employer is still hiring. Check the original posting.
Job details
| Seniority | Lead |
| Department | Software development |
| Hours per week | 40 (estimated) |
| Travel | air: none · ground: none |
| Work setting | Office |
| Position | Mostly sitting |
| Physical demands | physical low · computer high |
| Languages | English |
Summary and details written by AI from the posting; the employer’s posting is the authority.
CGI
| Field | Value |
|---|---|
| Company size | 10001+ |
| Headquarters | E-Commerce Place |
| Open jobs on Jobsy | 514 |
Job description
This role is hybrid and requires you to be at our downtown Toronto and/or Client office at a minimum 2 days per week subject to change at any time.
About the Role
CGI's Financial Services team is looking for a Technical Lead to raise the engineering bar across five Agile pods delivering for a major banking client. Each pod already runs with strong process discipline under a dedicated Scrum Master — what's missing is a single technical owner accountable for code quality, architecture consistency, and cross pod reuse. This is a hands on technical leadership role, not a delivery management role: you'll spend your time on code, architecture, and mentorship, partnering with — not duplicating — the Scrum Masters who own planning, ceremonies, and velocity.
What You'll Own
• Quality: Raise the engineering bar across all 5 pods — code quality, design consistency, and technical craftsmanship, measured through real metrics, not assumed.
• Mentorship: Build the Dev Leads into strong technical decision makers rather than solving every problem yourself — multiply, don't do.
• Collaboration: Turn 5 pods working in isolation into one engineering organization — shared components, shared patterns, shared learning.
• AI enabled engineering: Champion GitHub Copilot and other AI assisted development tools to lift developer productivity and code quality across the pods, and coach teams on how to use them well.
• Unblocking: Be the escalation point that unblocks design conflicts, integration issues, and tooling gaps before they become delivery risks.
How This Role Is Different From a Scrum Master
This is a technical authority role, not a delivery process role — the two are designed to complement each other, not overlap.
Tech Lead owns Scrum Master owns (unchanged)
Code quality, standards, and review rigor across all pods Sprint planning, backlog grooming facilitation
Architecture decisions and reference patterns (Angular / Node.js / Spring Boot / AWS Lambda) Velocity tracking and predictability
Technical impediment resolution (design conflicts, integration blockers, tooling gaps) Ceremonies: standups, retros, sprint reviews
Mentorship of Dev Leads and Developers (onshore + offshore) Team level health reporting to engineering leadership
Cross pod technical collaboration and reuse (shared components, APIs, libraries) Scope, capacity, and commitment management with PO
Technical risk escalation to engineering leadership Individual performance management
About the Role
CGI's Financial Services team is looking for a Technical Lead to raise the engineering bar across five Agile pods delivering for a major banking client. Each pod already runs with strong process discipline under a dedicated Scrum Master — what's missing is a single technical owner accountable for code quality, architecture consistency, and cross pod reuse. This is a hands on technical leadership role, not a delivery management role: you'll spend your time on code, architecture, and mentorship, partnering with — not duplicating — the Scrum Masters who own planning, ceremonies, and velocity.
What You'll Own
• Quality: Raise the engineering bar across all 5 pods — code quality, design consistency, and technical craftsmanship, measured through real metrics, not assumed.
• Mentorship: Build the Dev Leads into strong technical decision makers rather than solving every problem yourself — multiply, don't do.
• Collaboration: Turn 5 pods working in isolation into one engineering organization — shared components, shared patterns, shared learning.
• AI enabled engineering: Champion GitHub Copilot and other AI assisted development tools to lift developer productivity and code quality across the pods, and coach teams on how to use them well.
• Unblocking: Be the escalation point that unblocks design conflicts, integration issues, and tooling gaps before they become delivery risks.
How This Role Is Different From a Scrum Master
This is a technical authority role, not a delivery process role — the two are designed to complement each other, not overlap.
Tech Lead owns Scrum Master owns (unchanged)
Code quality, standards, and review rigor across all pods Sprint planning, backlog grooming facilitation
Architecture decisions and reference patterns (Angular / Node.js / Spring Boot / AWS Lambda) Velocity tracking and predictability
Technical impediment resolution (design conflicts, integration blockers, tooling gaps) Ceremonies: standups, retros, sprint reviews
Mentorship of Dev Leads and Developers (onshore + offshore) Team level health reporting to engineering leadership
Cross pod technical collaboration and reuse (shared components, APIs, libraries) Scope, capacity, and commitment management with PO
Technical risk escalation to engineering leadership Individual performance management
Journal
Only you can see this. Kept on this device, and in your account when you sign in.