1

Temporary Tcs Software Engineer Jobs in Toronto, ON

Software Engineer III

Toronto, ON · On-site

CA$125K - CA$154K/yr

... temporary market premium specific to this role that is reassessed annually. TD is committed to ... We are seeking a skilled Senior Software Engineer with expertise in Java with expertise in Node JS ...

Software Engineer III

Toronto, ON · On-site

CA$125K - CA$154K/yr

... temporary market premium specific to this role that is reassessed annually. TD is committed to ... Adhere to enterprise frameworks or methodologies that relate to software engineering activities

Software Engineer III

Toronto, ON · On-site

CA$125K - CA$154K/yr

... temporary market premium specific to this role that is reassessed annually. TD is committed to ... Adhere to enterprise frameworks or methodologies that relate to software engineering activities

Software Engineer III (AI Integration)

Toronto, ON · On-site +1

CA$125K - CA$154K/yr

... temporary market premium specific to this role that is reassessed annually. TD is committed to ... This role combines software engineering, data science, and machine learning expertise to develop ...

Software Engineer III

Toronto, ON · On-site

CA$125K - CA$154K/yr

... temporary market premium specific to this role that is reassessed annually. TD is committed to ... Develop and maintain technical solutions, ensuring adherence to engineering and architectural ...

Staff Software Engineer

Toronto, ON · Hybrid

CA$149K - CA$183K/yr

... temporary market premium specific to this role that is reassessed annually. TD is committed to ... DevOps practices, CI/CD pipelines, automated testing, and modern software delivery practices.

New

Software Developer

Stouffville, ON · Hybrid

CA$80K - CA$85K/yr

Software Developer (Temporary) Role Type: 3 Month Fixed Term Contract Department: R&D Reports to: Manager, Software Engineering Location: Stouffville, ON (Hybrid) Salary: $80,000 - $85,000 Who we are:

Knowledge and understanding of Software Engineering Concepts and Methodologies is required * 3+ years of experience in data engineering or software development, ideally with exposure to technical ...

Knowledge and understanding of Software Engineering Concepts and Methodologies is required * 3+ years of experience in data engineering or software development, ideally with exposure to technical ...

next page

Showing results 1-20

Temporary Tcs Software Engineer information

What is the difference between Temporary Tcs Software Engineer vs Contract Tcs Software Engineer?

AspectTemporary Tcs Software EngineerContract Tcs Software Engineer
Employment TypeTemporary, short-termContract, project-based
DurationTypically weeks to monthsVaries by project, often months to a year
CredentialsRelevant degrees, certificationsSame as Temporary, often similar requirements
Work EnvironmentCompany's office or remoteClient site or remote, depending on project
EmployerHired directly or through staffing agenciesHired through staffing or consulting firms

Both roles involve short-term software development work for TCS, with similar credentials and work environments. The main difference lies in employment duration and contractual nature, with temporary roles often being shorter and more flexible, while contract roles are tied to specific projects with defined timelines.

What are the typical responsibilities and expectations for a temporary TCS software engineer, and how does the role differ from a permanent position?

As a Temporary TCS Software Engineer, you will typically be tasked with supporting ongoing projects, contributing to software development, testing, bug fixing, and documentation within established teams. While your daily responsibilities mirror those of permanent engineers, your assignments are often more project-specific and time-bound. Temporary roles may require you to quickly adapt to new technologies and team processes, and you may be expected to deliver results within shorter timelines. While advancement opportunities may be limited due to the temporary nature of the contract, performing well can enhance your chances for future permanent roles within TCS or similar organizations.

What are the key skills and qualifications needed to thrive as a temporary TCS software engineer, and why are they important?

To thrive as a Temporary TCS Software Engineer, you generally need a degree in computer science or a related field, solid programming skills (such as Java, Python, or C++), and knowledge of software development methodologies. Familiarity with tools like Eclipse, Visual Studio, Git, and experience with enterprise software systems or cloud platforms is often required. Strong problem-solving abilities, adaptability, and effective teamwork are essential soft skills for excelling in dynamic project environments. These competencies ensure you can quickly contribute to complex projects, collaborate with teams, and deliver high-quality software solutions within tight deadlines.

What is a temporary TCS software engineer?

Temporary TCS Software Engineers are professionals hired by Tata Consultancy Services (TCS) on a contractual or temporary basis to work on software development, maintenance, or support projects. Unlike permanent employees, they are employed for a defined period, often to meet project demands or fill short-term skill gaps. Their responsibilities may include coding, testing, debugging, and collaborating with teams to deliver solutions. Temporary roles offer flexibility but may not include all the benefits and job security of permanent positions.
What are the most commonly searched types of Tcs Software Engineer jobs in Toronto, ON? The most popular types of Tcs Software Engineer jobs in Toronto, ON are:
Infographic showing various Temporary Tcs Software Engineer job openings in Toronto, ON as of June 2026, with employment types broken down into 80% Full Time, 15% Part Time, and 5% Contract. Highlights an 95% Physical, 3% Hybrid, and 2% Remote job distribution.

Full-time

Medical, Dental, Vision, Life, Retirement

Posted 2 days ago

New


Job description

About the Project:


The Eglinton Crosstown West Extension will bring the Eglinton Crosstown LRT another 9.2 kilometers farther west, creating a continuous rapid transit line from the east end of Toronto into Mississauga. The Stations, Rail, and Systems (SRS) package encompasses the design, construction, integration, and commissioning of key project components.


Position Overview:


TRP has a current vacancy for a S&TCS Design Manager who will be responsible for managing and coordinating all S&TCS design activities for the ECWE Project. The role ensures that design deliverables prepared by S&TCS equipment manufacturer are developed, reviewed, approved and submitted in accordance with the project requirements, contractual obligations, applicable standards and project schedules.
This role serves as the S&TCS technical lead managing the design interface between the Primary Lead Designer, the signalling equipment manufacturer and transit authorities. The primary focus is ensuring that the S&TCS design is fully constructible, safe, integrated compliant with project specifications, and seamlessly integrates Alstom's CBTC platform into both the new extension and the existing Line 5 backbone.

The S&TCS Design manager will ensure the effective design integration, timely resolution of technical issues, and accurate reporting of design progress and performance.


Key Responsibilities:


Design Management

  • Manage the end-to-end delivery of S&TCS design documentation developed by Alstom.
  • Monitor design progress against approved schedules and project milestones.
  • Ensure design deliverables comply with contractual requirements, client standards, regulatory requirements, and project procedures.
  • Review design submissions and coordinate comments from relevant stakeholders.
    Manage the technical review cycle with Infrastructure Ontario, Metrolinx, and the TTC to resolve engineering comments, clear variances, and secure Stage Gate approvals.
  • Track design revisions and ensure effective management of design changes.
  • Identify design risks and implement mitigation measures to maintain project objectives.


Coordination and Interface Management

  • Serve as the primary coordination point between Alstom and the Lead Designer.
  • Facilitate technical discussions and design review meetings.
  • Ensure timely resolution of design interfaces and technical issues.
  • Coordinate multidisciplinary design inputs and integration with other railway systems and civil infrastructure.
  • Maintain effective communication among project stakeholders to ensure alignment on technical requirements and project priorities.


Technical Oversight

  • Provide technical leadership and guidance on S&TCS design documentation.
  • Verify that system designs comply with relevant railway standards, specifications, and operational requirements.
  • Support the review and resolution of technical deviations, non-conformities, and design-related issues.
  • Participate in design assurance and verification activities as required.

Planning and Reporting

  • Develop and maintain design status trackers and action registers.
  • Monitor key performance indicators related to design delivery.
  • Prepare regular design progress reports for project management and stakeholders.
  • Present design status, risks, issues, and mitigation actions during project meetings.
  • Maintain records of design reviews, decisions, and action items.

Risk and Change Management

  • Identify and manage design-related risks and opportunities.
  • Support the assessment of design changes and their impact on cost, schedule, and project delivery.
  • Escalate critical issues requiring management intervention.


Engineering Governance & Constructability

  • Design Optimization: Review engineering submissions from the Lead Designer to enforce constructability, identify design gaps, and eliminate spatial or logic clashes before construction release.
  • Digital Engineering (BIM): Utilize BIM/Navisworks software to perform multi-disciplinary coordination, resolving physical clashes between signaling cables, trackway assets, structural elements, and MEP systems.
  • Stakeholder Technical Approvals: Manage the technical review cycle with Infrastructure Ontario, Metrolinx, and the TTC to resolve engineering comments, clear variances, and secure Stage Gate approvals.


Technical Change Management: Evaluate and provide technical impact assessments for any proposed design changes, modifications, or field variances affecting the S&TCS network.



Qualifications:


  • Bachelor's degree in Electrical, Computer, or Systems Engineering from an accredited university.
  • 8+ years of rail S&TCS design and engineering experience.
  • Proven experience working as a S&TCS Design Manager or Lead Systems Engineer for a general contractor, consortium, or major delivery partner on large-scale design-build transit projects.
  • Demonstrated success managing complex technical interfaces between major rolling stock/signaling OEMs and civil infrastructure teams.
  • Deep technical familiarity with Alstom CBTC, including zone controllers, transponders/balises, and system application configurations.
  • In-depth knowledge of CBTC (Communications-Based Train Control) principles, wayside equipment layouts, track circuits, and axle counters.
  • Thorough understanding of Metrolinx, TTC, and Canadian railway standards, alongside international functional safety frameworks (CENELEC and AREMA).


What TRP Can Offer You:


  • Competitive Salary
  • Medical, dental, and vision insurance
  • Employer Matching Retirement Program
  • Life insurance


At TRP, we are committed to providing an environment of mutual respect where equal opportunities are available to all applicants and teammates. Accommodation is available upon request for applicants throughout the recruitment and selection process.


We thank all applicants for their interest. However, only those selected for an interview will be contacted.


*Compensation range intentionally omitted as this position is exempt from compensation disclosure requirements under the Ontario Employment Standards Act, 2000, , S.O. 2000, c. 41.*