C#.Net Developer

Location Address : 2201 Eglinton Ave E Ecosystem 4.

Work arrangement : (Hybrid) 3 days in office

Contract Duration : till Oct 31st

Possibility of extension & conversion to FTE? –Yes / possible

Schedule Hours : 9am-5pm Monday-Friday –No over time

Typical Day in Role :

• Review existing VB6 application modules to understand current business logic, workflows, and dependencies.
• Translate and rewrite legacy VB6 code into modern C# / .NET Core following current architectural standards and best practices.
• Analyze legacy SQL queries, stored procedures, and data access patterns, then refactor or rebuild them using SQL Server.
• Document legacy functionality and map it to the new technology stack to ensure functional parity during the rewrite.
• Write clean, maintainable, testable C# code that aligns with the new enterprise wide modernization framework.
• Perform unit testing and assist with integration testing to validate rewritten components behave consistently with the original system.
• Participate in code reviews to ensure quality, consistency, and adherence to modernization guidelines.
• Troubleshoot issues discovered during the rewrite process and propose improvements to enhance performance, reliability, and maintainability.
• Contribute to ongoing documentation of the new system, including technical specifications, migration notes, and updated architecture diagrams.
• Support the team by identifying gaps, risks, or dependencies in the modernization effort and recommending solutions.

Candidate Requirements / Must Have Skills :

Nice to have requirements

Degrees or certifications :

Best vs average candidate

The ideal candidate is someone with strong experience working on legacy applications and leading modernization efforts. Because this project involves a large scale rewrite, we need someone who has already navigated the complexities of migrating older systems into a modern technology stack. Their background should include hands-on exposure to refactoring legacy code, validating functionality through thorough testing, and ensuring feature parity during the transition. This migration experience is the key indicator that they can step into this role and deliver successfully.

An average candidate would be someone who hasn’t gone through a major migration before. Without that experience, they’re often caught off guard by the unexpected issues that come up when rewriting or modernizing legacy systems. Migrations rarely go exactly as planned, and people who haven’t lived through that tend to struggle when things break, behave differently, or require creative problem solving. Candidates with real migration experience understand that unpredictability is part of the process, and they know how to adapt quickly, troubleshoot on the fly, and keep the project moving forward.