Sr. Software Engineer - 57596

Duration: 12 months

Extension possible: Yes

Conversion Possible: Yes possible

Work Location: Hybrid 2 days a week - but will be transition to 4 days eventually, Toronto, Ontario

Interview process: 2 rounds - 1st round will be managerial and some technologic (VIRTUAL) - second interview will be all technology based questions (IN PERSON)

Team Size/Culture: 7-8 member

Selling Points of Position (CVP): will have exposure to advanced technology. Team is collaborative.

As a Senior Software Engineer in the onboarding and compliancy team in business banking, you will contribute to the delivery and support of OBNC capabilities by owning engineering work across analysis, development, defect resolution, and operational improvements. You will operate within the pod’s delivery cadence and collaborate with cross‑pod partners to manage dependencies, deliver prioritized work, and maintain stable outcomes.

Key Responsibilities

• Deliver engineering work within the Pod scope: implement fixes, enhancements, and technical improvements aligned to prioritized backlog items
• Participate in pod operating rhythm (e.g., Daily Huddle, technical calls) to coordinate work, manage blockers, and communicate progress
• Perform triage and root‑cause analysis for issues/defects; implement corrective changes and support validation through testing and controlled releases
• Collaborate with other OBNC pods and stakeholders (e.g., cross‑pod huddles) to align on dependencies, sequencing, and handoffs.
• Maintain strong delivery hygiene: code reviews, documentation, operational readiness, and transparent tracking in work management tools (e.g., Jira epics/stories).
• Contribute to transition/continuity activities as work moves between pods (noted in OBNC delivery updates).

MUST-HAVE Hard Skills:

1.) Jira and GitHub - 7 years

2.) Strong communication skills

3.) Strong technical skills - azure, cloud native knowledge, Advanced Java, angular, MMSQL -Spring Boot - 7 years

4.) Coding Design pattern -5 years

NICE-TO-HAVE

1.) Cloud architecture

2.) AI capabilities - (copilot)

3.) Previous banking domain experience

4.) Kafka